> 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/phase13-session01-astro-scaffold-and-workspace-wiring/tasks.md). # Task Checklist **Session ID**: `phase13-session01-astro-scaffold-and-workspace-wiring` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-01 *** ## 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 | 4 | 4 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 6 | 6 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **20** | **20** | **0** | *** ## Setup (4 tasks) Initial configuration and environment preparation. * [x] T001 \[S1301] Verify Node.js and npm prerequisites and record exact blocker details if below baseline (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T002 \[S1301] Inventory existing `public-website` files and record preservation requirements before scaffold (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T003 \[S1301] Create an Astro blog starter in a temporary location with overwrite prevention for existing website files (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T004 \[S1301] Compare temporary starter files against existing website planning files and document the merge plan (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) *** ## Foundation (6 tasks) Core structures and base implementations. * [x] T005 \[S1301] \[P] Create website package metadata with `@factionos/public-website`, Astro scripts, and excluded-stack guardrails (`public-website/package.json`) * [x] T006 \[S1301] \[P] Configure Astro static output, `https://faction-os.com`, MDX, sitemap, and RSS-compatible integrations (`public-website/astro.config.mjs`) * [x] T007 \[S1301] \[P] Add Astro TypeScript defaults for package-local typechecking (`public-website/tsconfig.json`) * [x] T008 \[S1301] \[P] Add Astro environment type declarations (`public-website/src/env.d.ts`) * [x] T009 \[S1301] Merge starter public assets without promoting unknown-provenance or non-release media (`public-website/public/favicon.svg`) * [x] T010 \[S1301] Merge starter source route foundation with static render behavior and no analytics, forms, auth, or server claims (`public-website/src/pages/index.astro`) *** ## Implementation (6 tasks) Main feature implementation. * [x] T011 \[S1301] Register `public-website` in root npm workspaces without disturbing existing workspace entries (`package.json`) * [x] T012 \[S1301] Extend root format and lint script coverage to include website files using the existing Biome command style (`package.json`) * [x] T013 \[S1301] Install or reconcile Astro workspace dependencies and update the lockfile with reviewable changes (`package-lock.json`) * [x] T014 \[S1301] Review website dependency metadata for no server adapter, analytics, hosted forms, auth, CMS, React, Tailwind, shadcn/ui, or third-party marketing template (`public-website/package.json`) * [x] T015 \[S1301] Preserve public website planning and UX source files after scaffold merge (`public-website/build-site-plan.md`) * [x] T016 \[S1301] Preserve the public website README as source guidance after scaffold merge (`public-website/README_public-website.md`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T017 \[S1301] Run website typecheck or record the exact environment blocker (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T018 \[S1301] Run website build or record the exact environment blocker (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T019 \[S1301] Verify root workspace recognition and dev script startup or record the exact environment blocker (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) * [x] T020 \[S1301] Validate ASCII encoding, Unix LF line endings, and excluded dependency posture across created website files (`.spec_system/specs/phase13-session01-astro-scaffold-and-workspace-wiring/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing or exact environment blockers recorded * [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/phase13-session01-astro-scaffold-and-workspace-wiring/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.