Sign-in steps (password, sign-up, email code, two-step sign-in and its
setup with recovery codes, privacy notice, news question), forgot and
reset password, the account page, admin (people, deletions, church
profile, linked products, settings, notice, licence, audit) and setup.
Strict CSP with a nonce per page; church colours from the profile.
@crosscode/ui gets its first components (shell, card, fields, buttons).
Plan: roles stay in each product (asked 2026-11-18).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Site settings → Linked products (Connect, Show events from, Publish my
events), help, command palette.
- Events from linked products on /events, the home and campus pages, and
/events/linked/<product>/<id> (markdown with HTML off, canonical to the
origin, no JSON-LD, not in the sitemap).
- Event page JSON-LD from @crosscode/seo; lib/eventSchema.ts removed.
- Readiness check for linked products' sync; e2e spec with a fake
Church Website (not run yet: needs the e2e Postgres).
- crosscode: install and build the shared packages Events uses first
(an older tag still builds as before); scripts/tests/events.bats.
- Release notes, changelogs, handovers, hub-protocol.md, and the plan's
"Changes while building".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
EVENTS-2.4-PLAN.md: protocol v2 (public key in the v2 heartbeat, Hub 2.2.0),
Linked products and Connect (crosscode.link/1, contracts 1.4.0), the event
feed, showing sibling events, and packages/seo. Six decisions to confirm.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Root HANDOVER: phases 1b–1d released and VM tested, the nine bugs the VM
test found, rollout next. Events HANDOVER: 2.3.0, where two-factor and the
Hub-install pieces live. AGENT-1.0-PLAN and EVENTS-2.2-PLAN: tested and
released, the VM changes; ROADMAP §9 marked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ls1vMdni7EfytGYqQTprME
Events 2.2.0: the move into the monorepo and the crosscode script, plus
AI use in tokens and the backend under /api. Contracts 1.2.0: token
fields on the AI status. Agent phase 1d moves to contracts 1.3.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
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>