TrackCTL Roadmap Alignment

`tasks/roadmap.md`

Append this phase after the two completed sections. Preserve existing completed roadmap content exactly.

## Phase 3: Upgrade Alignment Pages

**Goal**: Upgrade the six existing `alignment/*.html` review pages to the current alignment-page standard without losing page-specific research, decisions, questions, gates, or review context.

**Scope**:
- Archive each original alignment page under `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/`.
- Rewrite `alignment/concept-exploration-trackctl.html` to the current dark-mode alignment-page standard.
- Rewrite `alignment/icp-trackctl.html` to the current dark-mode alignment-page standard.
- Rewrite `alignment/competitive-analysis-trackctl.html` to the current dark-mode alignment-page standard.
- Rewrite `alignment/value-prop-canvas-trackctl.html` to the current dark-mode alignment-page standard.
- Rewrite `alignment/journey-map-trackctl.html` to the current dark-mode alignment-page standard.
- Rewrite `alignment/customer-user-stories-trackctl.html` to the current dark-mode alignment-page standard.
- Run central alignment compilation after page upgrades; do not edit `alignment/index.html` by hand.

**Acceptance Criteria:**
- [ ] Each upgraded page uses the current dark-mode alignment-page standard with responsive layout and an in-flow top Table of Contents.
- [ ] Each page preserves its page-specific title, meta/context, findings, matrices, assumptions, decisions, open questions, review notes, proposed next steps, and existing diff/change context.
- [ ] Every major section has section feedback controls with local feedback-only YAML generation.
- [ ] Each applicable approval gate has required inline radio questions with `Other / None of the above`, `Need clarification`, optional notes, and unanswered-question handling.
- [ ] The bottom compile section provides separate feedback-only YAML and final answer YAML flows, copy status, explicit copy buttons, and clipboard fallback behavior.
- [ ] Research-oriented pages include evidence coverage, confidence/assumption handling, source coverage gaps, alternatives or lower-confidence findings where relevant, and downstream decision impact.
- [ ] Each original page is archived under `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/<filename>.html` before replacement.
- [ ] `alignment/index.html` is regenerated only through the central alignment compile workflow, not edited by hand.

**Parallelization:** serial
**Coordination Notes:** The six pages share the same generated-page standard, archive path, and index regeneration dependency. Keep serial to reduce content-loss risk and avoid conflicting archive/index state.

`tasks/todo.md`

Insert or replace a top-level `## Priority Task Queue` before the current handoff. The first unresolved task should route to phase decomposition after the roadmap phase exists.

## Priority Task Queue

- [ ] `$plan-phase 3` - decompose `Phase 3: Upgrade Alignment Pages` because `tasks/todo.md` contains an unchecked alignment-upgrade handoff, but `$exec` needs roadmap-backed implementation steps before it can run.

Files intentionally not changed in this step

• `alignment/*.html` pages remain unchanged until `$exec` executes the planned phase.
• `alignment/index.html` remains untouched; central regeneration is a later phase step.
• No `tasks/manual-todo.md`, `tasks/record-todo.md`, or `tasks/recurring-todo.md` is needed for this phase.

Deferred findings

• `tasks/history.md` is absent. This should be recorded during the later shipping step, not used to block the roadmap repair.
• No active implementation specs exist in `specs/`; broader product-phase discovery should happen after the current alignment-maintenance phase is unblocked or explicitly parked.