The site and its API can share one address with one proxy rule (/api to
the backend, everything else to the frontend). Status page at /api (/
redirects), /api/health, /api/docs/v2, /api/uploads. Stored upload
paths stay /uploads/… and are given out as /api/uploads/…. Old paths
still answer (/health, /uploads) or redirect (/docs, /docs/v2), so
two-address sites keep working. DEPLOYMENT.md and the agent plan
describe the single rule.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Site settings → AI, the usage tables and the 80% email show input/output
tokens and the percentage; the rand amounts from the Hub are dropped on
arrival. AiCall stores each call's tokens (migration ai_tokens). v2
/ai/status and /ai/usage carry tokens instead of cents. Needs Hub 2.0.1
for the token figures; older Hubs show the percentage only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One script for installing, updating and moving church installs, replacing
hope-events' scripts/deploy.sh and install.sh:
- deploy <church> [events] / --every-church, with --version, --main, --check
and --allow-local-changes: checks every product first (files changed by
hand, Node, release requirements from WHATS-NEW.md headings), then each
product in order with backup, checkout, install, migrate, build, PM2 reload
and a /health version check; a failure rolls that product back and stops.
- status [<church>]: checked-out and latest release, /health, and the old
folder kept after adopt.
- install <church> --products events --domain <address>: a new church under
/var/www/sites/<church>, writing church.env.
- adopt <church> --events-dir <old> builds the monorepo checkout next to the
running install and switches PM2 over; adopt --undo goes back to it.
Product hooks live in scripts/products/events.sh. shellcheck (lint:scripts)
and 47 bats tests (test:scripts) are part of npm run check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Workspaces: apps/events/backend and apps/events/frontend; apps/events itself
excluded (npm doesn't install node_modules for a workspace nested in another).
Its dev tools (Playwright, axe, concurrently) move to the root.
- Packages renamed @crosscode/events, -backend, -frontend; nested lockfiles removed.
- allowScripts moved to the root (npm ignores it in workspaces), same choices.
- Direct dependencies that moved pinned to their 2.1.1 versions in root overrides;
@sentry/node pinned only inside the backend.
- Same results as 2.1.1: 52 suites / 711 backend tests, typecheck, both builds.
- EVENTS-2.2-PLAN §2 and HANDOVER updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
History rewritten under apps/events/ (git filter-branch). Commit hashes changed;
the originals stay in the archived hope-events repo. Old v… tags are not brought over.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent on every server runs installs, scheduled/emergency updates and
uninstalls on signed jobs from the Hub, polls only (no listening port),
appends to frpc.ini in marked blocks, builds .env files from per-server
config in the Hub. FastPanel and DNS stay manual (emailed instructions).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ROADMAP-v3 decisions 21-24: Cross Events moves into crosscode-platform
(2.2.0); one crosscode script deploys Accounts plus the products named;
the Hub tracks releases per product with requirements; the Hub gets the
contracts as a committed file, not from the package registry. Cross Events
versions in the build order move up by one. HANDOVER updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- schemas/: JSON Schema (draft 2020-12) generated from the zod schemas by
npm run build (scripts/json-schemas.cjs), exported as
@crosscode/contracts/schemas/*
- Test: files match the zod schemas, every sample passes them (Ajv)
- Version 1.0.0, CHANGELOG and README
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- crosscode.event/1 and crosscode.event-feed/1 (feed, event.changed
webhook), with session and registration rules; parseEventFeed skips
and reports bad events instead of failing the whole feed.
- crosscode.church/1: branding, campuses, service times, contact, links.
- crosscode.identity/1: sign-in claims and the user.updated /
user.deleted / user.export back-channel calls and replies.
- Sign-in return helpers (isSafeReturnPath, encodeState/decodeState,
isRegisteredRedirectUri) so every product returns people to the page
they came from in the same safe way.
- Hub protocol v2: product on register/heartbeat, stats per product,
install public key, linked products, customerId/product in licences.
- @crosscode/contracts/signing (Node only): the Hub's HMAC scheme.
- Samples for every contract in samples/, checked by the tests (120).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm workspaces (packages/*, apps/*) with shared TypeScript, ESLint and
Jest setup and `npm run check`. @crosscode/contracts builds to CommonJS
and ESM (tsup) with the crosscode.<name>/<major> schema-name helpers.
packages/ui and apps/{accounts,website,app} are placeholders.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One install of each product per customer; House of Prayer booking
defaults; email and WhatsApp only (no push); Accounts hidden from
members. Pricing: Website R99 with 5 GB plus storage add-on, App from
R99, address once per church (own domain, crosscode.co.za address R10,
domain included R25). Authenticator app 2FA as Cross Events 2.2.0.
Handover now points at ROADMAP-v3; nothing left open in ROADMAP-v2.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Plan for selling three products from one Hub: shared users through a
per-church Accounts service, event sync in any direction on one shared
format (crosscode.event/1), PM2 installs per product per church.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Send now and Remind answer straight away with who they're going to and
queue the feedback-send task; the Feedback page refreshes to show progress.
- One-off background tasks (enqueueTask in src/jobs/index.js): pg-boss with
retries, or in-process after the response when the queue is off.
- Reminders are claimed with the 24-hour rule, so two tasks at once never
remind the same person twice.
- Tests: tests/tasks.test.js, tests/feedbackPage.test.ts, e2e/feedback.spec.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Supervisor -> Feedback (supervisors and admins, campus-scoped): every
event's form with answered of asked, response rate, average rating and
last reminder; per event the results per question (with the AI summary),
each response, and on named forms who was asked and who has answered.
- Remind those who haven't answered (or one person on a named form): a
fresh link, plus the form to anyone eligible who hasn't had it; nobody gets
the form or a reminder twice within 24 hours. The 3-day job is unchanged.
- Anonymous forms show no names and no list of who has answered.
- FeedbackInvite.reminderCount (migration 20261103120000_feedback_reminders);
access log action feedback_responses; help page; dashboard and Ctrl+K links.
- Roadmap: the AI helpers on the privacy pages are dropped; 2.1.0 is the
feedback page.
- Tests: tests/feedbackPage.test.ts, e2e/feedback.spec.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Heartbeat income bands widened from "over R100 000" to 14 bands up to
"over R10 000 000"; every licence-tier edge is a band edge (tested).
- New income.eventIncome12m: last 12 months' event income without donations,
sponsorships or donation legs, which the licence tier is billed on.
- Fix: donation legs were counted twice in the heartbeat income bands.
- Protocol doc, roadmap pricing decisions, changelog, what's new, handover.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The eight reports that list people get the AI summary too, sent as
anonymised totals built on the screen (aiReportData.ts): no names,
contact details, notes or comments; consent and medical only as counts.
The server refuses personal columns on those reports and logs each
summary in the access log (ai_report; sensitive for consent and medical).
Roadmap §18: 2.0.1, then crosscode.co.za, then 2.1.0 (AI helpers on the
Consent log and Access log).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
crosscode.co.za as Cross Code's main site with a Cross Events page;
church website and app as "coming later"; repo joshua/crosscode-site;
own server; no prices yet; contact form to info@crosscode.co.za;
privacy notice and terms of use; no cookies. Content from Joshua later.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AI helpers, API v1 removed, Argon2id passwords, React Compiler lint
rules back to errors, migration guide. Docs (HANDOVER, roadmap) mark
2.0.0 as released.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The 192 places the rules flagged are fixed and the rules are errors
again (npx eslint src: nothing). lib/hooks.ts: useStateSync (state
that follows other state, set while rendering), useExternalEffect
(API loads and browser reads), useNow; lib/navigation.ts hardNavigate
for full reloads after sign-out or identity switches; other pages use
the router. Resets moved into the handlers that cause them.
- The banner shows and hides at its times on open pages.
- HANDOVER, roadmap, README, FEATURES, SETTINGS, CHANGELOG updated;
2.0.0 section drafted in WHATS-NEW.
e2e 102/102 (PayFast sandbox skipped); production build passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>