docs: add microtasks.md as source of truth, archive planning docs, add traceability gate

[Copilot]

Replaces a sprawling docs/planning/ folder (83 files) and scattered phase summaries with a single canonical microtask registry and a CI gate script that keeps it honest.

Summary

Introduces docs/microtasks.md as the single source of truth for all 221 microtasks across 35 phases, archives legacy planning documents, and adds scripts/validate_traceability.sh to enforce traceability in CI.

Details

• Bug fix
• New feature
• Performance improvement
• Documentation / tooling

What changed?

• docs/microtasks.md (635 lines, new) — per-phase tables for PHASE-00 through PHASE-34; each row carries ID | Microtask | Status (🟢🟡🔴🔵⚪) | P | Effort | 🌟 | Description (done when) | Gate; progress summary shows 186/221 complete (84%)
• docs/archive/ (new dir) — all 83 docs/planning/ files + 9 misplaced phase summaries from clients/, infrastructure/, ios/, android/ consolidated here; docs/planning/ removed
• scripts/validate_traceability.sh (new, executable) — CI gate: asserts microtasks.md exists, all PHASE-00–PHASE-32 IDs are present, every referenced gate script exists on disk, and docs/archive/ is populated; exits 0 on 43/43 checks
• docs/IMPLEMENTATION_STATUS.md — prepended high-level phase completion table; pointer to microtasks.md as canonical source

Rationale

• Phase summaries and progress notes had proliferated across 5+ directories with no single authoritative status view; microtasks.md provides that view with machine-checkable gates
• The traceability script can be wired into CI so green status on any microtask requires an explicit gate pass, not just a doc edit
• Aligns with RootStream's clarity-over-cleverness principle: one file to check instead of 90

Testing

• scripts/validate_traceability.sh run locally: 43/43 checks pass, exit 0

• docs/microtasks.md manually verified to contain all phase headings PHASE-00 through PHASE-34

• Built successfully (make)

• Basic streaming tested

• Tested on:

  • Distro: N/A (docs/tooling only)
  • Kernel: N/A
  • GPU & driver: N/A

Notes

• Potential impact on latency or resource usage: none
• Follow-up: wire validate_traceability.sh into the GitHub Actions CI matrix; begin PHASE-32 (Backend Integration) tasks now that the registry is in place

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.