> 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/phase16-session03-automated-checks-and-build-gates/tasks.md). # Task Checklist **Session ID**: `phase16-session03-automated-checks-and-build-gates` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-02 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1603]` = Session reference (16=phase number, 03=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 8 | 8 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **20** | **20** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1603] Verify Session 03 prerequisites, completed Sessions 01 and 02, Node/npm baseline, and package context (`.spec_system/PRD/phase_16/session_03_automated_checks_and_build_gates.md`) * [x] T002 \[S1603] Create implementation notes with command matrix, evidence status labels, script coverage assumptions, and static-output gate checklist (`.spec_system/specs/phase16-session03-automated-checks-and-build-gates/implementation-notes.md`) * [x] T003 \[S1603] Inspect root and website package scripts for install, format, lint, typecheck, build, preview, and static-check coverage with deterministic command names (`package.json`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S1603] Map website package command coverage for Astro typecheck, build, preview, and static checks, adjusting package scripts only if coverage is unclear (`public-website/package.json`) * [x] T005 \[S1603] Extend built-site checker file discovery and route/content helpers for deterministic RSS, sitemap, robots, metadata, and draft checks with bounded extensions and relative-path failures (`scripts/check-public-website-links.mjs`) * [x] T006 \[S1603] Add draft exclusion validation for blog and news content so draft entries cannot appear as built routes, sitemap URLs, or RSS items (`scripts/check-public-website-links.mjs`) * [x] T007 \[S1603] Add RSS, sitemap, robots, and canonical metadata validation with explicit missing-file and malformed-output errors (`scripts/check-public-website-links.mjs`) * [x] T008 \[S1603] Add broad static-output analytics and tracker absence checks for built HTML, JavaScript, XML, and text files while allowing negated no-analytics policy copy (`scripts/check-public-website-links.mjs`) *** ## Implementation (8 tasks) Main feature implementation. * [x] T009 \[S1603] Run root `npm install` and record pass, fixed, blocked, or unavailable status with no raw tokens, env values, or local secret paths (`.spec_system/specs/phase16-session03-automated-checks-and-build-gates/implementation-notes.md`) * [x] T010 \[S1603] Run root `npm run format:check`, verify website file coverage, and fix or document any root-format coverage gap (`package.json`) * [x] T011 \[S1603] Run root `npm run lint`, verify website file coverage, and fix or document any root-lint coverage gap (`package.json`) * [x] T012 \[S1603] Run root `npm run typecheck`, verify website workspace inclusion or document explicit package-scoped delegation (`package.json`) * [x] T013 \[S1603] Run package `npm --workspace @factionos/public-website run typecheck` and resolve Astro or TypeScript failures without adding `@astrojs/check` (`public-website/package.json`) * [x] T014 \[S1603] Run package `npm --workspace @factionos/public-website run build` and resolve static build failures without adding server rendering or a Cloudflare adapter (`public-website/package.json`) * [x] T015 \[S1603] Run root `npm run build`, verify website workspace inclusion or document explicit package-scoped delegation (`package.json`) * [x] T016 \[S1603] Run package static checker and resolve draft, RSS, sitemap, robots, metadata, approved-link, hosted-form, runtime-network, storage, analytics, or tracker failures (`public-website/package.json`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T017 \[S1603] \[P] Update public website README with launch check commands, root/package command delegation, static-output expectations, and no-tracking boundary (`public-website/README_public-website.md`) * [x] T018 \[S1603] \[P] Update development and release docs if root/package website command guidance or launch gate names changed (`docs/development.md`) * [x] T019 \[S1603] Record final command results, static output spot checks, fixed/deferred items, deployment no-claim boundary, and validation handoff notes (`.spec_system/specs/phase16-session03-automated-checks-and-build-gates/implementation-notes.md`) * [x] T020 \[S1603] Confirm ASCII encoding, Unix LF line endings, clean static privacy boundary, and ready-for-validate checklist for all session artifacts (`.spec_system/specs/phase16-session03-automated-checks-and-build-gates/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 Run the validate workflow step to verify session completeness. --- # 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/phase16-session03-automated-checks-and-build-gates/tasks.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.