> 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/tasks.md).

# Task Checklist

**Session ID**: `phase08-session05-production-hosted-validation-and-deploy-smoke` **Total Tasks**: 21 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31

***

## Legend

* `[x]` = Completed
* `[ ]` = Pending
* `[P]` = Parallelizable (can run with other \[P] tasks)
* `[SNNMM]` = Session reference (NN=phase number, MM=session number)
* `TNNN` = Task ID

***

## Progress Summary

| Category       | Total  | Done   | Remaining |
| -------------- | ------ | ------ | --------- |
| Setup          | 3      | 3      | 0         |
| Foundation     | 5      | 5      | 0         |
| Implementation | 9      | 9      | 0         |
| Testing        | 4      | 4      | 0         |
| **Total**      | **21** | **21** | **0**     |

***

## Setup (3 tasks)

Initial configuration and environment preparation.

### Cross-cutting

* [x] T001 \[S0805] Verify analyzer state, completed Sessions 01-04 prerequisites, Phase 08 routing, and cross-cutting package context before implementation (`.spec_system/PRD/phase_08/session_05_production_hosted_validation_and_deploy_smoke.md`)
* [x] T002 \[S0805] Review release/deployment/hosted-services/public-demo/War Room docs and record the production-hosted target baseline without copying credentials or raw dashboard values (`docs/deployment.md`)
* [x] T003 \[S0805] Create implementation notes and confirm this session validates deployed surfaces only, with no hosted auth/storage/analytics/push/remote/tunnel activation (`.spec_system/specs/phase08-session05-production-hosted-validation-and-deploy-smoke/implementation-notes.md`)

***

## Foundation (5 tasks)

Core structures and base implementations.

### scripts

* [x] T004 \[S0805] Define hosted smoke target records for public demo, Worker custom domain, Worker workers.dev, and optional app shell with no-claim unavailable defaults (`scripts/check-production-hosted-smoke.mjs`)
* [x] T005 \[S0805] Add URL validation and environment parsing that rejects unsafe schemes, credentials, query strings, fragments, localhost production targets, and malformed values with explicit error mapping (`scripts/check-production-hosted-smoke.mjs`)
* [x] T006 \[S0805] Add sanitized reporter helpers for issue codes, timing buckets, docs paths, safe host labels, unavailable states, and sensitive-output rejection (`scripts/check-production-hosted-smoke.mjs`)

### tests

* [x] T007 \[S0805] \[P] Create hosted smoke test fixtures for safe URLs, unsafe URLs, public demo responses, Worker health responses, unavailable app hosts, and sensitive output (`tests/productionHostedSmoke.test.ts`)

### package

* [x] T008 \[S0805] Add the root `release:hosted-smoke` npm script without changing existing release gate commands (`package.json`)

***

## Implementation (9 tasks)

Main feature implementation.

### scripts

* [x] T009 \[S0805] Implement public demo production checks for HTTPS shell load, service-worker script availability, cache-version evidence, local endpoint leak markers, and raw repository asset leak markers with explicit loading, timeout, malformed-response, and offline/fetch-failure states (`scripts/check-production-hosted-smoke.mjs`)
* [x] T010 \[S0805] Implement War Room Worker health checks for custom-domain and workers.dev targets with timeout, compact metadata validation, rate-limit posture validation, deployment-type validation, and failure-path handling (`scripts/check-production-hosted-smoke.mjs`)
* [x] T011 \[S0805] Implement optional app-shell checks that return unavailable/no-claim status when no explicit host is configured and validate supplied hosts without implying hosted identity or storage (`scripts/check-production-hosted-smoke.mjs`)
* [x] T012 \[S0805] Implement CLI flags for no-network mode, JSON output, target selection, timeout control, and nonzero exit behavior for blocking contract failures (`scripts/check-production-hosted-smoke.mjs`)

### .spec\_system

* [x] T013 \[S0805] Create sanitized Phase 08 production-hosted evidence artifact with target matrix, command usage, allowed unavailable results, residual risks, and no raw credential/dashboard output (`.spec_system/PRD/phase_08/production_hosted_validation_evidence.md`)

### docs

* [x] T014 \[S0805] Update release and deployment docs with hosted smoke command, target matrix, no-claim app-host behavior, rollback notes, and local/mocked evidence distinction (`docs/release.md`)
* [x] T015 \[S0805] \[P] Update hosted-services, environments, privacy/security, War Room runbook, War Room README, and web README with production-hosted validation boundaries and no hosted-service activation claims (`docs/hosted-services.md`)
* [x] T016 \[S0805] \[P] Update public-demo deployment and validation docs with production URL smoke expectations, service-worker evidence notes, and Cloudflare Pages rollback readiness (`public-demo/docs_public-demo/deployment.md`)

### tests

* [x] T017 \[S0805] Write unit tests for URL validation, target defaults, no-network summaries, public demo checks, Worker health checks, app-host no-claim states, timeout/fetch failures, and sanitized output (`tests/productionHostedSmoke.test.ts`)

***

## Testing (4 tasks)

Verification and quality assurance.

### Cross-cutting

* [x] T018 \[S0805] Run focused Vitest coverage for hosted smoke helpers and the no-network hosted smoke command (`tests/productionHostedSmoke.test.ts`)
* [x] T019 \[S0805] Run docs/no-overclaim grep review for production-hosted, hosted identity, analytics, push, remote, tunnel, trusted erasure, certification, and local/mocked evidence wording (`docs/release.md`)
* [x] T020 \[S0805] Run whitespace, ASCII, LF, and `git diff --check` validation over new scripts, tests, docs, and spec artifacts (`.spec_system/specs/phase08-session05-production-hosted-validation-and-deploy-smoke/implementation-notes.md`)
* [x] T021 \[S0805] Record command outcomes, evidence result, residual risks, and Session 06/08 handoff in implementation notes and update task checklist readiness (`.spec_system/specs/phase08-session05-production-hosted-validation-and-deploy-smoke/implementation-notes.md`)

***

## Completion Checklist

Before marking session complete:

* [x] All tasks marked `[x]`
* [x] All tests passing
* [x] All files ASCII-encoded
* [x] implementation-notes.md updated
* [x] Ready for the validate workflow step

***

## Next Steps

Session complete. After `updateprd`, the next workflow command is `plansession` while Phase 08 still has unfinished sessions, or `audit` once Phase 08 is fully complete.


---

# 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/tasks.md?ask=<question>&goal=<endgoal>
```

`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.
