Central servers only get the agent (install.sh --central), not the crosscode script, but a central agent accepts status jobs and ran `crosscode status` for them, which failed with `spawn /usr/local/bin/crosscode ENOENT`. A central agent now reports its own stats (frps and the agent version) for status; church servers still run crosscode status. Also ignores temp/ (local screenshots). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.6 KiB
5.6 KiB
Changelog
Each package and app has its own section and its own tags (contracts@1.0.0, accounts@1.0.0, …).
agent@1.0.1 - 2026-11-18
- A
statusjob on the central server is answered by the agent itself (its stats, frps and the agent version). It used to runcrosscode status, which central servers don't have, and failed withspawn /usr/local/bin/crosscode ENOENT.
events@2.3.0, contracts@1.3.0, agent@1.0.0 - 2026-11-17
Phase 1c (authenticator-app sign-in) and phase 1d (docs/AGENT-1.0-PLAN.md): installs, updates and uninstalls from the Hub (Hub 2.1.0) through the agent. Tested end to end on a VM (church server + central server + Hub, AGENT-1.0-PLAN §13 and EVENTS-2.2-PLAN §6).
Events (2.3.0)
- Two-factor with an authenticator app, and recovery codes. The env template, the church export
and registering by itself from
HUB_LICENCE_KEYfor installs from the Hub. Details inapps/events/CHANGELOG.md.
Contracts (1.3.0)
crosscode.agent-job/1(fixed job types, strict arguments),crosscode.agent-report/1,crosscode.script-report/1,crosscode.agent-stats/1, the agent join / poll requests,crosscode.env-template/1andcrosscode.church-export/1.@crosscode/contracts/signing: Ed25519 jobs (over canonical JSON) and agent requests, config sealed to a server (X25519 + HKDF + AES-256-GCM), export encryption.
Agent (1.0.0)
apps/agent: polls the Hub, checks every job (pinned key, server, time window, replays, type, arguments) and runs the crosscode script for it; stats every minute; listens on nothing. Install script, systemd unit, self-update with automatic revert.
crosscode script
--jsonreports and--configon every command;.envfiles from each release's env template (appended to, never rewritten, on deploy);install --frpwith Hub-given ports, a database on another server, and clean-up on failure; frpc.ini blocks;restart,export,uninstall,purge.- Fixed in the VM test:
adoptapplies a release's new migrations in the switch-over; a failed migration is marked rolled back so later deploys aren't blocked; frpc is restarted once when its admin lines are first added; a site's PM2 always runs under its own systemd unit (pm2-<user>), so restarting or updating the agent never stops a site; tags are fetched with--force.
events@2.2.0, contracts@1.2.0 - 2026-11-17
Events
- Cross Events 2.2.0, the first release from this repo (
apps/events, ROADMAP-v3 phase 1b): moved in with its history, npm workspaces with one root lockfile, and thecrosscodescript (deploy,status,install,adopt) inscripts/. Also AI use shown in tokens instead of rand, and everything the backend serves under/api. Details inapps/events/CHANGELOG.md.
Contracts
- AI status (Hub protocol §3b): optional
usedInputTokens,usedOutputTokens,capInputTokens,capOutputTokens(Hub 2.0.1). Churches see tokens; the cents stay for the Hub and older installs.
Docs
- The roadmap (
docs/ROADMAP-v3.md) and the Hub protocol (docs/hub-protocol.md) move here fromhope-events/docs/, since they cover every product. New:docs/HANDOVER.md(where each phase stands) anddocs/EVENTS-2.2-PLAN.md(phase 1b, Cross Events into the monorepo).
contracts@1.1.0 - 2026-11-04
Contracts
- Hub protocol v2: optional
requireson a release ([{ product, version }]), the sibling versions it needs. The Hub refuses an update request with409 REQUIREMENT_NOT_METuntil they're met (Hub 2.0, ROADMAP-v3 §5). Optional, so the schema stays/1-compatible.
contracts@1.0.0 - 2026-11-04
Monorepo
- Set up: npm workspaces (
packages/*,apps/*), shared TypeScript, ESLint and Jest setup, andnpm run check(lint, typecheck, tests and build). packages/contracts: package set up with a dual CommonJS / ESM build (tsup) and the schema-name helpers every contract uses (crosscode.<name>/<major>).packages/ui,apps/accounts,apps/website,apps/app: placeholders.
Contracts
crosscode.event/1andcrosscode.event-feed/1: the event, the feed response and theevent.changedwebhook. Checks thatstartsAt/endsAtmatch the sessions and that only Cross Events takes registrations.parseEventFeedskips and reports a bad event instead of failing the whole feed;eventKeyis the cross-product id.crosscode.church/1: the church profile (branding, campuses, service times, contact, links).crosscode.identity/1: sign-in claims (no roles; 2FA method including the authenticator app, news consent, privacy notice version) and theuser.updated,user.deleted(with a "deferred" reply) anduser.exportback-channel calls.- Sign-in return:
isSafeReturnPath,safeReturnPath,encodeState/decodeStateandisRegisteredRedirectUri, so every product sends people back to the page they came from in the same safe way. - Hub protocol v2:
producton register and heartbeat, stats per product (Events as in v1; Website storage and App active-member bands for billing), the install's public key, linked products in the replies,customerId/productin the licence token. @crosscode/contracts/signing(Node only): the Hub's HMAC scheme for the Hub and product links.- Sample payloads for every contract in
samples/, checked by the tests. - JSON Schema (draft 2020-12) for every contract in
schemas/, generated from the zod schemas bynpm run build(scripts/json-schemas.cjs), for consumers that don't use TypeScript or zod. A test checks the files match the zod schemas and that every sample passes them (Ajv). Checks JSON Schema can't express (e.g.startsAtmatching the sessions) only run in zod.