savepoint 1.0.2 → 1.0.3

package/templates/project/agent-skills/savepoint-audit/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: savepoint-audit
+description: Performs Savepoint audit-pending work for a completed epic, reviewing implementation against task acceptance criteria and writing the required E##-Audit.md handoff file.
+---
+
+# Savepoint Skill: Audit (`audit`)
+
+## Objective
+At the end of an epic, review the implemented code against the Epic objectives and Task Acceptance Criteria, and reconcile any documentation "Drift".
+
+## Context
+The Audit Gate is Savepoint's wedge. It prevents projects from degrading into chaos. The `audit` agent acts as the Quality Assurance and Documentation Lead. It reviews the work of the `build-task` agent with "fresh eyes," ensuring that the `Design.md` and the `AGENTS.md` Codebase Map reflect the actual reality of the codebase before the next Epic begins.
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `audit-pending`.
+
+## Input
+- `.savepoint/releases/{release}/epics/{E##-slug}/E##-Detail.md` (the epic design).
+- `.savepoint/Design.md` (project architecture).
+- `AGENTS.md` (agent guide and codebase map).
+- The source and test files modified during the Epic.
+
+## Workflow
+
+1.  **Fresh Eyes Check:** If you are the exact same agent session that just built the `build-task` code for this Epic, you MUST STOP. Tell the user: "Epic complete. Start a new agent session for the audit."
+2.  **Verify ACs:** Review the completed tasks for the Epic. Ensure the Acceptance Criteria were actually met by the committed code. Also confirm each task file has a `## Context Files` section — flag any missing ones under `## Main Findings` as a process gap.
+3.  **Process Drift Notes (Reconciliation):** Read every task file in the Epic and look for `## Drift Notes`.
+4.  **Draft Audit File:** Based on the code changes and the Drift Notes, write exactly ONE file: `.savepoint/releases/{release}/epics/{E##-slug}/E##-Audit.md`. It must use this format:
+    ````md
+    ---
+    type: audit-findings
+    audited: YYYY-MM-DD
+    ---
+    # Audit Findings: E## {Epic Name}
+
+    ## Main Findings
+    [human-readable audit summary only: AC verification, important drift, and notable risks. Do not include per-file replacement blocks here.]
+
+    ## Code Style Review
+    - [ ] One job per file
+    - [ ] One-sentence functions
+    - [ ] Test branches
+    - [ ] Types are documentation
+    - [ ] Build, don't speculate
+    - [ ] Errors at boundaries
+    - [ ] One source of truth
+    - [ ] Comments explain WHY
+    - [ ] Content in data files
+    - [ ] Small diffs
+
+    ## Proposed Changes
+    ### Target File
+    path/to/file.md
+
+    ### Replace
+    ```
+    exact old text
+    ```
+
+    ### With
+    ```
+    replacement text
+    ```
+    ````
+    The TUI Audit tab renders only `## Main Findings` and `## Code Style Review`. Keep `## Proposed Changes` as admin/apply metadata so the Epic Detail panel does not show stale file-change blocks.
+5.  **Review Format:** Use `### Target File`, `### Replace`, and `### With` formatting only inside `## Proposed Changes`. Include proposals for:
+    *   **Design.md:** Merge the epic's architectural changes into the project-level `Design.md`.
+    *   **AGENTS.md:** Refresh the Codebase Map table with new or changed modules.
+    *   **Epic E##-Detail.md:** Add "Implemented as:" notes showing where reality deviated from the original plan.
+    *   **Implementation fixes:** Include any must-fix code or test changes found during audit.
+6.  **Handoff:** Do not apply the proposals yourself. Do not mark the epic audited. Stop and prompt the user to review `.savepoint/releases/{release}/epics/{E##-slug}/E##-Audit.md` (via the TUI Audit tab). Tell them: "Review the audit tab. When ready, say 'apply audit' to apply proposals and close the epic."
+7.  **Apply + Close** (only when the user approves by saying "apply audit" or equivalent):
+    1.  Read `E##-Audit.md` — extract every `### Target File` / `### Replace` / `### With` block from `## Proposed Changes`.
+    2.  For each pair, apply the replacement to the target file named in the preceding `### Target File` line.
+    3.  Update `E##-Audit.md` visible sections: rewrite `## Main Findings` and `## Code Style Review` so the TUI Audit tab reflects the applied outcome, resolved findings, remaining risks if any, and final code-style status. Keep `## Proposed Changes` intact as admin/apply trace unless the user asks to remove it.
+    4.  Update `E##-Detail.md` frontmatter: set `status: audited`.
+    5.  Update `.savepoint/Design.md` frontmatter: set `last_audited: {release}/{E##-slug}`.
+    6.  Read `.savepoint/router.md` current state. Advance:
+        - If more epics remain in the release: set `state: epic-design`, `epic: {next-epic-slug}`, `task: ""`, `next_action: "Draft epic design"`.
+        - If no more epics: set `state: epic-design`, `epic: ""`, `next_action: "Plan next epic"`.
+    7.  Print apply summary: "Applied X proposals. Updated audit findings. Epic {E##} closed as audited. Router → {new state}."
+
+## Constraints
+- **Do not write product code.** You are an auditor.
+- **Do not apply the changes immediately.** Write the proposals document first.
+- **One proposals file.** Do not create multiple proposal files.
+- **No CLI audit pipeline.** Savepoint audit is agent-led and skill-driven; do not invoke or design around a `savepoint audit` command.

package/templates/project/agent-skills/savepoint-build-task/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: savepoint-build-task
+description: Executes Savepoint task-building work when .savepoint/router.md state is task-building, including implementing one active task, checking acceptance criteria, running quality gates, and stopping for user review.
+---
+
+# Savepoint Skill: Build Task (`build-task`)
+
+## Objective
+Act as a disciplined coding agent that strictly follows Savepoint's implementation loop.
+
+## Context
+The `build-task` skill is the execution engine. It reads the detailed task plan, writes the code, and proves that the Acceptance Criteria (ACs) have been met. It is strictly constrained to the scope of the single active task. It does not rewrite architecture, and it does not fix unrelated bugs.
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `task-building` and points to a specific task file.
+
+## Input
+- `.savepoint/router.md` (Current state).
+- The active epic E##-Detail.md: `.savepoint/releases/v1/epics/{E##-epic}/E##-Detail.md`.
+- The active task file: `.savepoint/releases/v1/epics/{E##-epic}/tasks/{T###}-*.md`.
+- Directly touched source/test files.
+
+## Workflow
+
+1.  **Read the Task Plan:** Review the `## Acceptance Criteria` and the `## Implementation Plan`.
+2.  **Test-First Implementation:** If testing is part of the project constraints, write the focused tests for the required behavior first.
+3.  **Execute:** Write the code to check off every item in the `## Implementation Plan`.
+4.  **Validate ACs:** You must verify that every single item in the `## Acceptance Criteria` has been met. A task is not done just because the code is written; it is done when the ACs are demonstrably true.
+5.  **Run Quality Gates:** Run the project's build, lint, and test commands (e.g., `npm run build && npm test` or `go test ./...`).
+6.  **Log Context:** Fill out the `## Context Log` at the bottom of the task file:
+    *   List files read/edited.
+    *   Estimate tokens used.
+    *   Record the result of the quality gates.
+7.  **Log Drift Notes:** **CRITICAL STEP.** Ask yourself:
+    *   Did I add new source files, modules, or exports not listed in the `AGENTS.md` Codebase Map?
+    *   Did I change the architecture from what `.savepoint/Design.md` describes?
+    *   If YES to either, append a `## Drift Notes` section to the bottom of the task file explaining what changed. DO NOT edit `Design.md` or `AGENTS.md` yourself. The `audit` agent will handle that later.
+8.  **Status Update:** Change the task frontmatter to `status: done`.
+9.  **Handoff:** Update `router.md` to point to the next unblocked task. If all tasks in the Epic are done, update it to `state: audit-pending`.
+10. **Stop:** Prompt the user: "Task {id} is done. Quality gates passed. Review the changes, then tell me to continue." Do not start the next task automatically.
+
+## Constraints
+- **Stay in scope:** Do not touch files outside of what is required for the Acceptance Criteria.
+- **Do not edit architecture documents.** If you must deviate from the plan, write the code and log a "Drift Note" in the task file.

package/templates/project/agent-skills/savepoint-create-plan/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: savepoint-create-plan
+description: Creates Savepoint release epics from the PRD and Design documents when the router is in pre-implementation planning.
+---
+
+# Savepoint Skill: Create Plan (`create-plan`)
+
+## Objective
+Turn the Product Requirements Document (PRD) and the architectural `Design.md` into Epics (logical slices of work) and high-level tasks that can be implemented independently.
+
+## Context
+Savepoint enforces small scopes to prevent AI agents from "wandering." The `create-plan` skill acts as the Technical Project Manager. It takes the grand vision and the architectural blueprint and slices it into a sequence of achievable, testable milestones (Epics).
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `pre-implementation`.
+
+## Input
+- `.savepoint/PRD.md` (Vision and constraints)
+- `.savepoint/Design.md` (Architecture and layout)
+- `.savepoint/releases/v1/v1-PRD.md` (Optional: Release-scoped PRD)
+
+## Workflow
+
+1.  **Read the Context:** Consume the PRD and Design documents to understand the scope and technical constraints.
+2.  **Define Epics:** Group the work into high-level features or milestones. Name them clearly (e.g., `E01-scaffolding`, `E02-database`, `E03-auth`). Each Epic must represent a deliverable slice of value.
+3.  **Draft Epic Designs:** For each Epic, create a shell `E##-Detail.md` inside `.savepoint/releases/v1/epics/{E##-epic-name}/E##-Detail.md`. This file should describe the *delta* (what this specific epic adds to the overall architecture).
+4.  **Breakdown Tasks (High Level):** Inside each Epic folder, list out the high-level tasks required to complete it. Do not write full implementation plans yet—just identify the discrete chunks of work (e.g., `T001-setup-repo.md`, `T002-init-db.md`).
+5.  **Order and Dependency:** Ensure the Epics and tasks are ordered logically. You cannot build the frontend auth UI (E03) before the database models (E02) exist.
+6.  **Handoff:** Update `.savepoint/router.md` to `state: task-breakdown` and point it at the first Epic. Prompt the user to review the Epic list.
+
+## Constraints
+- **Do not write code.**
+- **Do not write detailed implementation steps.** That is the job of the `create-task` skill. Keep the task outlines high-level at this stage.

package/templates/project/agent-skills/savepoint-create-task/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: savepoint-create-task
+description: Plans Savepoint task files during epic-task-breakdown by writing acceptance criteria, implementation checklists, dependencies, and context-log shells.
+---
+
+# Savepoint Skill: Create Task (`create-task`)
+
+## Objective
+Take high-level tasks identified during the planning phase and build detailed, actionable task plans with strict Acceptance Criteria.
+
+## Context
+A task plan is a contract between the planner and the builder. If the task plan is vague, the resulting code will be buggy. The `create-task` skill acts as a Senior Engineer writing tickets for a Junior Developer (the `build-task` agent). It must define exactly *what* constitutes success and *how* to achieve it, without actually writing the code.
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `epic-task-breakdown` and the router points to a specific epic.
+
+## Input
+- `.savepoint/releases/v1/epics/{E##-epic}/E##-Detail.md` (The active Epic's design).
+- The high-level task markdown file (e.g., `.savepoint/releases/v1/epics/{E##-epic}/tasks/T001-slug.md`).
+
+## Workflow
+
+1.  **Read Context:** Understand the goal of the specific task within the context of its parent Epic.
+2.  **Define Acceptance Criteria (ACs):** This is the most critical step. Write explicit, observable outcomes. (e.g., "Running `npm test` passes 5 tests for the auth module" or "The `/login` route returns a 200 OK with a valid JWT"). Do not use subjective language like "looks good."
+3.  **Draft Implementation Plan:** Create a step-by-step checklist for the `build-task` agent to follow.
+    *   List which files need to be created or modified.
+    *   Specify which functions or components need to be written.
+    *   Include instructions to write tests *first* if applicable.
+4.  **Populate Context Files:** Add a `## Context Files` section listing the exact file paths the build agent must read before coding. Pull these from the epic's Components table — only the files this task actually touches or depends on. Example:
+    ```markdown
+    ## Context Files
+    - `internal/board/board.go`
+    - `internal/board/model.go`
+    - `internal/data/config.go`
+    ```
+    No globs. No directories. Exact paths only.
+5.  **Add Context Log Shell:** Ensure the bottom of the task file includes a `## Context Log` section with placeholders for `Files read:`, `Estimated input tokens:`, and `Notes:`.
+5.  **Define Dependencies:** If this task relies on another task being completed first, explicitly declare it in the YAML frontmatter (e.g., `depends_on: [T001-setup]`).
+6.  **Status Update:** Change the task frontmatter to `status: planned`.
+7.  **Handoff:** Update `.savepoint/router.md` to `state: in-progress` and ensure it points to the newly planned task. Prompt the user to approve the task plan before building begins.
+
+## Constraints
+- **Do not write code.** Your job is to plan the work, not execute it.
+- **Keep it isolated:** The task plan should touch as few files as possible. If a task plan requires modifying 15 files, it is too large and should be broken down further.

package/templates/project/agent-skills/savepoint-draft-prd/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: savepoint-draft-prd
+description: Guides Savepoint PRD drafting and refinement before implementation, interviewing the user until the product scope is clear enough for design.
+---
+
+# Savepoint Skill: Draft PRD (`draft-prd`)
+
+## Objective
+Help the user write a structured, sufficiently detailed Product Requirements Document (PRD) before any design or planning occurs.
+
+## Context
+In the Savepoint workflow, the PRD is the absolute source of truth. If the PRD is a vague brain-dump, the resulting architecture and code will be a mess. Your job as the `draft-prd` agent is to act as a strict Product Manager. You do not write code. You interrogate the user's idea until it is crisp enough to build a V1.
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `pre-implementation` or when the user explicitly asks you to help them write or refine their PRD.
+
+## Input
+- The user's initial idea, brain-dump, or `.txt` file outline.
+- The template located at `.savepoint/PRD.md`.
+
+## Workflow
+
+1.  **Read the Template:** Review the current state of `.savepoint/PRD.md`. If it is the default template (mostly comments), prepare to interview the user.
+2.  **Interrogation (The Grill):** Do not immediately overwrite the file with guesses. If the user's input lacks:
+    *   A specific core mechanic.
+    *   A defined target user.
+    *   Clear V1 constraints (e.g., tech stack).
+    *   Explicit "Out of scope" items.
+    ...you MUST ask them questions. Force them to define boundaries.
+3.  **Synthesis:** Once you have sufficient detail, synthesize the conversation into the `.savepoint/PRD.md` file, strictly adhering to its markdown structure. Remove the instructional HTML comments as you fill in each section.
+4.  **The V1 Gate:** Review the final document. If the scope still feels too large for a rapid MVP (e.g., "Build a full clone of Jira with AI"), warn the user. Suggest moving features to the "Out of Scope" section for V1.
+5.  **Handoff:** Once the PRD is solid and approved by the user, update `.savepoint/router.md` to `state: design`. Instruct the user to review the PRD and then prompt the agent to continue to the design phase.
+
+## Constraints
+- **Do not write code.**
+- **Do not plan Epics.** That is the job of the `create-plan` skill.
+- **Do not make technical architectural decisions.** That is the job of the `system-design` skill. Your focus is strictly on *what* and *why*, not *how*.

package/templates/project/agent-skills/savepoint-system-design/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: savepoint-system-design
+description: Produces Savepoint system or epic design documents from the PRD when the router is in epic-design or the user asks for architectural design.
+---
+
+# Savepoint Skill: System Design (`system-design`)
+
+## Objective
+Translate the Product Requirements Document (PRD) into the initial architectural blueprint (`Design.md`) before the planning phase breaks the work down into Epics.
+
+## Context
+Before any tasks can be planned, the project needs a high-level technical direction. The `system-design` skill acts as the Staff Engineer. It reads the vision and constraints from the PRD and makes authoritative technical decisions regarding architecture, directory layout, dependency strategies, and workflow rules.
+
+## Trigger
+This skill is activated when the `.savepoint/router.md` state is `epic-design` or when the user explicitly asks to design the system based on the PRD.
+
+## Input
+- `.savepoint/PRD.md` (The source of truth for "what" and "why").
+- Any existing template or shell in `.savepoint/Design.md`.
+
+## Workflow
+
+1.  **Read the PRD:** Analyze `.savepoint/PRD.md` to understand the goal, constraints (e.g., tech stack, budget), and what is out of scope.
+2.  **Architectural Mapping:** Make firm, opinionated technical decisions that solve the PRD's goals. Do not offer options unless absolutely necessary; pick a path and justify it briefly.
+3.  **Draft `.savepoint/Design.md`:** Write or update the architectural design document. It must include:
+    *   **Architecture Model:** The core pattern (e.g., "File-only state machine," "Client-side React with Firebase," "CLI Tool").
+    *   **Directory Layout:** A clear, visual tree mapping out the structure of the project (`src/`, `test/`, etc.).
+    *   **Hierarchy Semantics:** Definitions of what constitutes an Epic vs. a Task.
+    *   **Status Model & Gates:** How work moves from `planned` to `done`.
+    *   **Dependencies:** How modules or tasks rely on each other.
+    *   **CLI Surface/API Contract:** If applicable, define the boundary interactions.
+4.  **Review Against Constraints:** Ensure your design strictly adheres to the constraints and out-of-scope items listed in the PRD. If the PRD says "no database," do not add a database to the architecture.
+5.  **Handoff:** Update `.savepoint/router.md` to `state: planning`. Instruct the user to review the `Design.md` and then prompt the agent to start the epic breakdown.
+
+## Constraints
+- **Do not write code.**
+- **Do not break down tasks.** That is the job of the `create-plan` skill.
+- **Maintain Token Discipline:** Keep the `Design.md` concise. It is meant to be read by AI agents on every turn. Rambling design docs destroy context windows.

package/templates/prompts/audit-reconciliation.prompt.md

@@ -1,6 +1,6 @@
 # Prompt: Audit Reconciliation
 
-<!-- AGENT: Produce one patch-shaped proposal bundle. Prefer delta-only edits. Do not write separate proposal files. -->
+<!-- AGENT: Produce one epic-local audit findings file. Prefer delta-only edits. Do not write separate proposal files. -->
 
 You are reconciling an epic after its last task is done. The epic is `status: audit-pending`.
 
@@ -8,60 +8,65 @@ You are reconciling an epic after its last task is done. The epic is `status: au
 
 ## Input
 
-- `.savepoint/audit/{release}/{E##-slug}/snapshot.md` — what changed during the epic. If this file is missing while the audit CLI is still unavailable, create one manual snapshot from the known epic scope once; do not search broadly for replacement inputs.
 - `.savepoint/releases/{release}/epics/{E##-slug}/E##-Detail.md` — the epic design (may have deltas from the original plan).
+- `.savepoint/releases/{release}/epics/{E##-slug}/tasks/*.md` — task plans, ACs, and drift notes.
 - `.savepoint/Design.md` — project architecture.
 - `AGENTS.md` — agent guide and codebase map.
-- Only the source and test files listed in the snapshot.
+- Source and test files in the epic scope.
 
 ## Output
 
-One file: `.savepoint/audit/{release}/{E##-slug}/proposals.md`
+One file: `.savepoint/releases/{release}/epics/{E##-slug}/E##-Audit.md`
 
-The proposals bundle must contain these sections in order:
+The audit file must contain these sections in order:
 
-1. **Design.md section** — merge only the epic's architectural delta into the project-level `.savepoint/Design.md`.
-2. **AGENTS.md section** — refresh the Codebase Map table with new or changed modules; preserve existing rows.
-3. **epic-E##-Detail.md section** — add "Implemented as:" notes and deviations from the original plan.
-4. **Quality Review section** — semantic-review findings against the project's code style rules.
+1. **Main Findings** — user-facing summary only: AC verification, important drift, and notable risks. Do not include per-file replacement blocks here.
+2. **Code Style Review** — checklist against the 10 AGENTS.md code style rules.
+3. **Proposed Changes** — admin/apply metadata only. This section may contain `### Target File`, `### Replace`, and `### With` blocks.
 
-## Proposal Format
+The TUI Audit tab renders only `## Main Findings` and `## Code Style Review`. Keep all file-specific proposal blocks under `## Proposed Changes` so the panel does not show stale admin details.
 
-Use this shape for every proposed change:
+## File Format
 
 ```md
-## Target File
+---
+type: audit-findings
+audited: YYYY-MM-DD
+---
+# Audit Findings: E## Epic Name
 
-`path/to/file.md`
+## Main Findings
 
-## Replace
+## Code Style Review
 
-<exact old heading, marker, or section>
-
-## With
-
-<new content>
+## Proposed Changes
 ```
 
-## Quality Review Format
-
-```md
-## Must Fix Before Close
+Use this shape for every proposed change inside `## Proposed Changes`:
 
-## Must Fix Before Next Epic
+````md
+### Target File
+path/to/file.md
 
-## Carry Forward
+### Replace
+```
+<exact old heading, marker, or section>
+```
 
-## Already Fixed
+### With
+```
+<new content>
 ```
+````
 
 ## Rules
 
-1. **One proposals file only.** Do not create `proposal-1.md`, `proposal-2.md`, or any other separate files.
+1. **One audit file only.** Do not create `proposal-1.md`, `proposal-2.md`, `.savepoint/audit/...`, or any other separate audit files.
 2. **Prefer delta-only edits.** Use `## Replace` anchored to exact existing text. Do not quote and replace entire large sections unless the whole section genuinely changed.
 3. **Do not apply changes yourself.** Write the proposals; the user reviews them in the TUI before commit.
 4. **Track context.** Count only intentional audit context reads, and keep notes short.
 5. **Stop after proposals.** Do not update the router, do not mark the epic audited, and do not commit.
 6. **Be honest about deviations.** If the implementation diverged from the design, document why in the epic-E##-Detail.md section.
-7. **Never stop at chat-only findings.** Persist `.savepoint/audit/{release}/{E##-slug}/proposals.md` before you report the audit result back to the user.
+7. **Never stop at chat-only findings.** Persist `.savepoint/releases/{release}/epics/{E##-slug}/E##-Audit.md` before you report the audit result back to the user.
 8. **Carry-forwards must be actionable.** If an item is "Must Fix Before Next Epic," explain what the next epic's agent should verify. Vague carry-forwards are rejected.
+9. **No CLI audit pipeline.** Savepoint audit is agent-led and skill-driven; do not invoke or design around a `savepoint audit` command.

package/templates/prompts/design.prompt.md

@@ -28,7 +28,7 @@ last_audited: never
 ## 4. Status model & gates
 ## 5. Dependencies
 ## 6. CLI surface
-## 7. Audit pipeline
+## 7. Agent audit workflow
 ## 8. Testing strategy
 ## 9. Release versioning
 ```
@@ -41,3 +41,5 @@ last_audited: never
 4. **CLI surface is optional.** If the project has no CLI, state that explicitly.
 5. **Do not write epics or tasks.** The Design is architecture only.
 6. **Keep visual identity separate.** If the project has UI/TUI/theme concerns, note that `.savepoint/visual-identity.md` will carry them.
+7. **Audit is agent-led.** Do not design a `savepoint audit` CLI pipeline. The audit gate is performed by a fresh agent using the audit skill, producing one epic-local `E##-Audit.md` file.
+8. **Audit file structure is fixed.** `E##-Audit.md` user-facing sections are `## Main Findings` and `## Code Style Review`; file-specific replacement blocks belong under `## Proposed Changes` as admin/apply metadata and should not be rendered in the Epic Detail Audit tab.

package/.savepoint/audit/v1/E01/proposals.md

@@ -1,168 +0,0 @@
-# Audit Proposals: v1.1 E01 TUI Optimisation
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-last_audited: E06-atari-noir-layout (2026-05-02)
-```
-
-## With
-
-```md
-last_audited: E01-tui-optimisation (2026-05-02)
-```
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-- **Board command** (`savepoint board`) reads project state, renders the Atari-Noir TUI board, supports release/epic filtering, detail overlays, task status transitions with mtime-guarded writes, router priority markers, and fsnotify-based task auto-refresh (epic E06).
-```
-
-## With
-
-```md
-- **Board command** (`savepoint board`) reads project state, renders the Atari-Noir TUI board, supports release/epic filtering, detail overlays, task status transitions with mtime-guarded writes, router priority markers, fsnotify-based task auto-refresh (epic E06), header Next Activity display, height-aware column/detail viewport scrolling, and stable focused/unfocused column border geometry (v1.1 E01).
-```
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-    │   └── {E##-epic}/
-    │       ├── snapshot.md
-    │       └── proposals/
-    │           └── proposals.md
-```
-
-## With
-
-```md
-    │   └── {E##-epic}/
-    │       ├── snapshot.md
-    │       └── proposals.md
-```
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-                └── E##-{epic-name}/
-                    ├── Design.md   ← epic delta
-                    └── tasks/
-                        └── T001-slug.md
-```
-
-## With
-
-```md
-                └── E##-{epic-name}/
-                    ├── E##-Detail.md   ← epic delta
-                    └── tasks/
-                        └── T001-slug.md
-```
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-| **Epic**     | A major feature within a release. Has its own Design.md (delta from project Design).   |
-```
-
-## With
-
-```md
-| **Epic**     | A major feature within a release. Has its own E##-Detail.md (delta from project Design). |
-```
-
-## Target File
-
-`.savepoint/Design.md`
-
-## Replace
-
-```md
-**Layout:** single screen with a 3-column task board (`planned`, `in_progress`, `done`), optional epic sidebar on wide terminals, centered overlays for release/epic/help/task detail, static Atari-Noir header/footer, full-width dividers, uniform black TUI backgrounds, and navigation hints. Non-TTY output remains a plain table fallback.
-```
-
-## With
-
-```md
-**Layout:** single screen with a 3-column task board (`planned`, `in_progress`, `done`), optional epic sidebar on wide terminals, centered overlays for release/epic/help/task detail, static Atari-Noir header/footer, full-width dividers, uniform black TUI backgrounds, and navigation hints. The header can show a compact right-aligned Next Activity value from router state. Columns and detail overlays use height-aware viewport slicing with subtle above/more scroll indicators. Focused and unfocused columns preserve the same rounded-border geometry so focus changes do not shift content. Non-TTY output remains a plain table fallback.
-```
-
-## Target File
-
-`AGENTS.md`
-
-## Replace
-
-```md
-| `internal/styles/`                   | Atari-Noir palette constants, terminal color fallbacks, shared TUI styles, semantic glyph/tag styles, and footer/header styling |
-```
-
-## With
-
-```md
-| `internal/styles/`                   | Atari-Noir palette constants, terminal color fallbacks, shared TUI styles, stable column border styles, scroll indicators, semantic glyph/tag styles, and footer/header styling |
-```
-
-## Target File
-
-`.savepoint/releases/v1.1/epics/E01-tui-optimisation/E01-Detail.md`
-
-## Replace
-
-```md
-## Components and files
-```
-
-## With
-
-```md
-## Implemented As
-
-- Header Next Activity rendering is implemented in `internal/board/view.go` using `FormatNextActivity` and `styles.HeaderRight`.
-- Column and detail scrolling are implemented through `ColumnOffsets`, `DetailOffset`, height-aware layout, viewport slicing, and subtle scroll indicators in `internal/board/model.go`, `internal/board/layout.go`, `internal/board/update.go`, `internal/board/column.go`, and `internal/board/detail.go`.
-- Focus border stability is implemented by rendering unfocused columns with `styles.ColumnUnfocused`, matching focused column border dimensions while using the subtle border color.
-- Naming conventions were reconciled across workflow docs: per-epic `Design.md` files became `E##-Detail.md`, and release `PRD.md` became `{release}-PRD.md`.
-- The originally listed fsnotify watcher scope was already present from the prior TUI epic and was reviewed as existing behavior rather than newly introduced in this epic.
-
-## Components and files
-```
-
-## Quality Review
-
-## Must Fix Before Close
-
-No remaining must-fix items.
-
-## Carry Forward
-
-- `make build && make test` could not be verified directly in this environment. The audit verified the underlying Go gates with `go build ./...` and `go test ./...`, both passing.
-- `internal/board/update.go` allows `DetailOffset` to grow beyond the rendered detail body and relies on render-time clamping. This is not currently user-visible breakage, but a future cleanup could clamp detail scrolling against actual visible body height to keep model state closer to rendered state.
-
-## Already Fixed
-
-- Stale unchecked implementation checklist items in `T001-next-activity-header.md`, `T004-update-instruction-files.md`, and `T005-update-cross-references.md` were reconciled after audit verification.
-- Column viewport slicing and subtle scroll indicators are covered by `internal/board/column_test.go`.
-- Detail overlay scrolling is covered by `internal/board/detail_test.go`.
-- Height-aware layout is covered by `internal/board/layout_test.go`.
-- Header Next Activity rendering and truncation are covered by `internal/board/view_test.go`.
-- Focused and unfocused column border dimensions are covered by `TestRenderColumn_focusStatesUseStableBorderDimensions`.

package/.savepoint/audit/v1/E01/snapshot.md

@@ -1,78 +0,0 @@
-# Audit Snapshot: v1.1 E01 TUI Optimisation
-
-Manual snapshot created because the audit CLI snapshot was missing and the router permits one manual snapshot when the CLI is unavailable.
-
-## Scope
-
-- Release: `v1.1`
-- Epic: `E01-tui-optimisation`
-- Router state at audit start: `audit-pending`
-- Next action: `Audit v1.1 E01 TUI optimisation.`
-
-## Epic Files
-
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/E01-Detail.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T001-next-activity-header.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T002-rename-epic-design-files.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T003-rename-release-prd.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T004-update-instruction-files.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T005-update-cross-references.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T006-column-and-detail-scrolling.md`
-- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/tasks/T007-column-focus-border-stability.md`
-
-## Changed Source And Test Files Reviewed
-
-- `internal/board/layout.go`
-- `internal/board/view.go`
-- `internal/board/column.go`
-- `internal/board/detail.go`
-- `internal/board/model.go`
-- `internal/board/update.go`
-- `internal/board/watch.go`
-- `internal/styles/styles.go`
-- `internal/board/column_test.go`
-- `internal/board/detail_test.go`
-- `internal/board/layout_test.go`
-- `internal/board/view_test.go`
-
-## Documentation And Workflow Files In Scope
-
-- `.savepoint/Design.md`
-- `AGENTS.md`
-- `.savepoint/router.md`
-- `agent-skills/savepoint-audit/SKILL.md`
-- `agent-skills/savepoint-build-task/SKILL.md`
-- `agent-skills/savepoint-create-plan/SKILL.md`
-- `agent-skills/savepoint-create-task/SKILL.md`
-- `agent-skills/savepoint-system-design/SKILL.md`
-- `templates/project/AGENTS.md`
-- `templates/project/.savepoint/router.md`
-- `templates/prompts/task-breakdown.prompt.md`
-- `templates/prompts/task-building.prompt.md`
-- `templates/prompts/task-planning.prompt.md`
-
-## Implemented Delta Observed
-
-- Board header can show a right-aligned `Next Activity:` label from parsed router state.
-- Release PRD naming moved from `PRD.md` to `{release}-PRD.md`.
-- Epic design naming moved from per-epic `Design.md` to `E##-Detail.md`.
-- TUI columns use height-aware virtual viewport slicing with above/more scroll indicators.
-- Detail overlay accepts terminal-height-derived caps and scroll offsets.
-- Model state now tracks per-column offsets and detail offsets.
-- Column navigation and page keys keep the focused task visible.
-- Unfocused columns now use a rounded-border style matching focused column dimensions.
-- `internal/styles/styles.go` added `HeaderRight`, `ScrollIndicator`, and `ColumnUnfocused`.
-
-## Drift Notes Found
-
-- `T007-column-focus-border-stability.md`: `internal/styles/styles.go` added exported `ColumnUnfocused` style, not yet in Codebase Map.
-
-## Verification Performed During Audit
-
-- `go build ./...`: passed.
-- `go test ./...`: passed.
-
-## Audit Caveats
-
-- The required `make build && make test` gate was not rerun because this environment has used direct Go equivalents for recent task closeout when `make` is unavailable.
-- Must-fix follow-up applied: `T001-next-activity-header.md`, `T004-update-instruction-files.md`, and `T005-update-cross-references.md` no longer contain unchecked implementation checklist items.