Production diagnostic denied and cleanup verified with scheduling activation still gated
Coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local executed the reviewed bounded Platform production diagnostic plan. ADR-0048 remains open. No production scheduling capability or resource-read feature was enabled, no migration ran, and no business endpoint was called by the diagnostic procedure. Existing application traffic and cron activity continued independently.
The first exact Git-backed deployment, dpl_C8HWXqqh4xMyP9RJ9ffPpobwffDQ at 4af8f419dfb9cb6c81d2f18c173824b740f21bab, reached Ready but omitted the requested deployment-scoped environment overrides. The coordinator stopped before any approval write or authenticated diagnostic request, restored the prior Ready deployment at 3909dacbdd9070b365f593c6b898c2d8704c0f7b, and verified the alias, unchanged public key and diagnostic route 404.
The revised plan created only two temporary production project settings, SERVICE_AUTH_CUSTODY_WINDOW_ID and SERVICE_AUTH_CUSTODY_ENABLED. Their exact values and created record IDs were verified. Deployment dpl_HSzHYduyYwMnt9dRHpL8vDYyzC47 at the same reviewed 4af8f419 source reached Ready off the production alias, with both runtime environment names present. Its 226 build-log entries confirmed the exact command npx prisma generate && next build and no migration execution. Both temporary project records were deleted and verified absent before deliberate promotion to the canonical alias.
Window 1a2fdfb0-47fa-4c2b-89a3-c2768ccd247d made exactly one authenticated diagnostic POST. The owner-approved immutable approval row persisted, but the diagnostic returned HTTP 404 and no reservation appeared. No comparison result, production key-pair proof or runtime database binding was established. The window is not retried and its approval remains immutable. Its fixed end is 2026-10-03T06:25:06.963Z.
The coordinator restored the previous deployment while cleanup built, then promoted the reviewed wrapper-free cleanup source d7f77314d709a730c6711c8c4423cc1e8a6b971d as dpl_6YCAaQtDfJGBhcrvdU7FkChHaujQ. Cleanup is Ready on platform.sguildswim.com. Its 225 build-log entries confirmed the same no-migration command. Verification confirms the wrapper is absent from source, the canonical diagnostic POST returns 404, custody project and runtime settings are absent, the public key is unchanged, and the four new scheduling enablement flags remain absent and disabled by default. ADR-0049 person resolution remains enabled. Deliberate promotion restored automatic production domain assignment. Main was not merged. The Platform owner independently refreshed Render through its authenticated UI: dep-db05l8jm8hqs73cq01i0 remains Live at 3909dac on main.
The retained diagnostic deployments still retain their immutable source snapshots. Their generated URLs returned deployment-protection redirects, which are not handler 404 evidence. They must not be re-promoted or receive another approval for their fixed windows. The completed cleanup does not erase the failed attempt.
Read-only investigation found a concrete Next 16.1.4 adapter defect: a real zero-byte HTTP POST has a non-null body stream, while the diagnostic rejected any non-null stream before reservation. Actual logs confirm the intended deployment returned 404 inside the approved interval. This defect is consistent with the failure, but the exact production denial branch was not logged, so origin, runtime metadata and serving-database binding remain unproven. A bounded empty-stream check, actual framework-adapter regressions and fixed private denial telemetry are under separate review. No origin or authorization check is being relaxed.
Platform cleanup source passed CI run 37102314735, 506 unit tests, 32 identity and three geography integration checks, typecheck, lint and module guardrails. Production evidence is retained under the primary Platform checkout's .tmp/adr-coordination/ADR-0050/production-custody-009/ and production-custody-010/; owner investigation and payload records are under docs/adr0050-production-auth-009/ through 011/ in its isolated checkout. Draft Platform PR https://github.com/sguild-admin/platform/pull/1 retains the reviewed source history.
Local scheduling progress is independent of this denied production diagnostic. The third prospective Sales original has an actual Delivery bind, deliberately lost successful reply, exact replay and settlement using the original allocated settlement ID. Coaching observed the actual protected booking. Platform independently matched the settlement exchange to its issuance audit, confirmation SHA256 549c6427b96bcd4a74c79d0280c4b6e87791b7d72683638d6e082083d832452b. Compensation, finalization, production workload identity, actual business-serving-role privileges, provider validation and activation remain open. No domain completion commitment is closed by this checkpoint.