feat: Kata Manager Project — multi-project control plane

[codevibesmatter]

Summary

Standalone manager project at ~/.kata/manager/ that acts as a control plane for all kata-enabled projects. First-class kata projects subcommand tree.

Key capabilities

• Auto-discover kata projects from ~/.claude/projects/ + manual add/remove
• List all projects with version, mode, layout info
• Init from manager — set up new projects from outside (avoids hook loops)
• Cross-project doctor — health checks across all projects
• Bulk upgrade — batteries --update across all projects
• Compare/sync/backup — config operations between projects

Bundled surgical fixes (from config traceability audit)

• Stop condition enum (no more magic strings)
• Remove hardcoded mode names in enter.ts/suggest.ts
• Dead field cleanup (micro_planning, workflow_prefix, VALID_CATEGORIES)

Implementation phases

1. P1: Surgical fixes (B11-B13)
2. P2: Manager foundation — init, discovery, registry, list (B1-B4)
3. P3: Project management — init from manager, doctor, upgrade (B5-B7)
4. P4: Config operations — compare, sync, backup (B8-B10)
5. P5: Tests and verification

Spec

planning/specs/24-kata-manager-project.md

Research

• planning/research/2026-02-25-config-traceability-refactor.md
• planning/research/2026-02-25-kata-manager-project.md

[codevibesmatter]

Spec approved and committed: planning/specs/23-kata-manager-project.md (acce33f)

13 behaviors across 5 phases:

• P1: Surgical fixes (stop condition enum, hardcoded modes, dead fields)
• P2: Manager foundation (init, discovery, registry, list)
• P3: Project management (init from manager, doctor, upgrade)
• P4: Config operations (compare, sync, backup)
• P5: Tests and verification

[codevibesmatter]

Starting implementation on branch: feature/23-kata-manager

[codevibesmatter]

Implementation complete. PR: #24

Summary:

• 29 files changed, 2528 insertions, 35 deletions
• 45 new unit tests, all passing
• 5 granular commits (surgical fixes → foundation → project mgmt → config ops → tests)