# Handover — where things stand and how to carry on Last updated: 2026-11-05, after **2.1.1** (deployed), **Hub 2.0.0** (released, not deployed yet), **contracts 1.1.0** and the crosscode-site address prices (not deployed yet); ROADMAP-v3 updated for the monorepo move and the `crosscode` deploy script (decisions 21–24). **The plan from here is [ROADMAP-v3.md](./ROADMAP-v3.md)** (Accounts, Church Website, Church App, Cross Code Hub; decisions table near the end). How Cross Events got to 2.x is in [ROADMAP-v2.md](./ROADMAP-v2.md); the round before that in [FEATURES-ROUND-1.md](./FEATURES-ROUND-1.md). The product is called **Cross Events** (renamed from Hope Events in 1.41.3); the Hub is the **Cross Events Hub**. Technical names keep `hope-events` on purpose — the repo, browser storage keys (`hope_events_*`), the settings encryption salt, applied migrations, PM2/nginx names, the install folder and the database name — because renaming them would sign everyone out, make encrypted settings unreadable or break existing installs. ## Done so far (road to 2.0) **2.0.0 is released** (2026-11-02). What changed for integrations and servers is in [MIGRATING-TO-2.md](../MIGRATING-TO-2.md). | Version | What | |---------|------| | 2.1.1 | **Feedback sends in the background:** "Send now" and "Remind" answer straight away and queue the `feedback-send` task (`enqueueTask` in `src/jobs/index.js` — pg-boss, or in-process when the queue is off; tasks must be safe to run twice). Tests `tests/tasks.test.js`, `tests/feedbackPage.test.ts` | | **2.1.0** | **Feedback page** (Supervisor → Feedback): overview, per-event results / responses / people, **Remind** (all who haven't answered, or one person on a named form; 24-hour gap) — `src/services/feedback.ts`, `src/v2/resources/feedback.ts`, `frontend/src/app/dashboard/supervisor/feedback/page.tsx`; reminders share `sendFeedbackReminders` (utils/feedback.js) with the 3-day job; anonymous forms show no names or who answered; access log `feedback_responses`. Migration `20261103120000_feedback_reminders` (`FeedbackInvite.reminderCount`). Tests `tests/feedbackPage.test.ts`, `e2e/feedback.spec.ts` (the e2e seed puts a named form on the past event). AI on the privacy pages dropped from the roadmap | | 2.0.2 | **Billing bands** (Hub 1.7.0 bills on them: invoices, receipts, statements, licence-change notices — events-hub README "Billing"): heartbeat income bands widened to `over R10 000 000` (`BAND_TOPS` in `src/hub/report.js`, every licence-tier edge is a band edge — test in `tests/hub.test.js`), new `income.eventIncome12m` (12 months, no donations/sponsorships/legs) that the tier is billed on, donation legs no longer double-counted. Tiers and prices live in `crosscode-site/src/data/pricing.mjs` and the Hub's `frontend/src/lib/tiers.ts` (Hub 1.6.2) | | 2.0.1 | **Summarise this report on every report:** the eight reports that list people are sent as anonymised totals built on the screen (`frontend/src/components/reports/aiReportData.ts`; attendees in `buildAiPayload` in `ReportsV2.tsx`); the server refuses personal columns on those (`personalColumns` in `backend/src/ai/helpers.ts`, 403 `AI_REPORT_HAS_PEOPLE`) and logs each (`ai_report`) | | **2.0.0** | **AI helpers** (draft an event, draft a message, summarise a report or feedback, improve text — `backend/src/ai/`, through the Hub with a rand cap per licence; eval set `npm run ai:eval`); **API v1 removed** (410 `API_V1_REMOVED`; provider webhooks and links in sent messages still answered — [v1 removed](#v1-removed-20)); **Argon2id passwords** with re-hashing at sign-in ([Passwords](#passwords-20)); `node-fetch` removed; React Compiler lint rules back to errors (`lib/hooks.ts`, see [Next.js 16](#nextjs-16-1515)); campus-scope route test on v2 (`tests/v2CampusScope.test.ts`); migration guide `MIGRATING-TO-2.md`. Migration `20261030120000_ai_helpers`. Needs Hub 1.6.0+ for AI | | 1.52.3 | **Urgent fix:** licence read-only mode blocks the `/api/v2` routes too (`src/hub/readOnly.js` only listed v1 paths, and the screens have used v2 since 1.51.15). A test checks each blocked v2 path is a real route | | 1.52.2 | `scripts/deploy.sh` stops first (listing them) when files in the install were changed or added by hand; `--check` runs only that; runs from a copy outside the install too; `ALLOW_LOCAL_CHANGES=1` overrides | | 1.52.1 | **API documentation complete:** every v2 route documents its body, answer and parameters — the ~300 answered by v1 handlers through `documented` shapes (`src/v2/docs.ts`), shown but not enforced, logged outside production when they don't fit; empty bodies say "No body needed". Test `tests/v2Docs.test.ts` | | 1.52.0 | **Urgent fix + Corrections:** required attendee forms no longer leave paid door/manual registrations without tickets — popup with "Fill in later" (`Registration.formWaivedAt`, `POST /api/v2/registrations/{id}/form-later`); one form per person on picked sessions; forms with no questions don't hold tickets; kiosk asks for the forms the server says are missing. Admin **Corrections** page (`src/services/corrections.ts`, `/api/v2/corrections/…`): issue missing tickets, pay later (`ticketsReleasedAt`), make it free (`complimentaryDiscount`), check in after the event. Migration `20261102120000_corrections`. e2e `e2e/corrections.spec.ts` | | 1.51.17 | **Security:** forgot-password and sign-in don't reveal whether an account exists (same answer, status and timing); forgot-password rate-limited | | 1.51.16 | **Incoming webhooks and message links on v2** — `src/v2/links.ts` (`/api/v2/webhooks/…`, one-click unsubscribe, 308s for old links); provider URLs and email links point at v2 | | 1.51.15 | **Privacy and admin on v2** — `resources/adminPrivacy.ts`; every frontend call on v2; impersonation end/log allowed on v2 while read-only | | 1.51.14 | **People and messaging on v2** — `resources/peopleMessaging.ts`; `/event-listing` for the public pages; `defineRoute` refuses duplicates | | 1.51.13 | **Kids check-in and volunteers on v2** — `resources/kidsVolunteers.ts` | | 1.51.12 | **Tickets and attendance on v2** — `resources/attendance.ts`; frontend `apiV2Raw()` for string-path helpers | | 1.51.11 | **Money on v2** — `src/v2/viaV1.ts` (`v1Route`: a v2 route answered by the v1 handler); `resources/money.ts`; `/docs/v2` collapsed with a filter | | 1.51.10 | **Managing registrations on v2** — `src/services/registrationAdmin.ts` (the rest of `registrationController.js`); frontend `fetchAllRegistrations()`; money split out to 1.51.11 | | 1.51.9 | **Series, season passes, bundles, coupons, campuses on v2** — `src/services/series.ts`, `deals.ts`, `campuses.ts`; `reason` on v2 errors from service codes; frontend `apiV2Data()` | | 1.51.8 | **Rest of event set-up on v2**: event in full, calendar, alias, ticket options and variants, attachments, sections, costs, image uploads — `src/services/eventDetails.ts`, `src/services/setup.ts`; frontend `fetchEvent()` and `lib/eventSetup.ts`; v2 `file` and `upload` routes | | 1.51.7 | **Setting events up on v2** (`/events/manage`, create, `PATCH`, deactivate, copy-from, notify-recipients) via `src/services/events.ts`; `fetchManagedEvents()` for every picker; **pg-boss 11** in schema `pgboss_v11` | | 1.51.6 | Command palette lists every report (from `ReportCatalog`) and every dashboard page (e2e drift check); exceljs → ExcelTS 10 (`@cj-tech-master/excelts`, no dependencies; e2e `e2e/excel.spec.ts`); backend `engines.node` >= 22 | | 1.51.5 | **Next.js 16** and React 19.3 (Turbopack), **ESLint 10** with Next 16's flat configs (`npm run lint` = `eslint src`); React Compiler-era rules as warnings for now; empty `middleware.ts` removed | | 1.51.4 | **Security and dependency updates**: Next.js 15.5.28, @sentry/nextjs, zod, multer, nodemailer and others for published advisories; minimum versions raised in package.json; cron-parser 5 | | 1.51.3 | **Express 5** (qs query parser and `req.body = {}` kept); scanner and at-the-door on v2 check-in; shared middleware answers v2-shaped on `/api/v2` (`legacyErrorsToV2`, `reason`); v1 `Deprecation` + `successor-version` headers (`src/v2/deprecation.ts`) | | 1.51.2 | **v2 accounts and check-in**: signup, login (+ code step), `PATCH /me`; check-in look-up and scan with `outcome`s. `src/services/auth.ts` (from userController) and `src/services/checkin.ts` (from ticketController); login/signup/profile pages on v2 | | 1.51.1 | **v2 registrations and payments**: register, get, cancel, checkout; create/cancel moved to `src/services/registrations.ts`, online checkout to `src/services/payments.ts` (v1 uses them too); typed frontend calls (`apiV2`, `npm run api:types`); register page, Pay now and My Events cancel on v2 | | 1.51.0 | **TypeScript backend + `/api/v2` foundations** (§14): tsconfig (`allowJs`), build to `dist/`, launcher `src/index.js` → `src/app.js`; v2 route declarations with zod → validation, response stripping and OpenAPI 3.1 at `/docs/v2`; first endpoints events, event, me, my registrations. Tests `tests/v2.test.ts`, e2e `e2e/api-v2.spec.ts` | | 1.50.2 | Searchable **event picker** (`components/shared/EventPicker.tsx`) on staff/supervisor pages and the kiosk; searchable reports events list; **How webhooks work** guide on Site settings → Webhooks (examples from `EVENT_TYPES[].example`). e2e `e2e/event-picker.spec.ts` | | 1.50.1 | Long lists: audit-log search/role filter/all actions and inclusive To date, data-request search and paging, webhook-delivery status filter and Load older, supervisor Payments loads only what it needs (`unpaid`, `userId`, `from`, `donations` filters). `components/shared/Pager.tsx`; e2e `e2e/long-lists.spec.ts` | | 1.50.0 | **Accessibility pass** (§11, WCAG 2.2 AA) on public pages, auth, registration, payment, My Events and the kiosk: skip link, focus ring, labelled fields, named quantity buttons, announced errors, `ModalOverlay` popups (focus trap, Escape), contrast and underlined in-text links, reduce-motion; Branding warns about a too-light primary colour. axe + keyboard e2e in `e2e/accessibility.spec.ts` | | 1.49.2 | **Saved filters** (§9 part 3) on registrations, users, events and reports (`/api/saved-filters`, `components/shared/SavedFilters.tsx`). Migration `20261028180000_saved_filters` | | 1.49.1 | **Bulk actions** on Manage registrations (§9 part 2): message, mark paid, move ticket, allocate, export, cancel (`POST /api/registrations/bulk`, `utils/bulkRegistrations.js`). Migration `20261028170000_registrations_bulk` | | 1.49.0 | **Dashboard and command palette** (§9 part 1): Today and Waiting for you on the staff/supervisor/admin dashboards (`GET /api/dashboard/today`), Ctrl+K palette (`GET /api/dashboard/search`, pages in `lib/commandPages.ts`), deep links on events/registrations/users | | 1.48.2 | Four demo seeds (`npm run demo:small|events|ministry|multicampus`, `demo:list`); fixes `set-demo`, broken since 1.43.0 by TRUNCATE CASCADE through `User.homeCampusId` | | 1.48.1 | Built-in privacy notice updated (rosters, series, season passes, webhooks, acceptance); editor shows built-in changes to sites with their own version; activation asks for agreement; never-accepted users asked once after login | | 1.48.0 | **Outbound webhooks** (§8): Site settings → Webhooks, 8 event types, signed deliveries with retries and a delivery log, operator register entry per endpoint. Migration `20261028160000_webhooks` | | 1.47.4 | Fix: an update request for a version that has since been overtaken shows as such, with **Ask for … instead** (and the banner again). Hub 1.5.0 moves the open request on (`changed`); with an older Hub `requestUpdate` withdraws and asks again | | 1.47.3 | **Season passes** (§6 part 4): passes on the Event series page, buy on the series page (a registration per event, one checkout), price split by normal prices, one Payment per event from the webhook. Migration `20261028150000_season_pass` | | 1.47.2 | **Series: year on year** report (§6 part 3): `GET /api/series/:id/compare` (`compareSeries` in `utils/series.js`), report `seriesComparison` in `ReportsV2`, "Compare" on the Event series page | | 1.47.1 | **Event series** (§6 part 2): Event series page, Series box on events, public `/series/`, "Next in this series", follow (News & announcements email from the `series` job when a new event goes live). Migration `20261028140000_event_series` | | 1.47.0 | **Copy an event** (§6 part 1): "Copy" opens the event editor filled in from the source (campus, sessions, options, tiers, sections, form, recipients, feedback, certificates); "New start" moves every date; allocation groups and (admins) costs copied by `POST /api/events/:id/copy-from`. No registrations, coupons, attachments, kids check-in or volunteer roles | | 1.46.2 | Licence page: what's new (from WHATS-NEW.md via the Hub), withdraw update request, "Not now", urgent updates, provider notices banner (Hub 1.4.0: releases from git tags, Notices page) | | 1.46.1 | Removed the Gitea CI workflow (no runner): test, lint and deploy by hand | | 1.46.0 | **Volunteer rosters** (§5): serving roles per event or session, anyone signs up (or supervisors assign), day-before reminders, "can't make it" swaps that happen on accept (notify recipients emailed), self check-in with the event's QR code or by staff, kids-room roles count as leaders on duty, free volunteer ticket off by default, roster sheet and hours served. Also fixes the 1.45.0 kids ticket being offered publicly | | 1.45.1 | Privacy notice (built-in text) and terms of use brought up to date with kids check-in, sessions, certificates, campuses, the Hub heartbeat and where data is stored. Installs with a published notice must publish a new version themselves | | 1.45.0 | **Kids check-in** (§4), fully digital: families/children/authorised adults kept between events (My account → Kids), staff desk with pickup codes and a "write on the sticker" panel, rooms with age ranges and ratios, room screen (on duty, call parent, alerts), check-out by code (wrong code alerts, override with reason), offline desk with reserved codes, attendance through a free kids ticket; 6-month retention rule for children | | 1.44.0 | **Campus-scoped staff** (§12 part 2): Admin → Users "Limit to campuses"; `utils/campusScope.js` on every staff/supervisor route (and owner-or-staff routes), lists filtered, scanner names the other campus, church-wide events view/scan/door-only for scoped staff; route test `tests/campusScopeRoutes.test.js` | | 1.43.0 | **Campuses** (§12 part 1): Site settings → Campuses (off by default), events per campus or all campuses, public campus filter (remembered, starts on home campus) and `/campus/` pages, home campus on the profile, campus filters on Reports and the dashboards, "Everyone at a campus" in broadcasts, campus summary recipients, campus on ticket PDFs, heartbeat `campusCount`. Also adds the `hub_update_requested` audit action missing since 1.42.0 | | 1.42.1 | Production Hub public key built in (`publicKey.js`); `HUB_PUBLIC_KEY` only needed for a local Hub | | 1.42.0 | **Request update** instead of the deploy command: Site settings → Licence sends a signed update request to the Hub (protocol §3a), which opens an alert and emails Joshua; "Update requested on …" until the site runs that version, and the admin update banner hides meanwhile. Audit action `hub_update_requested`. Needs Hub 1.1.0 | | 1.41.3 | Renamed Hope Events → **Cross Events** in all UI text and docs (technical identifiers unchanged, see above) | | 1.41.2 | Background jobs page: last-run times were 2 h ahead (Prisma's pg adapter drops the offset of timestamptz in raw queries — read pg-boss times `AT TIME ZONE 'UTC'`); `APP_TIMEZONE` documented | | 1.41.1 | Licence fixes — no licence (never connected, or the Hub answers `INSTALL_NOT_FOUND`, which now drops the old licence) is read-only like suspended; read-only also blocks editing events/options/variants; heartbeat 30 s after start and after connecting; `LICENCE_CHECK_DISABLED` for e2e | | 1.41.0 | Cross Events Hub connection — licence step in `/setup` and Site settings → Licence, 15-minute heartbeat (health, totals, income bands), licence states checked offline (grace banner for site admins only, read-only when suspended/revoked), `/health`, "update available", `scripts/install.sh`. The Hub itself is `joshua/events-hub` 1.0.0 | | 1.40.0 | POPIA toolkit part 3 — readiness checklist with score, retention policies + nightly `retention` job (inactive accounts anonymised after 5 years with a 30-day warning, on by default), breach register with notification drafts, children's/medical flag in the access log, `{retention}` in the notice | | 1.39.0 | POPIA toolkit part 2 — Admin → Privacy: privacy notice editor (built-in text as the start, placeholders, drafts, numbered versions, re-acceptance after login), operator register, consent log, access log; Information Officer on the contact page | | 1.38.0 | POPIA toolkit part 1 — Privacy page (news opt-in + history, download my data, correction and deletion requests), Event update vs News & announcements on every bulk send, unsubscribe links + one-click headers, WhatsApp STOP, one-time news question, Admin → Data requests, thorough anonymising | | 1.37.4 | Deploy script: no tag = latest main; per-install `ecosystem.config.js` out of git (`ecosystem.config.example.js`) | | 1.37.3 | Fix: the production build failed on unescaped quotes in a help text | | 1.37.2 | Payment status checks (PayFast transaction history; job every 15 min; Payments → Reconcile → Waiting for payment), PayFast Test connection | | 1.37.1 | "Pay online" hidden when no provider is on or under R15; SnapScan/Zapper dropped from the roadmap | | 1.37.0 | PayFast (signed form, ITN checks), `ProviderCheckout` with amount checks, the "Pay online" page (`/pay/`) where payers choose a provider | | 1.36.0 | Payment provider interface (`backend/src/payments`) with Yoco behind it, `ProviderTransaction`, `Payment.provider`, Site settings → Payments (on/off and order per provider), R15 minimum | | 1.35.1 | Waitlist per session, session picker at the door, "All sessions" tickets let people tick sessions at one price; fixes (per-session stock limits, offline service worker serving stale scripts) | | 1.35.0 | Multi-day events phase B — "pick sessions" (per-session tickets and prices, session capacity) | | 1.34.0 | Background jobs on pg-boss (admin Background jobs page), Playwright e2e tests, Gitea CI workflow (removed in 1.46.1), `scripts/deploy.sh` | | 1.33.0 | Multi-day events phase A — sessions, late joining + late pricing, per-session check-in, attendance register, session reminders, certificates (4 templates, verify page) | | 1.32.0 | Early-bird ribbon on event cards | ## Next up 1. **Roadmap v3** ([ROADMAP-v3.md](./ROADMAP-v3.md), decided 2026-11-03). Everything in ROADMAP-v2 is done: 2.1.1 is deployed, and the marketing site (`../crosscode-site`, crosscode.co.za, with prices) is live. Build order (§9): - **0 — contracts 1.0.0: released 2026-11-04** (`../crosscode-platform`, tag `contracts@1.0.0`): `crosscode.event/1`, `crosscode.church/1`, `crosscode.identity/1`, Hub protocol v2, generated JSON Schema in `packages/contracts/schemas/`. **1.1.0** (2026-11-04) adds `requires` on Hub releases. Not published to Gitea's package registry, and won't be (decision 22). - **1 — Hub 2.0.0: released 2026-11-05** (`../events-hub`, tag `v2.0.0`; plan and what each step did in its `docs/HUB-2.0-PLAN.md` and CHANGELOG): products and one licence per product, protocol v2 next to v1 (Linked products), releases per product with requirements, billing per church (bundles, founding, Website storage, App tiers, prorating), the church's address, AI per church, dashboard per product. **Deploying it:** `events-hub/deployment.md` → "Upgrading to 2.0" (run `check-hub2` first). crosscode-site has the address prices (merged, deploy it too). Then installs show up per product; Cross Events 2.1.x keeps speaking protocol 1 until 2.4.0. - **1b — Cross Events 2.2.0: moves into the monorepo** as `apps/events` with its history, and the **`crosscode` script** (`deploy [events] [website] [app]` — Accounts always —, `status`, `install`, `adopt`) replaces `scripts/deploy.sh` / `install.sh`. Run `crosscode adopt` once per existing install; then archive this repo (ROADMAP-v3 §8, "Releases and updates"). From here on this file and the roadmap live in the monorepo. - **1c — Cross Events 2.3.0:** **authenticator app 2FA** (TOTP + recovery codes) next to email and WhatsApp (`TwoFactorMethod` enum in `prisma/schema.prisma`). - **2 — Cross Events 2.4.0:** protocol v2, Linked products, the event feed (publish and show). - **3 — Accounts 1.0.0**, **4 — Church Website 1.0.0**, **5 — Cross Events 3.0.0** (sign-in moves to Accounts), **6 — Church App 1.0.0** (House of Prayer). - **Before selling the Website or App:** put the prices decided in ROADMAP-v3 §10 in `crosscode-site/src/data/pricing.mjs` and the Hub's `frontend/src/lib/tiers.ts`. - Servers stay **PM2 + nginx** (no Docker); one database per product per church. - **AI for a church:** set the licence's monthly AI cap above R0 on the Hub (Hub 1.6.0+); with no cap the buttons don't show. - Testing AI locally: run the Hub (`../events-hub`, port 5200), set Settings → AI there, give a test licence an AI cap, and start Cross Events with `HUB_URL=http://localhost:5200`. - **Deploying:** `bash scripts/deploy.sh --check`, then `bash scripts/deploy.sh v` on each server (installs ask through Request update as usual). From Events 2.2.0 on: `crosscode deploy events` (ROADMAP-v3 §8). 2. **AI rules** (decided 2026-10-29, roadmap §15): the AI buttons show only when the licence's monthly cap is above R0, and are disabled (not hidden) once it's reached. The Hub charges the real cost plus a markup % (a default and a per-licence override) and counts the cap in charged rand. AI endpoints are `/api/v2` only. The model is set on the Hub (Settings → AI); its list prices live in `events-hub/backend/src/utils/aiModels.js`. 3. **Later (2.x):** move the v1 controllers behind `v1Route` into TypeScript services (the v2 API doesn't change); remove the handlers no v2 route uses any more (e.g. the v1 scan handler and `v1ScanResponse`, `v1Status` in `services/errors.ts`). Move from ExcelTS to `documonster` once it is stable. After 1.51.7 has run everywhere, drop the old `pgboss` schema (`DROP SCHEMA pgboss CASCADE;`). Languages (Afrikaans, §10) and Wallet passes (§7) are removed from scope (2026-10-28). ## Working on this repo - **Release routine:** branch `feat/` → commit → bump with `npm version X.Y.Z --no-git-tag-version` in `.`, `backend` and `frontend` → add the `## [X.Y.Z] - date` heading under `[Unreleased]` in CHANGELOG.md → write the church-facing `## X.Y.Z` section in **WHATS-NEW.md** (plain language; `— urgent` in the heading for a security or serious fix) → `git merge --no-ff` into `main` → `git tag vX.Y.Z` → `git push origin main vX.Y.Z`. One minor version per feature. - **Before tagging:** run `npx eslint src` in `frontend` over the **whole** app (since Next 16 `next build` no longer lints — it still fails on TypeScript errors — so lint errors only show up if you run it; keep it at 0 errors). If a dev server is running, a full check build needs its own folder: `NEXT_DIST_DIR=.next-buildcheck npx next build` (then delete it and `git checkout frontend/tsconfig.json`). - **Changelog:** add entries to `[Unreleased]` as you go, in plain language. CHANGELOG.md is the full log; WHATS-NEW.md is what churches see before updating (the Hub reads it from main every 15 minutes, for tagged versions only and sets the latest version from the tags — nothing to do in the Hub). - **Docs to keep in step:** CHANGELOG.md, FEATURES.md, README.md, SETTINGS.md (the API documents itself at `/docs/v2`; `backend/API_DOCUMENTATION.md` only points there), and in-app help in `frontend/src/content/help/` (register new pages in `registry.ts`). - **Prisma migrations:** `npx prisma migrate dev --create-only --name x` against a local DB. Prisma 7 keeps adding an unrelated `_EventNotifyRecipients` primary-key/index change — delete those two blocks from the generated SQL. It also rewrites the comment in `migration_lock.toml`; `git checkout` that file back. New `AdminAuditAction` values need a migration. - **Server Node version:** Node 24 LTS on every server (2026-10-29); new installs get it too. The backend declares `engines.node >= 22`. pg-boss 11 (1.51.7) runs in its own schema, `pgboss_v11` — it can't migrate pg-boss 10's `pgboss` schema; there's no `archive` table any more (finished runs stay in `job` until they expire). - **Deploying:** `bash scripts/deploy.sh [tag]` on the server (no tag = latest main). It stops first if files in the install were changed or added by hand (`--check` to only check; `ALLOW_LOCAL_CHANGES=1` to go ahead anyway). Each install keeps its own `ecosystem.config.js` (PM2 app names, port), which is not in git. The script runs from a temp copy of itself and rolls back on failure before the PM2 reload. It was tested by running it against a throwaway clone with npm/pm2 stubbed: across the tracked → untracked change for the PM2 file, deploying main, failed builds and a bad tag. - **Pushing:** pushing from some shells fails with "Failed to authenticate user" (a stale saved credential); pushing from your own terminal works. ## Tests - Backend unit tests: `cd backend && npm test` (Jest). - PayFast e2e (`e2e/payfast.spec.ts`) pays into a real PayFast sandbox account and is skipped unless `E2E_PAYFAST_MERCHANT_ID`, `E2E_PAYFAST_MERCHANT_KEY` and `E2E_PAYFAST_PASSPHRASE` are set (from the Sandbox dashboard). PayFast's documented public test merchant (10000100) no longer accepts payments. ITNs can't reach localhost; they're covered by unit tests (`backend/tests/payments.test.js`) — to try one for real, use a tunnel, a public `BACKEND_URL` and `PAYFAST_SKIP_IP_CHECK=true`. - End-to-end: `npm run test:e2e` from the repo root (first time: `npm install` and `npx playwright install chromium`). They start their own backend (5100) and frontend (3100) against `_e2e`, which is dropped and re-seeded every run (`e2e/support/prepare-db.js`). The DB user must be able to create databases. ~5 minutes in dev mode. Locally, Playwright reuses servers already running on 5100/3100. If the run times out waiting for the frontend (the home page returns 500 until the e2e backend is up), start them yourself — `node e2e/support/prepare-db.js`, then the backend from `backend/` with `PORT=5100`, the e2e `DATABASE_URL`, `JOBS_ENABLED=false`, `TWO_FACTOR_REQUIRED_ROLES=false`, and `npx next dev -p 3100` from `frontend/` with `NEXT_DIST_DIR=.next-e2e NEXT_PUBLIC_API_URL=http://localhost:5100` — then run `npx playwright test`. Don't edit frontend files while it runs. - **Careful with ad-hoc scripts against a dev/test database that has SMTP set up:** registrations and check-ins send real email/WhatsApp. Use made-up `@test.local` people only. - No CI: the Gitea workflow was removed (no machine to run a Docker runner). Run the backend tests, frontend eslint and e2e tests yourself before tagging, and deploy by hand with `scripts/deploy.sh ` on the server. ## Where the multi-day code lives - `backend/src/utils/sessions.js` — all session rules (dates, check-in window, late pricing, pick sessions, capacity, grouping); unit tests in `backend/tests/sessions.test.js`. - `backend/src/utils/certificates.js`, `sessionReminders.js`, `controllers/attendanceController.js` (register + certificates API). - `backend/src/jobs/index.js` — the background job registry. - Frontend: `src/lib/sessions.ts`, `src/components/events/ScheduleEditor.tsx`, `SessionPicker.tsx`, `SessionSchedule.tsx`, `src/app/dashboard/supervisor/attendance/`. ## Where the payment code lives - `backend/src/payments/index.js` — the provider registry and the `PaymentProvider` interface (documented at the top), provider on/off and order (AppSetting `payment_providers`), the R15 minimum, and `createCheckout`. Tests: `backend/tests/payments.test.js`. - `backend/src/payments/providers/yoco.js` — Yoco: checkouts, webhook signature check, webhook parsing. Keys/webhook admin stays in `utils/yoco.js` + `controllers/yocoController.js`. - `backend/src/payments/webhook.js` — shared webhook processing (Payment with `provider`, donation split, registration status, tickets, emails, `ProviderTransaction`). - `backend/src/payments/checkouts.js` — registration checkouts (balance, part, + donation). - `backend/src/payments/status.js` — status checks for notifications that never arrived (`payment-status` job, Payments → Reconcile → "Waiting for payment"). PayFast looks payments up in its transaction history (`findPayments`); Yoco's Checkout API documents no lookup, so Yoco checkouts are "can't check". Tests: `backend/tests/paymentStatus.test.js`. - **Adding a provider:** write `providers/.js` with the same interface, add it to `PROVIDERS` in `index.js`, mount `handleProviderWebhook('')` at `/api/v2/webhooks/` (in `src/v2/links.ts`; add the v1 path in `routes/webhookRoutes.js` only for providers already registered there), and give it a settings card in `frontend/src/components/admin/PaymentsTab.tsx`. New providers start switched off. - `Payment.method` stays the wallet type (card, apple_pay…) because cashups bucket on it; the provider is `Payment.provider`. ## Where the privacy (POPIA) code lives - `backend/src/utils/privacy.js` — news opt-in (`setNewsPreferences`, logged in `CommunicationConsent`), unsubscribe tokens (HMAC with `JWT_SECRET`, never expire), `filterRecipients` (every bulk send goes through it: `kind` 'update' passes, 'news' only to opted-in accounts and not to `MessagingOptOut` addresses), email/WhatsApp footers, STOP handling, data requests, `deletionBlockers`, `anonymiseUser`, `exportUserData` + PDF. Tests: `backend/tests/privacy.test.js`; e2e: `e2e/privacy.spec.ts`. - `controllers/privacyController.js` + `routes/privacyRoutes.js` (`/api/privacy`). - Bulk sends: `broadcastController`, `whatsappBroadcastController`, and `emailEventAttendees` / `whatsappEventAttendees` in `eventController` take `kind`; scheduled payloads carry it. - WhatsApp STOP: `handleIncomingMessage` in `whatsappController.js` (WAWP `message` event on `/api/v2/webhooks/whatsapp?secret=…` — older set-ups use `/api/whatsapp/webhook` or `/api/webhooks/whatsapp`, which run the same handler since 1.51.16; secret in AppSetting `WAWP_WEBHOOK_SECRET`). - Frontend: `app/dashboard/user/privacy`, `app/unsubscribe`, `app/dashboard/admin/data-requests`, `components/shared/NewsPrompt.tsx` (dashboard layout), `MessageKindPicker.tsx`. - **Anything new that stores personal data** must be added to `anonymiseUser` and `exportUserData`. - Privacy notice: `utils/privacyNotice.js` (built-in sections, placeholders, versions, draft in AppSetting `privacy_notice_draft`, `noticePromptPending`); public page `app/legal/privacy` (renders whatever `/api/privacy/notice` returns), admin `app/dashboard/admin/privacy` + `components/admin/privacy/*`, prompt `components/shared/NoticePrompt.tsx` (via `PrivacyPrompts.tsx`: notice first, then the news question). **Changing the built-in text changes the live notice only for installs that haven't published a version yet** — so every change to `DEFAULT_SECTIONS` must also add an entry to `BUILT_IN_UPDATES` (the release, a summary, the section ids changed). Sites with their own version then see it in the editor until they press "Done — hide this" (AppSetting `privacy_notice_builtin_reviewed`). A test checks the ids exist. - Accepting the notice: sign-up (`source: 'signup'`), account activation (`'activation'`, the form's terms box) and the after-login prompt (`'prompt'`). `noticePromptPending` is `'first'` for anyone who never accepted (`noticeVersionAccepted` null) and `'updated'` when a significant version came out later. The e2e seed sets `noticeVersionAccepted: 0` so the prompt doesn't cover every test. - The cookie button on the privacy page shows above any section whose id contains "cookie". - Access log: `utils/accessLog.js` (`logDataAccess(req, { action, what, eventId, records })`). **Any new bulk export or list of personal data should call it** and get a label in `ACCESS_ACTIONS`. Operators: `Operator` table, seeded in the 1.39.0 migration. - Retention: `utils/retention.js` (policies in AppSetting `retention_policies`, `runRetention`, `preview`, `noticeLines` for `{retention}`), job `retention` (03:30). **Anything new that stores personal data should get a retention rule** (a new entry in `POLICIES` + runner). Inactive = latest of `User.createdAt`, `lastLoginAt` (set on login), registrations/event end, attendee rows, payments. Readiness: `utils/readiness.js`. Breaches: `SecurityBreach`. Admin panels: `components/admin/privacy/{Readiness,Retention,Breaches}Panel.tsx`. - e2e: `privacy-retention.spec.ts` runs the retention job on seeded six-year-old accounts (`prepare-db.js` → `retention`); `privacy-notice.spec.ts` publishes a version that needs accepting, then accepts it for all seeded users in `afterAll` so later spec files don't meet the prompt. ## Where the Hub client lives (1.41.0, update requests 1.42.0) - Protocol: `docs/hub-protocol.md` — the same file is in the Hub repo (`joshua/events-hub`, developed at `../events-hub`); change both together. - `backend/src/hub/`: `publicKey.js` (the production Hub key, built in since 1.42.1 — if the Hub's signing key is ever regenerated, update it here in a release; `HUB_PUBLIC_KEY` env overrides it for a local Hub), `licence.js` (verify tokens, work out active / grace / suspended / revoked / unlicensed, cached 30 s), `client.js` (connect, heartbeat, update request — the last two share `signedPost`; AppSetting `hub_*` keys, which the generic settings endpoints never touch), `report.js` (health, totals, income bands), `readOnly.js` (the routes blocked in read-only mode — add any new "create" or event-edit route there). Read-only = suspended, revoked or unlicensed. - Job `hub-heartbeat` (every 15 min), routes `/api/hub/*` (status, connect, heartbeat, update-request), `/health`. - Frontend: `components/admin/LicenceTab.tsx` (Site settings → Licence, with the **Request update** button; its `ConnectForm` is also on the last `/setup` screen), `components/shared/LicenceBanner.tsx` (site admins only). - **Updates:** sites never update themselves and never show the deploy command. "Request update" tells the Hub (an `update_requested` alert + one email to Joshua); the Hub resolves it when the site's heartbeat reports a newer version. Joshua then runs `scripts/deploy.sh` on the server. - Local testing: run the Hub (`../events-hub`, ports 5200/3200), create a licence there, and start Cross Events with `HUB_URL=http://localhost:5200` and `HUB_PUBLIC_KEY` = the key on Hub → Settings. - `scripts/install.sh` — fresh Ubuntu server to a running site (tried on a test server 2026-10-28). ## Where campuses live (1.43.0) - `backend/src/utils/campuses.js`: the setting (`campuses_enabled`, off by default), `campusWhere` (list filters: one campus, `'all'` = church-wide only, `withAllCampuses` for the public list), `campusForEvent` (what to save on an event), `campusAudienceWhere` (broadcast audience). Pure parts are tested in `tests/campuses.test.js`. - `controllers/campusController.js`, routes `/api/campuses/*`. The setting is changed only through `PUT /api/campuses/settings` (it's in `PRIVATE_KEYS` in the settings controller). - **While campuses are off, every campus field and filter is ignored** (the data stays). New code should check `campusesEnabled()` the same way. - Frontend: `hooks/useCampuses.ts` (one cached `GET /api/campuses` per page load), `components/shared/CampusFilter.tsx` (`CampusFilter`, `matchesCampus`, `CampusBadge`), `CampusAudiencePicker.tsx`, `components/admin/CampusesTab.tsx`, `components/events/EventsGrid.tsx` (public filter, `hope_events_campus` in localStorage), `app/campus/[slug]/page.tsx`. - e2e: the campuses and two events' campuses are **seeded** in `e2e/support/prepare-db.js` with campuses off (so a pre-built frontend already has them); `campuses.spec.ts` turns them on and off. ## Campus-scoped staff (1.44.0) — adding a staff route - **Every route behind `staff` or `supervisor` must carry a marker from `utils/campusScope.js`**, or `tests/campusScopeRoutes.test.js` fails: - `scopeEvent({ resolve, from, need, ownerOk, nameCampus })` — one event, or a record traced to one (`RESOLVERS`: registration, ticket, ticketQr, payment, eventOption, optionVariant, bundle, allocationSet/Group, waitlistEntry, scanLock, syncReport, section, certificate, consentRequest). `need: 'manage'` for setup, cashup and refunds (church-wide events refused). - `scopeBody([[field, resolver], …], { need, orphan })` — records named in the body (lists of ids too); `orphan: 'deny'` when there must be an event (payments). - `scopeList` — the controller filters with `listWhere(req, path)` / `withScope(where, extra)` (never spread a scope `where` over one that has its own OR) or checks itself. - `unscopedOnly`, `campusIndependent('reason')`, `scopeBroadcast({ freeformField })`. - Routes open to the owner *and* staff (no role middleware, so the test can't see them) need `scopeEvent({ …, ownerOk: true })` by hand — registrations, payments, tickets, consent requests and coupon validation have it. - Rules: admins never scoped; scopes ignored while campuses are off; another campus → 404, except the scanner (403 naming the campus). Tested in `tests/campusScope.test.js` and e2e `campus-scoped.spec.ts` (staff and supervisor scoped to E2E South; a seeded North ticket). ## Where kids check-in lives (1.45.0) - `backend/src/utils/kids.js` — everything: codes (`randomCode`, `normaliseCode`), occasions (`occasionFor`: today's session, or the day), room suggestion and status, families and children (allergies/medical/custody encrypted with `utils/encryption.js`), `checkIn` (code per family per occasion via `KidsPickupCode`, a free place on `Event.kidsOptionId` through `ticketForChild`, a `TicketUsage` per check-in), `checkOut` / `overrideCheckOut`, messages, `board`, duty, offline snapshot and `syncOffline`, and the privacy parts (`removeFromFamily`, `exportFamily`, `runKidsRetention`). Pure parts tested in `tests/kids.test.js`. - `controllers/kidsController.js` + `routes/kidsRoutes.js` (`/api/kids`); campus resolvers `kidsCheckIn` and `kidsAlert` in `utils/campusScope.js`. - Rooms are `AllocationGroup`s of `Event.kidsRoomSetId` (with `minAge`, `maxAge`, `ratio`). Event ids on `Event` (`kidsOptionId`, `kidsRoomSetId`) are plain strings, checked in code. - Kids check-in isn't blocked in licence read-only mode, on purpose: it's like scanning tickets, and children's safety at pickup comes first. - Frontend: `lib/kids.ts` (types, room suggestion, offline copy in `hope_events_kids_offline_`), `components/kids/*` (`KidsEventPicker`, `ChildForm`, `RoomBoard`, `StickerPanel`), pages `app/dashboard/staff/kids` (desk), `staff/kids/rooms`, `supervisor/kids` (setup), `user/kids`. - e2e: `kids.spec.ts` on the seeded hidden "E2E Kids Church" (set up, parent adds a child, desk checks in, parent sees the code, wrong code then the right one, room alert). ## Where volunteer rosters live (1.46.0) - `backend/src/utils/volunteers.js` — everything: shifts (`shiftOf`: the role's own times, else its session's, else the event's), overlap and check-in-window rules, roles, sign-up / leave / swaps, the free volunteer place (`givePlace` / `releasePlace`, `VolunteerSlot.registrationId`), QR and manual check-in (kids-room roles start a `KidsRoomDuty` with `fromRoster`), `rosteredForRooms` (used by the kids board), messages, the `volunteers` reminder job, hours served, and the privacy parts (`exportVolunteering`, `forgetVolunteer`). Pure parts tested in `tests/volunteers.test.js`. - `reservedOptionIds` / `publicOptions` there: the kids and volunteer tickets are left out of public event pages and refused on public registration (`eventController`, `registrationController`). **A new staff-only ticket type should be added to `reservedOptionIds`.** - `controllers/volunteerController.js` + `routes/volunteerRoutes.js` (`/api/volunteers`); campus resolvers `servingRole` and `volunteerSlot`; sign-ups, new roles and assigning are in `readOnly.js`. - Swaps: no approval — accepting moves the slot at once (claimed with an `updateMany` on `status: 'open'` so two people can't both take it); `tellOrganisers` emails `getEventNotifyEmails(event)` (notify recipients, else the creator), not the registrations inbox. - The check-in QR holds `SERVE-`; the page encodes it as a URL (`/serve/check-in?code=…`) so phone cameras open it directly. - Frontend: `lib/volunteers.ts`, `components/volunteers/{RosterSheet,CheckInQr}.tsx`, pages `dashboard/supervisor/volunteers` (roles, QR, ticket, hours), `dashboard/staff/volunteers` (the day), `dashboard/user/serving` (`?event=` opens one event — the shareable sign-up link), `serve/check-in`. - e2e: `volunteers.spec.ts` on the seeded hidden "E2E Serving Sunday" (role, ticket hidden publicly, sign-up, cover request, staff take over, QR check-in, roster). ## Where copying an event lives (1.47.0) - The copy is made in the browser: `EventModal` in `app/dashboard/supervisor/events/page.tsx` takes `source` (create mode, `cloning`), fills its state from it (`cloneOptions` leaves out the kids and volunteer tickets and all ids; cancelled sessions dropped; sessions keyed by the source's ids so late joining still points right; sections loaded and mapped onto the copied options; feedback questions without the sent/answered state), and `moveAllDates` shifts every date for "New start". It saves through the normal create path, so **a new field on the event form is copied automatically** if it's initialised from `base`. - What the form doesn't hold is copied by the server afterwards: `utils/eventClone.js` (`copyEventSetup`: allocation sets/groups except `kidsRoomSetId`, costs for admins only since costs are admin-only) via `POST /api/events/:id/copy-from`. Tests: `tests/eventClone.test.js`, e2e "copy an event" in `supervisor.spec.ts`. ## Where event series live (1.47.1) - `backend/src/utils/series.js` — input cleaning, `seriesForEvent`, `nextInSeries` (next public event starting later), `splitEvents`, follow/unfollow, the `series` job (`runAnnounceJob`: public, not started, `seriesAnnouncedAt` null → claimed, then followers filtered with `filterRecipients` as news), `exportFollows`. Tests: `tests/series.test.js`; e2e `series.spec.ts`. - `controllers/seriesController.js` + `routes/seriesRoutes.js` (`/api/series`, campus-independent: the list filters each series' events by scope). Event create/update take `seriesId`; changing it clears `seriesAnnouncedAt` so the new series' followers hear. - `SeriesFollow` is personal data: in `anonymiseUser` and `exportUserData`. No retention rule of its own — follows go when the account is anonymised. - Frontend: `app/dashboard/supervisor/series`, `app/series/[slug]`, `components/events/SeriesLinks.tsx`, `FollowSeriesButton.tsx` (asks the API itself: the page is cached for everyone), the Series box in the event editor. Series pages aren't in the sitemap yet (no public list endpoint). ## Where season passes live (1.47.3) - `backend/src/utils/seasonPass.js` — `splitCents` / `itemShares` (the price over the events by normal price, whole cents), `notOnSale`, `passView`, `cleanPassInput`, `buyPass` (advisory lock per pass, stock checked per item, a registration per event with a tranche at the share), `startPassCheckout` (checkout metadata `{ type: 'season_pass', purchaseId }`), `recordPassPayment` (called from `payments/webhook.js` `recordSucceededPayment`; `allocate` pays each registration what it owes; first Payment carries `externalId`), `notOnSeasonPass` (route guard on options edit and coupons), `exportPurchases`. Tests: `tests/seasonPass.test.js`; e2e in `series.spec.ts`. - `refreshPricingForRegistration` skips pass registrations; `payments/status.js` treats a pass checkout as paid once its purchase is. - Frontend: `components/series/SeasonPassesPanel.tsx` (Event series page), `components/series/SeasonPassOffers.tsx` (series page: buy, "Your passes", Pay now). - Not built yet: buying a pass at the door or by staff, cancelling a whole purchase in one go (staff cancel and refund each event's registration), one combined payment email (each event's payment sends its own). ## Where outbound webhooks live (1.48.0) - **Noticing:** `backend/src/config/db.js` wraps the Prisma client with `$extends` query hooks (registration create/update to paid or cancelled, payment create, ticketUsage create, user create, event create/update to public). **New code gets webhooks for free** as long as it writes through `prisma` (`updateMany` isn't hooked). Hooks only call `notice`; never put slow work there. - `backend/src/utils/webhooks.js` — event types, the in-memory queue (`notice` → `flush` after 1.5 s, which re-reads the record and skips it if it changed back), payload builders (kids/volunteer tickets left out), `send` (claim, SSRF check, sign, 10 s timeout, retry schedule), `runJob` (`webhooks` job: due retries, stuck sends, 30-day prune), `resend`, `sendTest`. Queued events are lost if the process stops in that 1.5 s (no outbox table yet). - `controllers/outboundWebhookController.js` + `routes/outboundWebhookRoutes.js` (`/api/outbound-webhooks`, admin). Operator register entry per endpoint (`operatorId`). - **Adding an event type:** add it to `EVENT_TYPES`, a case in `buildPayload`, a hook in `db.js` if needed, and a line in `dataShared` (operator register text). - Frontend: `components/admin/WebhooksTab.tsx`. Tests: `tests/webhooks.test.js`, e2e `webhooks.spec.ts` (runs a receiver on localhost:5199; e2e backend has `WEBHOOKS_ALLOW_PRIVATE`). ## Demo data (1.48.2) - `backend/scripts/set-demo.js` builds everything in memory and writes it with `createMany` in one transaction (so no webhooks fire). `PROFILES` says which of the six upcoming events, which past events (by title) and which extras (`series`, `courses`, `conference`, `kids`, `volunteers`) each profile gets, and whether campuses are on. **A new feature that's worth demoing** gets a builder and an extra; add its tables to `INSERT_ORDER` (parents first). - Keep jobs quiet: set anything a job would act on as already done (`seriesAnnouncedAt`, `remindedAt`, certificates issued). Demo people use @example.com and no phone numbers. - `clearData` truncates every table except settings and users, but deletes (not truncates) tables that `User` points at — TRUNCATE CASCADE would empty `User` with them. - Tried by seeding all four into a throwaway database and calling the API (events, series page and report, season pass, kids board, roster, attendance registers, certificate check, cashups, campus scoping). ## Where the dashboard and palette live (1.49.0) - `backend/src/utils/dashboard.js` — `todaysEvents`, `moneyIn`, `pendingItems` (each item counted separately, failures logged and skipped; role-only items for admins), `search` (+ `amountOf`). Everything goes through `eventWhere(scopeFor(req))`. Routes: `routes/dashboardRoutes.js`. **A new "something needs doing" count** goes in `pendingItems` (with its link and the `order`). - Frontend: `components/dashboard/TodayPanel.tsx`, `components/shared/CommandPalette.tsx` (mounted in `app/dashboard/layout.tsx`; `CommandPaletteButton` on the dashboards), `lib/commandPages.ts` — **a new page or setting tab should be added there** with its roles. - Deep links read `window.location.search` once on load (no Suspense needed). - Tests: `tests/dashboard.test.js`, e2e `dashboard.spec.ts`. ## Where bulk actions live (1.49.1) - `backend/src/utils/bulkRegistrations.js` — `runBulk` checks the input (≤ 500, licence read-only for payments and moves) and runs one action per registration, collecting a result for each. Most actions **call the existing Express handlers in-process** (`call(handler, req)`, with the original request's user, headers and socket so audits keep the IP): `createPayment`, `cancelRegistration`, `allocationController.assign`, `emailEventAttendees` / `whatsappEventAttendees` (new `filter.registrationIds`). **Change a rule in those handlers and bulk follows.** - Moving tickets is its own code (`moveOption`): the edit handler refuses to remove issued tickets, so the lines are re-pointed in place (tickets and QR codes kept), repriced with `resolveOptionPrice`, attendees moved, then `updateRegistrationStatus`. - Frontend: `components/admin/RegistrationBulkBar.tsx` on `app/dashboard/admin/registrations`. Export goes through `/api/reports/excel` (access-logged). Tests: `tests/bulkRegistrations.test.js`, e2e `bulk.spec.ts`. ## Saved filters (1.49.2) - `backend/src/utils/savedFilters.js` (`PAGES` is the list of pages with saved filters; values are cleaned to simple types) + `routes/savedFilterRoutes.js`. Removed in `anonymiseUser`. - `components/shared/SavedFilters.tsx` takes the page's current filter values and an `onApply`; `skipDefault` when the URL already says what to show. **Adding it to another list page:** add the page to `PAGES` (and the component's `page` type), then pass the values in and apply them out. - e2e `saved-filters.spec.ts` (deletes what it saves). ## Accessibility (1.50.0) - **Popups:** use `components/shared/ModalOverlay.tsx` (`labelledBy` = the heading's id, `onClose`, `closeOnBackdrop`) instead of a bare `fixed inset-0` div — it gives the dialog role, focus trap, Escape and focus return. Radix `ui/dialog` is fine too. - **Fields:** tie every visible `