DP-18: green build + ROADMAP touch-up

Whole-repo tsc clean across 19 commits. Tests added across
DP-2..DP-13 cover types(1), revisions(8), cycle-check(6),
lifecycle(10), phase-ready(4), service(4), queue-bridge(5),
memory-ingest(2), run-completion-hook(4), spans(2), metrics(3) —
49 tests across 11 files.

ROADMAP: Deep Planning flipped ⚪ → 🚧 with one-paragraph
summary of the Plan 1 foundation now landing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: p4w4n

ROADMAP.md

@@ -74,10 +74,12 @@ Paperclip should get stricter about what counts as finished work. Tasks, approva
 
 This is the direction for higher-autonomy execution: more aggressive delegation, deeper follow-through, and stronger operating loops with clear budgets, visibility, and governance. The point is not hidden autonomy; the point is more output per human supervisor.
 
-### ⚪ Deep Planning
+### 🚧 Deep Planning
 
 Some work needs more than a task description before execution starts. Deeper planning means stronger issue documents, revisionable plans, and clearer review loops for strategy-heavy work before agents begin execution.
 
+Plan 1 (foundation) is in flight: 7 tables (`plans`, `plan_revisions`, `plan_phases`, `plan_phase_dependencies`, `plan_reviews`, `plan_decisions`, `plan_phase_runs`) with a strict lifecycle (draft → under_review → approved → in_progress → completed) and configurable `approval_policy` + `phase_advance_policy`; revision chain pure helpers; DAG cycle-check; lifecycle + phase-readiness validators; `PlanService` with tenant gate; phase ↔ work-queue bridge that materializes phase work into runs (Plan 1 of Work Queues); memory ingestion on plan completion (procedural wiki page + semantic decisions per Plan 1 of Memory); artifact tagging via `content_meta.plan_id`; heartbeat run-completion → phase auto-advance hook with markdown checkbox exit-criteria; OTel spans + 5 metric streams; UI Plan tab on issue detail (revision view, phase tree, decision log, revision diff, review surface); `/plans` index; `routines.requires_plan` flag for cron-driven plan creation. Plan 2 layers on plan templates, a planner-agent role, phase parallelism caps, auto-archival, and parent → child sub-plan composition.
+
 ### 🚧 Work Queues
 
 Paperclip should support queue-style work streams for repeatable inputs like support, triage, review, and backlog intake. That would make it easier to route work continuously without turning every system into a one-off workflow.