oidc-provider 9.13.3 with PKCE, ES256, crosscode.identity/1 claims and
back-channel logout; clients are the linked products (Connect). Sign-in
steps (password, sign-up, email check, 2FA and its setup, privacy notice,
news question, password reset) survive to the product. Account page and
admin API, church profile, export and deletion fan-out, Hub v2 client,
jobs. End-to-end tests with a test product on openid-client.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Hub client: register and heartbeat on protocol v2 with the site's
Ed25519 key (sent on the heartbeat until the Hub has it); falls back to
v1 for a day if the Hub refuses v2, so the licence always refreshes.
- crosscode.link/1 Connect / Disconnect, both directions, trusted through
the Hub's cached linkedProducts (ProductLink, LinkNonce).
- GET /api/feed/v1/events from FeedEntry (go-live, closing and selling
out are changes; deactivated events go in deleted), event.changed to
connected products, and showing their events (ImportedEvent).
- /api/v2/linked-products, /api/v2/linked-events; /events/:id/full gains
crosscodeEvent and priceRangeCents for the JSON-LD.
- Contracts: FEED_PATHS, typesVersions for @crosscode/contracts/signing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- crosscode.link/1 (link.connect / link.connected / link.disconnect), with
signLink / verifyLink, PEM conversion, link secrets and nonces.
- The v2 heartbeat can carry the install's publicKey; the reply says
saved / matches / mismatch (Hub 2.2.0). Never a failed heartbeat.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Jobs of fixed types with strict argument schemas, signed by the Hub with
Ed25519 over canonical JSON. Agent requests signed with the server's
Ed25519 key. Config sealed to the server's X25519 key (X25519 + HKDF +
AES-256-GCM; Node has no XSalsa20). Exports encrypted with a key that
only travels in the download link.
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>
- 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>