coh — World-class Polish Sprint
Sprint date: 2026-05-19 Target repo:Latimer-Woods-Tech/coh (the five-stream personal brand platform at https://cypherofhealing.com / https://api.cypherofhealing.com)
Parent doc updates: docs/APP_SCOPE_REGISTRY.md · docs/service-registry.yml · docs/GAP_REGISTER.md (G41–G48)
Why this sprint exists
coh shipped to production WITHOUT waiting for the W360-032 template buildout. All five product streams (Chair / Vault / Academy / Stage / Inner Circle) are live at the route level, 31 commits in the last 30 days, CI green, custom domains attached. But the underlying conformance score sits at 25/100 against a world-class threshold of 70 — the app is shipped at a sub-bar standard and the gap needs explicit retroactive closure rather than a silent demotion of expectations. Three parallel teams run today to close that gap in one synchronized sprint instead of three sequential weeks.Parallel teams
PR links
The Factory PR (Team C, this PR) is the meta PR that documents the sprint; the coh PRs are the actual shipped changes.
Target bar (definition of world-class for coh)
A “world-class” coh ships when all of the following hold simultaneously:- CI: Push to
mainrunstypecheck+testBEFOREwrangler deploy. Deploy job hasneeds:test job. (closes G41) - Test coverage: ≥90% lines, ≥85% branches measured by Vitest coverage report. Stretch target this sprint = 70%; world-class = 90%. (closes G42)
- Observability: Sentry initialized via
@latimer-woods-tech/monitoring.sentryMiddleware(c.env.SENTRY_DSN). A test error in production appears in the Sentry project inbox within 60s. (closes G43) - No
*.workers.devURLs in user-facing code:grep -r '\.workers\.dev' coh/web/returns zero hits in.html,.tsx,.tsfiles. All frontend API calls go viahttps://api.cypherofhealing.com. (closes G44) - No dangerous prod endpoints:
/__db/resetand/__db/stripe-bootstrapeither deleted in prod or wrapped inc.env.ENVIRONMENT !== 'production' && return 404.curl -X POST https://api.cypherofhealing.com/__db/resetreturns 404. (closes G45) - Docs hygiene: Root of repo has ≤5
.mdfiles (README + LICENSE + CHANGELOG + CONTRIBUTING + SECURITY). All operational docs live incoh/docs/runbooks/. README is internally consistent (no broken intra-repo links, no contradictory deployment instructions). (closes G46; deferred — stage-3) - Service registry: Factory
docs/service-registry.ymlhas acohentry with verifiedworkers_dev_url(curl proof attached to PR). (closes G47 — this PR) - Cohesion score: ≥70/100 on the
cypher-healingrow indocs/conformance/summary.md. Currently 25/100. (closes G48 as a roll-up) - Naming: Resolved 2026-05-19 in coh#50 — wrangler.jsonc was authoritative;
cypher-of-healing-apiis the canonical worker name and CLAUDE.md was the stale artifact. CLAUDE.md updated to match. - Dual-domain alias: Resolved 2026-05-19 in coh#50 — both
cypherofhealing.comandcipherofhealing.comare intentional aliases of the same product (DNS for both resolves to Cloudflare anycast). Worker custom_domain routes now bind both API hostnames; CORS allows both frontend origins.
Acceptance criteria for THIS PR (Team C)
-
docs/APP_SCOPE_REGISTRY.md:cohrow reflects shipped reality (not ”📚 Planning”) -
.bootstrap/cypher-healing/FUNCTIONS_MATRIX.md: header note documents the two-repo naming collision -
docs/service-registry.yml: newcohentry added with all bindings, secrets, vars, critical endpoints -
docs/GAP_REGISTER.md: G41–G48 added with severity tier + assigned owner -
docs/runbooks/coh-world-class-sprint.md: this file exists and is linked from all four artifacts above - 17 stale coh
agent-taskissues triaged (closed if shipped, commented +wc-polishlabel if partial, untouched if unstarted) - Sprint tracking issue created in
Latimer-Woods-Tech/cohtitled “World-class sprint — coh — 2026-05-19” with the three PR links as a checklist - Single Factory PR opened against
mainwith all six commits
Acceptance criteria for the SPRINT as a whole
Sprint is “done” when all target-bar checkboxes above are checked AND:- Three sprint PRs merged (Teams A + B + C)
- coh deploy verified post-merge:
curl https://api.cypherofhealing.com/healthreturns 200 - coh frontend verified post-merge:
curl https://cypherofhealing.com/returns 200 with no.workers.devrequests in the network tab - Sentry project receives a synthetic test event from production
- Test coverage report attached to Team B PR shows ≥70% lines
- Cohesion score in
docs/conformance/summary.mdreflects the new state (or, if the conformance job runs on a cron, the next run after merge shows ≥40 — gradual improvement is acceptable as long as the underlying gaps are closed and the score will follow)
Rollback
If the sprint reveals that any of the three teams is destabilizing production:- Revert that team’s merge commit on
main(the others can stay if independent) - Re-open the matching gap(s) in
docs/GAP_REGISTER.mdand re-assign for the next sprint - Update this tracker with a postmortem section
- File an incident report in
docs/runbooks/INCIDENT.md
git revert.
Contradictions found during reconciliation — RESOLUTIONS
These were surfaced during the sprint; resolutions ratified 2026-05-19:-
Two-repo name collision — RESOLVED:
Latimer-Woods-Tech/cohis the live product.Latimer-Woods-Tech/cypher-healingis the older multi-tenant scaffold and its spec’d hostnameapi.cipherofhealing.comis now an alias of coh (coh#50). Default disposition forcypher-healingrepo: RETIRE unless someone makes the case for keeping it. Service-registry note updated accordingly. -
Worker-name disagreement inside coh — RESOLVED:
wrangler.jsoncwas authoritative; the canonical worker name iscypher-of-healing-api. coh#50 fixes CLAUDE.md to match (was stale, said “coh”). Service-registrynamefield corrected in this PR amendment. -
FUNCTIONS_MATRIX scope — DEFERRED:
.bootstrap/cypher-healing/FUNCTIONS_MATRIX.mddescribes the OLDER cypher-healing scaffold, not coh. The 36 unverified rows cannot legitimately be marked “shipped” against coh’s routes — different worker. A fresh.bootstrap/coh/FUNCTIONS_MATRIX.mdis a follow-up PR. -
Dual-domain ratification (NEW, 2026-05-19): Both
cypherofhealing.comandcipherofhealing.comare intentional aliases. This dissolves the naming collision noted in #1 from “two competing products” to “one product, two domain spellings” — cleaner from a customer-acquisition standpoint (catches typos in either direction). - Issue count off by 2 (minor): Brief said 19 stale issues; only 17 actually open at sprint start (3 of the 2026-05-08 wave were already closed pre-sprint).