Current infrastructure tests run through local workerd and Alchemy dev: true. See local infrastructure testing for commands and current results. The cloud runs below are historical acceptance records.
Root accepted and integrated all five implementation units. The final integrated checkout passes 313 local tests and 1,633 assertions, build, typechecks, lint, and 29 real-cloud cases with 637 assertions. Independent cleanup verifies no disposable stage resources remain. These results establish implementation acceptance and controlled-provider behavior. Production readiness remains open for the live-provider and launch checks below.
| Record | Current reading |
|---|---|
| Alchemy CI/CD | Accepted bootstrap, guarded automatic releases, synthetic resident previews, and trusted close cleanup. Hosted activation remains unverified. |
| Effect review comments | Resolution of all 62 inline comments, API exceptions, and the corrected HTTP transport proof. |
| Foundation root review | Accepted foundation, raw HttpApi, native storage, reconstruction, and alarms. |
| Cache root review | Accepted cache and absolute command-deadline correction. |
| Twitch and release root review | Its final section accepts the corrected account and release implementation. Earlier failures remain historical. |
| Tenant and ingress root review | Its final section accepts ingress, Tenant execution, recovery, and cross-service deadline corrections. Integrated-root frozen installation and the subsequent 311-test/1,572-assertion pass are recorded separately from the initial missing-link setup failure. |
| Final integration | Unit 5 deletion, current configuration/docs, health, local workerd, final checks, and disposable-cloud evidence. Root review remains separate. |
| Final integration root review | Current integration status, independent checks, review verdicts, retained failed run, and final root acceptance. |
| Completed-alarm recovery | Exact completed-run HTTP verification, duplicate-request negative proofs, and native reconstruction after recovery. |
| Native alarm attribution | Initial instrumentation and a passing run that did not explain the historical failed global count. |
| Cloud helper evidence | Strict pre-execution readiness classification, native reconstruction, retained failures, and default discovery of all eight pure helper tests. |
| Tenant corrections | Historical failures and corrected native recovery, allocation observation, and live-dispatch joining. |
| Twitch deadline correction | Sixteen full signed-path clock tests and the narrow account correction. Later acceptance is in the root review. |
Owner records describe the revision and review state at which they were written. Read their later root reviews for acceptance. Historical failed deployments, setup failures, counts, and inconclusive causes remain evidence; a subsequent pass does not erase them.
Historical disposable cloud tests used unique per-worktree/run stages, real Workers and SQLite Durable Objects, Cloudflare-backed state, production application policy, and controlled HTTPS external providers. Their records retain exact checks and verified destruction. The current runner uses isolated local file state and workerd for integration acceptance.
Live Twitch authorization/EventSub delivery and timing, grants after onboarding-token expiry, Discord client privacy/registration/timing, remote CI/release configuration and execution, and observed launch cost remain NOT VERIFIED. Controlled-provider payloads and latency observations do not establish those live gates. Concrete next checks are in final integration and the operator guide. Do not put secret values or token-bearing authorization URLs in verification records.