Adds a separate sonicjs-client-backend Cloudflare Worker at client-backend.sonicjs.com so caching can be tuned independently from demo.sonicjs.com.
Resources
Resource
Value
Worker name
sonicjs-client-backend
Route
client-backend.sonicjs.com/*
D1 (shared)
sonicjs-demo — same content, no re-seed needed
R2 (shared)
sonicjs-demo-media
KV (isolated)
fa15ce6927af43af9149e926631d7ad5 — independent cache state
Changes
my-sonicjs-app/wrangler.client-backend.toml — new worker config
.github/workflows/deploy-client-backend-cms.yml — deploys on every push to main that touches packages/core/** or my-sonicjs-app/**, same trigger as deploy-demo-cms.yml; auto-creates DNS record on first CI run
.github/workflows/deploy-demo.yml — sets VITE_CMS_URL=https://client-backend.sonicjs.com for the Pages build; fixes project name (sonicjs-client-directory)
DNS
The workflow auto-creates the client-backend AAAA 100:: proxied record via CF API on first run. If the CI token lacks DNS write permission, add it manually: CF Dashboard → sonicjs.com DNS → Add AAAA client-backend 100:: proxied.
Summary by cubic
Adds a separate sonicjs-client-backend Cloudflare Worker at client-backend.sonicjs.com so caching can be tuned independently from demo.sonicjs.com. The demo Pages build now points at the new backend.
Changes
The new worker shares sonicjs-demo D1 and sonicjs-demo-media R2 (same content, no re-seed) but has an isolated KV namespace for cache state.
A new CI workflow deploys on the same triggers as the demo CMS workflow and auto-creates the DNS record on first run.
The demo Pages deployment now uses the corrected project name sonicjs-client-directory.
Deployment
If the CI token lacks DNS write permission, add the AAAA client-backend 100:: proxied record manually.
If the CI token lacks Workers Routes edit permission, the worker uploads but route registration fails; grant Zone > Workers Routes > Edit.
Confidence Score: 3/5
Fix the DNS lookup and first-deployment route checks before merging, and satisfy the secret-storage and browser-test requirements.
Adds a separate Worker for the employee directory and points its Pages build at the new backend.
A separate client backend runs at its own Cloudflare address.
The employee-directory site now sends CMS requests to the client backend.
lane711 explicitly allows manual DNS setup when the token lacks DNS write permission. That warning is intentional; the separate unguarded lookup remains an issue.