docs(roadmap): refresh -- add #266, #268 to Phase 2, #270 to Phase 3

[MScottAdams]

Roadmap Refresh -- Session 2 (2026-04-09)

Triaged (3 issues)

• docs(readme): move installer asset links to top near install instructions #266 (Phase 2, t2.10.1) -- move installer asset links to top of README
• docs(readme): wrap install commands in fenced code blocks so GitHub renders copy button #268 (Phase 2, t2.10.2) -- wrap install commands in fenced code blocks for copy button
• feat(setup): validate USER.md against current schema -- query user for missing fields if stale #270 (Phase 3, t3.2.1) -- validate USER.md against current schema + artifact format versioning

Held (1 issue)

• Questions skipped due to auto-approve - new user problem #269 -- investigating with Warp team (auto-approve silently skips interview questions on Mac)

Closed (1 issue)

• bug(setup): Warp Auto Approve on file edit silently auto-answers entire deft interview -- produces wrong USER.md/PROJECT.md #271 -- duplicate of Questions skipped due to auto-approve - new user problem #269 (same root cause; deft-side sentry/guard mitigation tracked in Questions skipped due to auto-approve - new user problem #269)

No stale entries

Checklist

• CHANGELOG.md has [Unreleased] entry
• task check passes (973 tests, lint, validate, mypy)
• Analysis comments posted on all triaged issues
• Spec skeletons created (t2.10.1, t2.10.2, t3.2.1)
• Open Issues Index updated
• Pre-commit file review (encoding, duplication, structure)

[greptile-apps]

Greptile Summary

Documentation-only roadmap refresh for session 2 (2026-04-09): triages three issues (#266, #268, #270) into Phases 2 and 3, holds #269 pending Warp team investigation, and closes #271 as a duplicate. All three files are correctly updated — ROADMAP.md phase bodies and Open Issues Index, CHANGELOG.md [Unreleased] entry (count fixed from 5 to 3 in the second commit), and SPECIFICATION.md skeleton tasks — with one minor ordering inconsistency noted inline.

Confidence Score: 5/5

Safe to merge — docs-only change with no code impact and only a P2 ordering nit remaining.

All changes are documentation updates to CHANGELOG.md, ROADMAP.md, and SPECIFICATION.md. The CHANGELOG triage count was proactively self-corrected in the second commit. The only finding is a P2 style issue (spec task numbers out of ascending order), which has no functional consequence. Confidence guidelines call for 5/5 when all remaining findings are P2 or lower.

SPECIFICATION.md — minor task-number ordering inconsistency (t2.10.x before t2.9.1, t3.2.1 between t3.1.2 and t3.1.3).

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds [Unreleased] roadmap-refresh entry for session 2 (2026-04-09); count correctly reads "Triaged 3 new issues" after the fix commit.
ROADMAP.md	Adds #266/t2.10.1 and #268/t2.10.2 to Phase 2 Content & Doc Fixes, #270/t3.2.1 to Phase 3, corresponding Open Issues Index rows, and footer update note; all placements are consistent with existing roadmap structure.
SPECIFICATION.md	Adds three skeleton spec entries (t2.10.1, t2.10.2, t3.2.1) with traces; t3.2.1 is inserted between t3.1.2 and t3.1.3, and t2.10.1/t2.10.2 appear before the previously-added t2.9.1, both reversing expected ascending task-number order.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Roadmap Refresh Session 2] --> B{Issue Disposition}
    B --> C[Triaged: 3 issues]
    B --> D[Held: #269]
    B --> E[Closed: #271]
    C --> F[#266 → Phase 2, t2.10.1\nMove installer asset links]
    C --> G[#268 → Phase 2, t2.10.2\nFenced code blocks]
    C --> H[#270 → Phase 3, t3.2.1\nValidate USER.md schema]
    D --> I[Held pending Warp team\nMac auto-approve bug]
    E --> J[Closed as duplicate of #269]
    F --> K[ROADMAP.md Phase 2]
    G --> K
    H --> L[ROADMAP.md Phase 3]
    K --> M[Open Issues Index]
    L --> M
    F --> N[SPECIFICATION.md skeleton\nt2.10.1 + t2.10.2]
    H --> O[SPECIFICATION.md skeleton\nt3.2.1]
    C --> P[CHANGELOG.md\nUnreleased entry]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: SPECIFICATION.md
Line: 1018-1032

Comment:
**Spec task ordering: t2.10.x appears before t2.9.1**

The new `t2.10.1` and `t2.10.2` entries (lines 1018–1032) are placed immediately before the previously-added `t2.9.1` entry (line 1034), reversing the ascending task-number order within the Phase 2 skeleton section. `t2.9.1` (group 9) should precede `t2.10.x` (group 10) in reading order.

A similar inversion affects Phase 3: the new `t3.2.1` entry was inserted between `t3.1.2` (line 645) and `t3.1.3` (line 699), breaking the visual sequential flow of the `t3.1.x` dependency chain (t3.1.3 explicitly depends on t3.1.1 and t3.1.2).

Neither affects functionality, but consistent ascending order makes the spec easier to scan.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (2): Last reviewed commit: "fix: CHANGELOG triage count 5 -> 3 (matc..." | Re-trigger Greptile}