> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session05-production-hosted-validation-and-deploy-smoke/implementation_summary.md). # Implementation Summary **Session ID**: `phase08-session05-production-hosted-validation-and-deploy-smoke` **Phase**: 08 - Release Hardening and Legacy Decommission **Status**: Complete and validated **Completed**: 2026-05-31 **Validated**: 2026-05-31 *** ## Summary Session 05 implemented the production-hosted validation gate for deployed release surfaces. The new root command is: ```bash npm run release:hosted-smoke ``` The command validates configured production targets with sanitized output: * `public-demo`: Cloudflare Pages public demo shell, `sw.js`, cache-version evidence, local endpoint leak markers, and raw repository asset leak markers. * `warroom-worker-custom`: custom-domain Worker `/health` metadata, service id, app-level rate-limit posture, and deployment type. * `warroom-worker-workers-dev`: workers.dev Worker `/health` metadata, service id, app-level rate-limit posture, and deployment type. * `app-shell`: optional production app shell, unavailable/no-claim by default because no production app host is configured. No hosted auth, hosted storage, analytics capture, public replay hosting, push delivery, remote access, Cloudflare Tunnel, hosted diagnostics, production account behavior, certification, or trusted unified erasure was activated. *** ## Files Changed * `scripts/check-production-hosted-smoke.mjs` - Added production-hosted smoke validator, strict URL validation, sanitized reporting, no-network mode, target selection, timeouts, and failure mapping. * `tests/productionHostedSmoke.test.ts` - Added 15 focused Vitest tests using injected fetch fixtures. * `package.json` - Added `release:hosted-smoke`. * `.spec_system/PRD/phase_08/production_hosted_validation_evidence.md` - Added sanitized evidence artifact. * `scripts/README_scripts.md`, `docs/deployment.md`, `docs/release.md`, `docs/hosted-services.md`, `docs/environments.md`, `docs/privacy-and-security.md`, `docs/runbooks/war-room-operations.md`, `apps/warroom/README_warroom.md`, `apps/web/README_web.md`, `public-demo/docs_public-demo/deployment.md`, and `public-demo/docs_public-demo/validation.md` - Added command usage, no-claim boundaries, and production-hosted evidence wording. *** ## Verification Passed: * `npm run release:hosted-smoke -- --no-network --json` * `npx vitest run tests/productionHostedSmoke.test.ts` * `npx biome check scripts/check-production-hosted-smoke.mjs tests/productionHostedSmoke.test.ts package.json` * docs/no-overclaim grep review * ASCII scan over changed scripts, tests, docs, and spec artifacts * LF/CR scan over changed scripts, tests, docs, and spec artifacts * `git diff --check` *** ## Residual Risks * No live production network smoke was recorded in this implementation session; the evidence artifact records credential-free no-network no-claim results. * `app-shell` remains unavailable/no-claim until an explicit production app URL is configured and validated. * Cloudflare dashboard constraints remain summarized only; raw dashboard/API output is not tracked. * Session 06 still owns mobile/accessibility evidence and certification no-overclaim wording. * Session 08 must either record safe live network smoke results or carry the no-claim states into final release closeout. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session05-production-hosted-validation-and-deploy-smoke/implementation_summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.