Add future milestones: T1 (hardening), T2 (scale), T3 (features)

T1: Error recovery, observability, metrics, audit logging (8 tasks)
T2: Caching, parallelism, distributed locking (8 tasks)
T3: Plugins, templates, dependencies, custom judges, nested workflows (8 tasks)

Total project timeline: ~3 months T0→T3.

tasks/ROADMAP.md

@@ -0,0 +1,102 @@
+# Project Roadmap
+
+Multi-agent dev orchestrator for Temporal, building toward a fully autonomous software development system.
+
+## Milestones
+
+### T0: Core System (IN PROGRESS)
+9 tasks, foundational: Planner/Judge/Implementer orchestration, git workflow, LLM integration, e2e validation.
+
+**Status:** 9 subtasks defined, testable criteria in place.
+**Timeline:** ~2-4 weeks to implementation.
+**Done:** All T0.1–T0.9 pass verification → squash-merge to main.
+
+**Board:** `tasks/board.md`
+
+---
+
+### T1: Production Hardening (PLANNED)
+8 tasks: Error recovery, observability, metrics, audit logging, health checks.
+
+**Focus:** Reliability for long-running orchestrators in homelab.
+**Key wins:**
+- Resume from crash without data loss
+- Structured logging + Grafana metrics
+- Auto-tuning based on historical failures
+- Audit trail for compliance
+
+**Board:** `tasks/board-T1.md`
+
+---
+
+### T2: Scale & Performance (PLANNED)
+8 tasks: Caching, parallelism, batching, distributed locking.
+
+**Focus:** Handle 100s of concurrent tasks, reduce API call overhead.
+**Key wins:**
+- Result caching deduplicates LLM calls
+- Parallel task dispatch (9x wall-clock speedup)
+- Git operation batching (fewer network round-trips)
+- Distributed lock for multi-pod safety
+
+**Board:** `tasks/board-T2.md`
+
+---
+
+### T3: Feature Expansion (PLANNED)
+8 tasks: Plugins, templates, dependencies, human gates, custom judges, nested workflows.
+
+**Focus:** Extensibility + domain specialization.
+**Key wins:**
+- Load custom skill plugins
+- Save/load orchestrator config as templates
+- Task dependency ordering
+- Swap Judge for domain-specific validator (security auditor, code reviewer, etc.)
+- Nest orchestrators (multi-level hierarchy)
+- Import tasks from GitHub/Linear/JIRA
+
+**Board:** `tasks/board-T3.md`
+
+---
+
+## Implementation Order
+
+1. **T0 (2-4 weeks):** Core system working end-to-end.
+2. **T1 (2 weeks):** Production-harden the core.
+3. **T2 (3 weeks):** Scale & optimize.
+4. **T3 (4 weeks):** Advanced features.
+
+**Total:** ~3 months to full feature parity.
+
+---
+
+## Success Metrics
+
+- **T0:** System runs unsupervised on 9-task milestone, all subtasks auto-complete, squash-merge to main succeeds.
+- **T1:** 1000+ tasks completed, zero data loss across pod restarts, metrics queryable.
+- **T2:** 1000 concurrent tasks complete 10x faster than T0, < 5 API calls/task (vs current ~20).
+- **T3:** Custom Judge plugin loads and validates tasks, workflow templates save/restore state.
+
+---
+
+## Risk Mitigation
+
+| Risk | Mitigation |
+|------|-----------|
+| Temporal cluster unavailability | Implement activity heartbeat recovery + resumption logic (T1.1) |
+| Git conflicts on shared FS | Test multi-pod concurrent access (T1.6) → upgrade to distributed lock if needed (T2.8) |
+| LLM API latency | Implement result caching + batching (T2.1, T2.6) |
+| Board state corruption | Detect + auto-heal (T1.4) |
+| Audit trail tampering | Sign audit log with workflow key (T3.6) |
+
+---
+
+## Notes
+
+- Each milestone is independent: T1 can start once T0 core is complete, doesn't need full T0 cleanup.
+- T0 tasks are foundational; changes will ripple into T1–T3 test suites, but core API should remain stable.
+- Future milestones (T4+) could focus on: web UI, real-time dashboard, automated deployment of orchestrator itself (meta!), multi-cluster orchestration.
+
+---
+
+**Next:** Start T0.1 (repo scaffold).