[ROADMAP] Plumb V0 → V1

[aram-devdocs]

Plumb V0 → V1 roadmap

Master tracking issue for V0 → V1 delivery. Each phase is a sub-runbook of
grouped child issues organized into sequential batches with a phase gate.

Specs: docs/runbooks/*-spec.yaml

Phases

Phase	Tracker	Gate	Status
Phase 1 — Real CDP driver + foundational rules	#10	real Chromium + 3 rules deterministic	⬜
Phase 2 — MVP rule set + token adapters	#20	8 rules zero false-positives + DTCG/Tailwind round-trip	⬜
Phase 3 — MCP surface expansion	#34	6 MCP tools + persistent-browser + real-URL lint_url	⬜
Phase 4 — Output formatter completeness	#43	SARIF uploads to Code Scanning + stats block	⬜
Phase 5 — Release distribution	#49	install works via cargo, brew, npm, curl + SLSA attested	⬜
Phase 6 — Docs + dogfooding	#56	plumb.aramhammoudeh.com live, 0 violations dogfooding, benchmarks published	⬜
Phase 7 — V1 features (post-V0)	#65	V1 feature set shipped (rules + driver + MCP + codegen + IDE)	⬜

How to execute

Open each phase tracker and follow its batches in order. Issues inside a
batch can run in parallel (one /gh-issue <N> session per issue, or a
single /gh-issue <N> <M> <O> --worktree session). Close a batch by
merging every child PR; the phase gate then unlocks the next batch (or
phase).

Non-goals (V0 + V1)

• Auto-fix source files — rendering ≠ source.
• Embedded Chromium — users bring their own.
• CSS-in-JS runtime token extraction — works with compiled output only.
• Commercial SaaS positioning — deferred.

Closing

Close this issue when every V0 phase parent (#10, #20, #34, #43, #49, #56) is closed AND Phase 7 (#65) has a committed V1 milestone.