savepoint 1.0.1 → 1.0.3

package/.savepoint/releases/v1.1/epics/E04-epic-navigation/tasks/T002-epic-detail-overlay.md

@@ -0,0 +1,73 @@
+---
+id: E04-epic-navigation/T002-epic-detail-overlay
+status: done
+objective: "Add Epic Detail overlay showing E##-Detail.md content, triggered by Enter on a focused epic"
+depends_on:
+    - E04-epic-navigation/T001-sidebar-focusable-navigation
+---
+
+# T002: Epic Detail Overlay
+
+## Acceptance Criteria
+
+- Pressing `Enter` on a focused epic in the sidebar opens a centered overlay titled "EPIC DETAIL"
+- The overlay content is read from the epic's `E##-Detail.md` file on disk
+- If the file exists, it shows: epic title, purpose, definition of done, and the components table (rendered as text)
+- If the file does not exist, the overlay shows an informative "(no detail available)" message
+- The overlay is height-capped at ~70% of terminal height with scroll indicators (↑/↓) for overflow
+- `↑`/`k` and `↓`/`j` scroll the detail content (reuses existing scroll indicator pattern from `detail.go`)
+- `PgUp`/`PgDown` scroll in page increments
+- `Esc` or `q` closes the overlay and returns to epic panel focus
+- The overlay uses `styles.DetailOverlay` for consistent visual styling with task detail
+
+## Implementation Plan
+
+- [x] Add `OverlayEpicDetail OverlayType = "detail-epic"` to `model.go`
+- [x] Add `EpicDetailOffset int` to `Model` in `model.go`
+- [x] Add `EpicDetailContent string` to `Model` in `model.go` (cached content of the detail file)
+
+- [x] In `epic_panel.go` — add `RenderEpicDetail(epicID, content string, overlayW, maxHeight, offset int) string`:
+  - Parse frontmatter lines from the markdown content (lines between `---` markers) for metadata display
+  - Render header: epic ID and title from markdown heading
+  - Render body: the rest of the markdown content as plain text (no markdown rendering)
+  - Use `visibleDetailLines` from `detail.go` for height-capped scrolling
+  - Reuse `styles.DetailOverlay`, `styles.ColumnTitleFocused`, `styles.CardMeta`, `styles.ColumnTitle`
+
+- [x] In `update.go` — when `m.EpicPanelFocus && enter`:
+  - Derive detail file path: `{m.Root}/releases/{m.SelectedRelease}/epics/{epicSlug}/{shortID(epicSlug)}-Detail.md`
+  - Read the file content with `os.ReadFile`
+  - If error (file missing, etc.), set `m.EpicDetailContent = "(no detail available)"`
+  - Set `m.Overlay = OverlayEpicDetail`, `m.EpicDetailOffset = 0`
+  - Cache the content in `m.EpicDetailContent`
+
+- [x] In `updateOverlay` in `update.go` — match `OverlayEpicDetail` and handle:
+  - `esc`/`q` → `OverlayNone` (exit back to epic panel focus)
+  - `up`/`k` → decrement `EpicDetailOffset` if > 0
+  - `down`/`j` → increment `EpicDetailOffset`
+  - `pgup`/`pgdown` → page scroll using existing `detailPageSize()`
+
+- [x] In `view.go` — match `OverlayEpicDetail` and call `RenderEpicDetail(...)` with the cached content
+- [x] Reuse `visibleDetailLines`, `clampDetailOffset`, `detailRow`, `WrapText` from `detail.go` — no need to copy
+- [x] Run `make build && make test` to verify no regressions
+
+## Context Log
+
+Files read:
+- `internal/board/model.go`
+- `internal/board/update.go`
+- `internal/board/view.go`
+- `internal/board/epic_panel.go`
+- `internal/board/detail.go`
+- `internal/board/card.go` — `shortID` helper
+- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/E01-Detail.md` — example detail file
+
+Estimated input tokens: ~2800
+
+Quality gate: `go build` ✓, `go test ./...` ✓ (all 3 packages pass)
+
+Notes:
+- `detail.go` functions `visibleDetailLines`, `clampDetailOffset`, `WrapText` are unexported — `epic_panel.go` is in the same `board` package so they're accessible
+- Content loading is synchronous (simple file read) — no async command needed
+- `shortID` extracts "E04" from "E04-epic-navigation" via first `-` split
+- Updated `TestUpdate_epicPanelEnterSelectsFocusedEpic` → `TestUpdate_epicPanelEnterOpensDetailOverlay` to reflect T002 behavior change
+- Added 7 new tests covering overlay open, scroll, pgup/pgdown, esc close, view rendering, no-content fallback

package/.savepoint/releases/v1.1/epics/E04-epic-navigation/tasks/T003-epic-status-glyphs.md

@@ -0,0 +1,73 @@
+---
+id: E04-epic-navigation/T003-epic-status-glyphs
+status: done
+objective: "Add status glyphs to the epic sidebar showing each epic's lifecycle state"
+depends_on:
+  - E04-epic-navigation/T001-sidebar-focusable-navigation
+---
+
+# T003: Epic Status Glyphs in Side Panel
+
+## Acceptance Criteria
+
+- Each epic in the sidebar shows a status glyph prefix: `○` for `planned`, `▶` for `in_progress`, `◉` for `done`, `✓` for `audited`, space for unknown
+- The glyph is styled: `○` in dim, `▶` in orange, `◉` in green, `✓` in green — matching the status colour convention
+- The status is read from the `status:` field in each epic's `E##-Detail.md` frontmatter at load time
+- Only the **side panel** is affected — the `E` key dropdown overlay is unchanged
+- The status map is loaded once during `loadBoardData` and cached in the Model (no per-frame file I/O)
+- If an epic's detail file is missing or has no `status` frontmatter, the glyph defaults to a space (no indicator)
+- All existing epic sidebar rendering (focus highlighting, cursor, active marker, selected marker) works unchanged
+- `make build && make test` pass
+
+## Implementation Plan
+
+- [x] Add `EpicStatus map[string]string` to `Model` in `model.go` — keyed by epic ID, values like `"planned"`, `"in_progress"`, `"done"`, `"audited"`
+- [x] In `board.go` — update `loadBoardData` to load epic statuses:
+  - After listing epics for a release, iterate each epic's directory
+  - Build detail file path: `filepath.Join(epic.Path, shortID(epic.ID)+"-Detail.md")`
+  - Read the file with `os.ReadFile`
+  - Parse frontmatter with `data.NewParser().ParseFrontmatter(string(content))`
+  - Extract `"status"` from the returned map; if missing, skip
+  - Store in `epicStatuses[epic.ID]` — collect all epics across releases into the map
+- [x] Pass `epicStatuses map[string]string` through the `reloadMsg` pipeline so dynamic reloads preserve glyphs
+- [x] In `epic_panel.go` — update `RenderEpicSidebar` signature to accept `status map[string]string`
+- [x] Add a helper function `epicSidebarGlyph(status map[string]string, epicID string) string`:
+  - `"planned"` → styles.CardMeta.Render("○")
+  - `"in_progress"` → styles.GlyphBuild.Render("▶")
+  - `"done"` → styles.TagDone.Render("◉")
+  - `"audited"` → styles.TagDone.Render("✓")
+  - default → " " (single space)
+- [x] In `RenderEpicSidebar` — prepend the glyph to each epic label: `"▶ E01-tui-optimisation"`
+- [x] In `view.go` — pass `m.EpicStatus` to `RenderEpicSidebar`
+- [x] Handle `EpicStatus` in `reloadMsg` handler in `update.go` — store the map when tasks reload
+- [x] Update `reloadMsg` struct in `watch.go` to carry `epicStatuses map[string]string`
+- [x] Run `make build && make test` to verify no regressions
+
+## Context Log
+
+Files read:
+- `internal/board/model.go`
+- `internal/board/epic_panel.go`
+- `internal/board/view.go`
+- `internal/board/board.go`
+- `internal/board/watch.go`
+- `internal/board/update.go`
+- `internal/board/card.go` — glyph pattern reference
+- `internal/styles/styles.go` — existing style constants
+- `internal/data/parser.go` — `ParseFrontmatter` for YAML extraction
+- `.savepoint/releases/v1.1/epics/E01-tui-optimisation/E01-Detail.md` — example frontmatter with status field
+- `.savepoint/releases/v1.1/epics/E04-epic-navigation/tasks/T001-sidebar-focusable-navigation.md` — dependency status check
+- `internal/board/epic_panel_test.go` — updated RenderEpicSidebar test calls
+
+Estimated input tokens: 1800
+
+Notes:
+- Reuses `data.NewParser().ParseFrontmatter()` which already handles YAML frontmatter extraction
+- Reuses `shortID()` from `card.go` (same package) to derive the detail file name
+- The `E` key dropdown in `epic_panel.go` (`RenderEpicDropdown`) is intentionally NOT updated — side panel only per user preference
+- Function named `epicSidebarGlyph` (not `epicStatusGlyph`) — takes `(map[string]string, string)` for nil-safe lookup
+- `go build` + `go test ./...` pass
+
+## Drift Notes
+
+No drift — all changes are within existing files and follow established patterns.

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Audit.md

@@ -0,0 +1,237 @@
+---
+type: audit-findings
+audited: 2026-05-02
+---
+
+# Audit Findings: E05 Tasking Permissions
+
+## Main Findings
+
+E05 verified the tasking-permissions shift from the planned `m` hotkey to the final `p` priority hotkey, along with explicit router priority writes that stay in `task-building` and leave audit handoff as an explicit workflow step.
+
+The audit found documentation drift rather than a core behavior failure: live implementation and tests used `p`, while several planning documents still referred to `m`. The file-specific reconciliation blocks are retained under Proposed Changes for apply/close testing.
+
+## 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
+
+`.savepoint/Design.md`
+
+### Replace
+
+```md
+- Router updates are explicit TUI actions: after setting a task to `in_progress`, the agent prompts the user to press `m` in the board to update `.savepoint/router.md` to the focused task. Navigation alone must not change router state.
+```
+
+### With
+
+```md
+- Router updates are explicit TUI actions: after setting a task to `in_progress`, the agent prompts the user to press `p` in the board to mark the focused task as router priority. Navigation alone must not change router task priority.
+```
+
+---
+
+### Target File
+
+`.savepoint/Design.md`
+
+### Replace
+
+```md
+**Keybindings:** arrow/vim navigation, enter advances, backspace retreats, r/R refreshes, a/A exits toward audit review when proposals exist, q quits.
+```
+
+### With
+
+```md
+**Keybindings:** arrow/vim navigation, enter opens focused task detail, space advances, backspace retreats, `p` marks the focused non-done task as router priority, `r`/`R` opens release selection or refreshes where supported, `?` opens help, and `q` quits or closes overlays.
+```
+
+---
+
+### Target File
+
+`AGENTS.md`
+
+### Replace
+
+```md
+3. After setting `in_progress`, press `m` in the TUI to update the router
+```
+
+### With
+
+```md
+3. After setting `in_progress`, press `p` in the TUI to mark the focused task as router priority
+```
+
+---
+
+### Target File
+
+`.savepoint/router.md`
+
+### Replace
+
+```md
+**Next:** When starting work, set task `status: in_progress` and press `m` in TUI to update router task. Execute plan, tick checkboxes, run quality gates, update router to next task or `audit-pending`. Stop.
+```
+
+### With
+
+```md
+**Next:** When starting work, set task `status: in_progress` and press `p` in TUI to mark the focused task as router priority. Execute plan, tick checkboxes, run quality gates, update router to next task or `audit-pending`. Stop.
+```
+
+---
+
+### Target File
+
+`.savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md`
+
+### Replace
+
+```yaml
+status: planned
+```
+
+### With
+
+```yaml
+status: audited
+```
+
+---
+
+### Target File
+
+`.savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md`
+
+### Replace
+
+```md
+- TUI `m` hotkey implemented: sets router's `task` field to the currently focused task; detects if it's the last uncompleted task in the epic → sets `audit-pending` state
+- Help overlay shows `m` key binding
+```
+
+### With
+
+```md
+- TUI `p` priority hotkey implemented: sets router's `task` field to the currently focused non-done task and keeps router state as `task-building`
+- Help overlay shows `p` key binding
+```
+
+---
+
+### Target File
+
+`.savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md`
+
+### Replace
+
+```md
+- The `m` hotkey reads the currently focused task, not the epic panel cursor
+- Router state derivation from task:
+  - Task is the last uncompleted task in its epic → `state: audit-pending`, `task: <empty>`
+  - Otherwise → `state: task-building`, `task: <full-task-id>`
+  - `release` and `epic` are always set from the focused task
+- The `m` key does nothing when no task is focused, or when focused on a `done` task
+- The `m` key is independent of navigation — user can browse freely without router drift
+- No code enforcement against agents writing `done`. This is a documentation-only trust boundary. AGENTS.md is the contract.
+```
+
+### With
+
+```md
+- The `p` hotkey reads the currently focused task, not the epic panel cursor.
+- Router priority writes always set `state: task-building`, `task: <full-task-id>`, `release`, `epic`, and `next_action` from the focused task.
+- The `p` key does nothing when no task is focused, when an overlay is open, or when focused on a `done` task.
+- The `p` key is independent of navigation — user can browse freely without router task drift.
+- Audit state is not inferred by the priority key; audit handoff remains an explicit workflow/router closeout action.
+- No code enforcement prevents agents from writing `done`. This is a documentation-only trust boundary. AGENTS.md is the contract.
+
+## Implemented as
+
+- `AGENTS.md`, `templates/project/AGENTS.md`, and phase skill guides now describe the three-status canon and agent/user task-status ownership boundary.
+- `.savepoint/router.md` was simplified around the current state machine and task-building handoff.
+- `.savepoint/Design.md` Section 4 records that agents may only set `in_progress`; user-only operations are `done` and retreat.
+- `internal/board/model.go` adds `writeRouterTask(task data.Task)`, which reads the current router, writes release/epic/task/state/next_action via `data.WriteRouterState`, and updates in-memory router fields.
+- `internal/board/update.go` handles `p` before normal navigation when no overlay is open, no-ops for done tasks, and writes user-visible status messages.
+- `internal/board/help.go` and `internal/board/view.go` advertise `p: Priority` and render priority/status feedback in the footer.
+- `internal/board/update_test.go`, `help_test.go`, `view_test.go`, `card_test.go`, and transition tests cover priority routing, done-task no-op, overlay no-op, help text, footer status feedback, and transition messages.
+- Implementation deviation: the original design specified `m` and last-task `audit-pending` derivation. The final behavior uses `p` and keeps priority writes in `task-building` so audit handoff remains explicit.
+```
+
+---
+
+### Target File
+
+`.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T005-update-help-overlay.md`
+
+### Replace
+
+```yaml
+objective: "Add `m` key binding to the TUI help overlay"
+```
+
+### With
+
+```yaml
+objective: "Add `p` priority key binding to the TUI help overlay"
+```
+
+---
+
+### Target File
+
+`.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T005-update-help-overlay.md`
+
+### Replace
+
+```md
+# T005: Update Help Overlay
+
+## Acceptance Criteria
+
+- Help overlay (`?` key) shows `m` key binding: "m: update router"
+- Key binding appears with consistent styling in the shortcuts list
+- No other help entries modified
+
+## Implementation Plan
+
+- [ ] Add `helpRow("m", "update router")` to `RenderHelp` in `help.go`
+- [ ] Run `make build && make test` to verify
+```
+
+### With
+
+```md
+# T005: Update Help Overlay
+
+## Acceptance Criteria
+
+- Help overlay (`?` key) shows `p` key binding for router priority
+- Key binding appears with consistent styling in the shortcuts list
+- No unrelated help entries modified
+
+## Implementation Plan
+
+- [x] Add the `p` priority shortcut to `RenderHelp` in `help.go`
+- [x] Verify with `go build -o savepoint.exe main.go` and `go test ./...`
+```
+
+---

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md

@@ -0,0 +1,54 @@
+---
+type: epic-design
+status: audited
+---
+
+# Epic E05: Tasking Permissions & Router Updates
+
+## Purpose
+
+Restrict agent task status mutation to `in_progress` only (no `done`, no retreat). Add an explicit TUI priority hotkey (`p`) to update the router to the focused non-done task, decoupling router task priority from navigation. The user retains full control over `done` transitions and retreats via the board.
+
+## Definition of Done
+
+- AGENTS.md updated: agents set `status: in_progress` when starting implementation; only user can set `done` or retreat
+- Router.md updated: document that agent sets router task when starting work via explicit `p` action
+- Design.md Section 4 updated: status model distinguishes agent vs user capabilities
+- TUI `p` priority hotkey implemented: sets router's `task` field to the currently focused non-done task and keeps router state as `task-building`
+- Help overlay shows `p` key binding
+- `make build && make test` passes
+
+## Components and files
+
+| Path | Purpose |
+|------|---------|
+| `AGENTS.md` | Remove "set status: done" from Task Completion Protocol; add `in_progress` guidance |
+| `.savepoint/router.md` | Add agent router-update guidance in task-building state |
+| `.savepoint/Design.md` | Revise Section 4 status model: agent `in_progress` only, user `done`/retreat only |
+| `.savepoint/releases/v1.1/v1.1-PRD.md` | Add E05 to epic breakdown |
+| `.savepoint/router.md` | Update current state for E05/T001 |
+| `internal/board/update.go` | Add `p` key handler for explicit router priority update |
+| `internal/board/model.go` | Add `writeRouterTask()` method to update router release, epic, task, state, and next action |
+| `internal/board/help.go` | Add `p` key to keyboard shortcuts |
+| `internal/data/router.go` | No changes needed (WriteRouterState already supports all fields) |
+| `internal/data/write.go` | No changes needed |
+
+## Architectural notes
+
+- The `p` hotkey reads the currently focused task, not the epic panel cursor.
+- Router priority writes always set `state: task-building`, `task: <full-task-id>`, `release`, `epic`, and `next_action` from the focused task.
+- The `p` key does nothing when no task is focused, when an overlay is open, or when focused on a `done` task.
+- The `p` key is independent of navigation — user can browse freely without router task drift.
+- Audit state is not inferred by the priority key; audit handoff remains an explicit workflow/router closeout action.
+- No code enforcement prevents agents from writing `done`. This is a documentation-only trust boundary. AGENTS.md is the contract.
+
+## Implemented as
+
+- `AGENTS.md`, `templates/project/AGENTS.md`, and phase skill guides now describe the three-status canon and agent/user task-status ownership boundary.
+- `.savepoint/router.md` was simplified around the current state machine and task-building handoff.
+- `.savepoint/Design.md` Section 4 records that agents may only set `in_progress`; user-only operations are `done` and retreat.
+- `internal/board/model.go` adds `writeRouterTask(task data.Task)`, which reads the current router, writes release/epic/task/state/next_action via `data.WriteRouterState`, and updates in-memory router fields.
+- `internal/board/update.go` handles `p` before normal navigation when no overlay is open, no-ops for done tasks, and writes user-visible status messages.
+- `internal/board/help.go` and `internal/board/view.go` advertise `p: Priority` and render priority/status feedback in the footer.
+- `internal/board/update_test.go`, `help_test.go`, `view_test.go`, `card_test.go`, and transition tests cover priority routing, done-task no-op, overlay no-op, help text, footer status feedback, and transition messages.
+- Implementation deviation: the original design specified `m` and last-task `audit-pending` derivation. The final behavior uses `p` and keeps priority writes in `task-building` so audit handoff remains explicit.

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T001-update-agents-md.md

@@ -0,0 +1,45 @@
+---
+id: E05-tasking-permissions/T001-update-agents-md
+status: done
+objective: "Update AGENTS.md to remove agent 'set status: done' permission and add 'set status: in_progress' guidance with router update instruction"
+depends_on: []
+---
+
+# T001: Update AGENTS.md
+
+## Acceptance Criteria
+
+- Task Completion Protocol no longer says "Set the task frontmatter to `status: done`"
+- Protocol says "When starting implementation, set `status: in_progress`"
+- Protocol says "After setting `in_progress`, press `m` in the TUI to update the router"
+- The words "Set the task frontmatter to `status: done`" are removed or replaced
+- Audit Handoff Rule still says the agent updates router.md to `state: audit-pending` when all tasks are done (this is router state, not task state)
+
+## Implementation Plan
+
+- [x] In AGENTS.md `## Task Completion Protocol`: replace "Set the task frontmatter to `status: done`" with appropriate guidance
+- [x] In AGENTS.md `## Task Completion Protocol` step 7: keep router update for `audit-pending` (that's router state, not task status)
+- [x] In AGENTS.md add note under `## Task Status Canon` about agent vs user capabilities
+- [x] Run `make build && make test` to verify
+
+## Context Log
+
+Files read:
+- AGENTS.md
+- .savepoint/router.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T001-update-agents-md.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T002-update-router-md.md
+- agent-skills/savepoint-build-task/SKILL.md
+- Makefile
+
+Files edited:
+- AGENTS.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T001-update-agents-md.md
+- .savepoint/router.md
+
+Estimated input tokens: 6500
+
+Notes:
+- `make build && make test` could not run literally because `make` is unavailable in this environment.
+- Equivalent gates passed: `go run ./internal/buildtool -version "" build` and `go test ./...`.

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T002-update-router-md.md

@@ -0,0 +1,40 @@
+---
+id: E05-tasking-permissions/T002-update-router-md
+status: done
+objective: "Add agent router-update guidance to router.md task-building state and update current state for E05"
+depends_on: ["E05-tasking-permissions/T001-update-agents-md"]
+---
+
+# T002: Update Router.md
+
+## Acceptance Criteria
+
+- Router.md `task-building` state section includes guidance: "When starting work, set task `status: in_progress` and press `m` in TUI to update router task"
+- Current state in router.md updated to point to E05/T001
+- Router.md continues to describe `audit-pending` transition correctly (user confirms, router updates)
+
+## Implementation Plan
+
+- [x] Edit `.savepoint/router.md` `task-building` state block to add agent router-update instruction
+- [x] Update router.md `## Current state` yaml block to point to E05 tasking-permissions epic
+- [x] Run `make build && make test` to verify
+
+## Context Log
+
+Files read:
+- .savepoint/router.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T001-update-agents-md.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T002-update-router-md.md
+- agent-skills/savepoint-build-task/SKILL.md
+
+Files edited:
+- .savepoint/router.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T002-update-router-md.md
+
+Estimated input tokens: 5200
+
+Notes:
+- `make build && make test` could not run literally because `make` is unavailable in this environment.
+- Equivalent gates passed: `go run ./internal/buildtool -version "" build` and `go test ./...`.
+- Router current state already pointed to E05/T002. I left it on the active task instead of moving it backward to completed dependency T001.

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T003-update-design-md.md

@@ -0,0 +1,47 @@
+---
+id: E05-tasking-permissions/T003-update-design-md
+status: done
+objective: "Revise Design.md Section 4 to document agent vs user task status capabilities"
+depends_on: ["E05-tasking-permissions/T001-update-agents-md"]
+---
+
+# T003: Update Design.md
+
+## Acceptance Criteria
+
+- Design.md Section 4 (`## 4. Status model & gates`) documents:
+  - Agent can only set `status: in_progress`
+  - Only user can set `status: done` or retreat
+  - Router update is explicit via TUI `m` key, not automatic on navigation
+- `last_audited` field updated (or not — this is documenting current design, not auditing)
+- No other sections modified
+
+## Implementation Plan
+
+- [x] Edit `.savepoint/Design.md` Section 4 to add new permission row or note
+- [x] Update `last_audited` in frontmatter
+- [x] Run `make build && make test` to verify
+
+## Context Log
+
+Files read:
+- .savepoint/Design.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T001-update-agents-md.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T002-update-router-md.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T003-update-design-md.md
+- .savepoint/router.md
+- agent-skills/savepoint-build-task/SKILL.md
+- Makefile
+
+Files edited:
+- .savepoint/Design.md
+- .savepoint/router.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T003-update-design-md.md
+
+Estimated input tokens: 8500
+
+Notes:
+- `make build && make test` could not run literally because `make` is unavailable in this environment.
+- Equivalent gates passed: `go run ./internal/buildtool -version "" build` and `go test ./...`.
+- Task remains `status: in_progress`; only the user may set `status: done`.

package/.savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T004-implement-m-hotkey.md

@@ -0,0 +1,98 @@
+---
+id: E05-tasking-permissions/T004-implement-m-hotkey
+status: done
+objective: "Implement TUI `m` hotkey that explicitly sets the router's task from the currently focused task"
+depends_on: ["E05-tasking-permissions/T002-update-router-md", "E05-tasking-permissions/T003-update-design-md"]
+---
+
+# T004: Implement TUI `m` hotkey
+
+## Acceptance Criteria
+
+- Pressing `m` in the TUI board (when no overlay is open) reads the currently focused task and updates `router.md` with:
+  - `release`: from focused task
+  - `epic`: from focused task
+  - `task`: full task ID
+  - `state`: `task-building` (or `audit-pending` if last uncompleted task in epic)
+- Pressing `m` when no task is focused does nothing
+- Pressing `m` when focused on a `done` task does nothing (or shows status message)
+- Router `task` field in `writeRouterReleaseEpic` is now set explicitly (currently it writes release+epic only)
+- The `m` key does NOT work when any overlay is open (consistent with other board keys)
+- The `m` key displays a status message confirming the router update: "Router set to {release} {epic}/{task}" or "Audit pending for {epic}" if last task
+
+## Implementation Plan
+
+- [x] Add `writeRouterTask(task data.Task)` method to `model.go`: reads current router, sets release/epic/task/state fields, writes via `data.WriteRouterState`
+- [x] Add `m` key handler in `update.go` main switch (before epic panel routing, like `q`/`e`/`r`/`?`)
+- [x] Handler: calls `focusedTask()` to get current task, calls `m.writeRouterTask()`, sets `m.StatusMessage` on success/error
+- [x] Detect "last uncompleted task in epic" logic: scan `m.AllTasks` for the same epic, check if any are not done
+- [x] Update `writeRouterReleaseEpic()` is unchanged (still only writes release+epic, used by navigation)
+- [x] Run `make build && make test` to verify
+
+## Strategic Visual Rework Plan
+
+This task is reopened because the `m` hotkey work exposed router-priority and board rendering paths where terminal color fallback behavior still makes the TUI look patchy between black and gray. Do not continue with incremental one-widget fixes. Apply one bottom-up rendering policy.
+
+- [x] Force Lipgloss to a deterministic 256-color profile before board rendering starts.
+- [x] Change black 256-color fallbacks for Background, Surface, and Surface 2 to the same actual ANSI256 black value.
+- [x] Centralize the background policy in `internal/styles/styles.go`: TUI surfaces emit no explicit background escapes; terminal default background remains the single source of truth.
+- [x] Remove or avoid explicit background fills from nested panels/cards where they create padded gray bars.
+- [x] Normalize focus borders across task columns, task cards, overlays, and epic sidebar. Prefer single-line box borders if rounded borders continue rendering as dash bars in Warp.
+- [x] Add regression tests that fail if rendered board/card/router-priority output emits explicit background escapes.
+- [x] Verify representative board states in both Windows Terminal and Warp after code tests pass.
+
+## Context Log
+
+Files read:
+- .savepoint/router.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/E05-Detail.md
+- .savepoint/releases/v1.1/epics/E05-tasking-permissions/tasks/T004-implement-m-hotkey.md
+- internal/board/model.go
+- internal/board/update.go
+- internal/board/update_test.go
+- internal/board/board.go
+- internal/board/view.go
+- internal/board/column_test.go
+- internal/board/view_test.go
+- internal/board/render_policy_test.go
+- internal/styles/palette.go
+- internal/styles/styles.go
+- internal/data/router.go
+- internal/data/write.go
+
+Estimated input tokens: 12000
+
+Notes:
+- Focused task comes from `m.Tasks[m.FocusedColumn][m.FocusedTask]`
+- Router state derivation: if all other tasks in the same epic+release are `done`, set `state: audit-pending` and clear `task`; otherwise `state: task-building` with the task ID
+- Focused test: `go test ./internal/board` passed
+- Quality gate: `make build` could not run because `make` is unavailable in this shell
+- Quality gate equivalent: `go run ./internal/buildtool build` passed
+- Quality gate equivalent: `go test ./...` passed
+- Strategic color rework: `lipgloss.SetColorProfile(termenv.ANSI256)` is set before board rendering.
+- Strategic color rework: Background, Surface, and Surface 2 ANSI256 fallbacks now all use `16`.
+- Strategic color rework: nested task/card/panel text no longer paints gray background fills; root-level full-width lines also avoid explicit background escapes.
+- Strategic border rework: rounded borders replaced with single-line borders to avoid Warp dash-bar artifacts.
+- Regression scan: no `RoundedBorder`, rounded border glyphs, or ANSI256 gray background fallback codes (`232`/`233`) remain under `internal/`.
+- Remaining manual check: visually compare representative board states in Windows Terminal and Warp.
+- Follow-up color consistency pass: removed explicit background painting from `Divider`, `HeaderFrame`, `BoardFrame`, and `RootLine`; this avoids mixing terminal-default cells with `48;5;16` cells after nested style resets.
+- Regression tightened: `internal/board/render_policy_test.go` now fails on any `48;` background escape or basic black `40m` escape across board, card, detail, release/epic dropdown, and help render paths.
+- Focused test: `go test ./internal/board` passed after the no-background policy change.
+- Quality gate: `make build` still cannot run because `make` is unavailable in this shell.
+- Quality gate equivalent: `go run ./internal/buildtool build` passed after the no-background policy change.
+- Quality gate equivalent: `go test ./...` passed after the no-background policy change.
+- Manual verification: user confirmed closeout after the PowerShell/Warp color consistency pass.
+- Closeout focused test: `go test ./internal/board` passed.
+- Closeout quality gate: `make build` failed because `make` is unavailable in this shell.
+- Closeout quality gate equivalent: `go run ./internal/buildtool build` passed.
+- Closeout quality gate equivalent: `go test ./...` passed.
+- 2026-05-02 r1.1 E05 T04 pass: task frontmatter set to `status: in_progress`, `phase: test`; router updated to active T004 task.
+- Dependency correction: replaced stale nonexistent `T005-add-help-entry` dependency with `T003-update-design-md`.
+- Focused test: `go test ./internal/board` passed.
+- Quality gate: `make build` failed because `make` is unavailable in this shell.
+- Quality gate equivalent: `go run ./internal/buildtool build` passed.
+- Quality gate equivalent: `go test ./...` passed.
+- Follow-up fix: `m` handler was updating `StatusMessage`, but the footer never rendered that message; `internal/board/view.go` now shows status feedback between the phase line and key hints.
+- Added regression coverage in `internal/board/view_test.go` for footer status rendering.
+- Focused test: `go test ./internal/board` passed after status rendering fix.
+- Quality gate equivalent: `go test ./...` passed after status rendering fix.