Coaching combined production release is serving with scheduling protection disabled

Coaching authored this evidence for assignment ADR-0053/coaching/010, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local, shared release ADR-0048-scheduling-20261003. Root is the sole canonical publisher. This memo records the authorized additive migration and default-off deployment, not protection activation or completion of the shared scheduling proof.

Serving release

At 2026-10-03T10:16:01.208Z, deployment dpl_GJyiXJDWxWQUm1tHYoB62ZUFtpyT, source af63339ec1a1e9501cd133f3412b6ee2ab3e7ee7, was verified READY and serving in project prj_sKBkMlnYoqcu8EhvdLG8UD7zhz3q, team team_byXeghD9Vv0Kd5UKuKWBqQb9. The canonical coaching.sguildswim.com, project-default coaching-jack-allreds-projects.vercel.app, and existing coaching-six-beryl.vercel.app aliases all point to this exact candidate. The other seven aliases remain unchanged, established from the complete ten-alias inventory.

The Linux ARM64 Node 24 artifact has 430 regular files and 58 confined symlinks. Provider upload UIDs and source metadata were reverified before promotion. Artifact manifest SHA256 is e479b563a56482e2428411ce2418651268a87fe8ee8c01082ec86c8acf515d5d; generated Prisma schema SHA256 is d1ef73aae31c1dce8ccebd729028aeeca8604eae96493ba62b90418e93c12e91. Both CoachCreationAttempt and SchedulingProtectionObservation models are retained. ADR-0051 creation source and its migration remain unchanged from the prior serving baseline.

All 12 business environment rows and project settings remain unchanged. COACHING_SCHEDULING_PROTECTION_ENABLED remains absent, which is the consumer's disabled default, and COACHING_PROTECTION_WRITER_EPOCH remains absent. No diagnostic key, endpoint or flag was added. This release does not enable protection or authorize a production writer epoch.

Runtime verification and recovered attempts

Canonical read-only checks passed: root GET redirects to /dashboard with 307; unauthenticated Coach-creation entry redirects to Platform sign-in with 307; missing-Organization eligibility GET returns the expected 400 before invoking the business service; the temporary diagnostic path returns 404. No authenticated Coach creation, scheduling, financial or provider mutation was performed for this smoke. These checks establish routing, application handler and authentication-rail behavior, not a new end-to-end scheduling proof.

The project-default hostname retains its preexisting Vercel SSO redirect, 302 to vercel.com/sso-api; it is not an unauthenticated application-health endpoint. The third public hostname retains its 307 dashboard entry behavior. Exact per-host classifications match their observed baseline. No deployment-protection bypass or configuration change was used.

Two verification-script errors preceded the successful third attempt. The first guard incorrectly allowed only two production aliases to move, omitting the preexisting third alias that also pointed to the baseline. The second attempt passed canonical candidate health but incorrectly expected public application behavior from the protected project-default hostname. Each triggered the authorized exact-baseline recovery, with all ten original aliases restored and canonical health verified. Neither was evidence of an unhealthy candidate. Original results and exclusive claims are retained separately. The corrected alias and host-classification guards passed eleven tests; the third attempt used a distinct claim/result and completed without recovery.

Additive migration and transport evidence

Under the separate coaching/009 authorization, exactly one native Prisma deploy applied 20261003034000_scheduling_protection_observation, SQL SHA256 704f4a2cf9dcf6b666035727fa6c95a39620557f7affc779f2867542e769521d. Its journal entry finished at 2026-10-03T10:03:04.092Z. The full 20-entry journal, unchanged full-row digests for all 19 prior entries, identical second readback and no-pending inventory were verified. Fresh catalog evidence confirms six expected columns, the sole composite primary key, and zero observation rows. No migration was rerun during promotion.

The historical ops-surfaces checksum difference was resolved to an introductory comment-only edit with exact applied source recovered from Git. Historical SQL and journal entries were preserved. The separate public-schema attendance journal was not changed or treated as an automatic Coaching gate.

Native Windows read-only inspection verified the official direct database host with the pinned public Supabase CA and normal certificate/hostname validation. The actual role is postgres; no alternate role, role default or grant was introduced. Exact baseline journal/catalog correlation and native Prisma read-only assertions established the CA and startup timeout path before the authorized migration. Earlier session-pooler timeout-option mismatch and TLS trust stops remain in the evidence. No raw credential is included in the packet.

Evidence, rollback and remaining commitment

The immutable coaching/009 packet is at C:/Users/jallr/.codex/worktrees/adr0053-coaching-release/coaching/.tmp/staging009/packet.json, SHA256 1ceafb0bdab276d49b898727c510e2e9f25a325000f52ee439f39bd6a130a40f. Promotion attempt records, health, guard tests, full alias readbacks and this owner memo are under the sibling .tmp/promotion010/ directory; the accompanying final packet supplies their exact hashes.

Before protection activation, the verified recovery target remains dpl_FadadtUTMUZJV3v7GyHzF8Y2H6jF, source ecd830069ed3f4deff342359b21341dabc77c529. A binary rollback preserves the additive table, all existing data and immutable migration evidence. After protection becomes required, do not independently disable the consumer or restore legacy affirmative availability. Root must retain compatible observation/recovery and coordinate admission pauses and any compatible rollback.

Live-ledger discovery found no narrower pending Coaching commitment satisfied solely by this default-off deployment. 2026-10-02-coaching-adr-0053-protection-consumer-position::0 remains working. Its completion still requires the accepted production Delivery observation, compatible writer epoch, Platform workload policy, bounded coherent consumer proof, relevant caller cutover and coordinated activation. No commitment status is advanced by this memo.