Cycle Management Consolidation

Cycle management is duplicated across 6 projects with nearly identical agents that drift independently. Design's agent has 2-stage creation (initial-prompt.md → CYCLE.md) but the others use single-stage. qflow and qmap use a separate dev/experiments/ pattern. No clear canonical source exists, making updates error-prone.

One canonical cycle-manager in design, rolled out to all sister projects. Each project can append project-specific extensions. qflow and qmap converge to cycles/ while keeping their copy-based code workflow as an extension.

• .claude/agents/cycle-manager.md — all 6 projects
• cycles/ directories — new for qflow and qmap
• CLAUDE.md — sync documentation
• cycles/c29.cycle-management-consolidation/report.md — consolidation report

• Design's cycle-manager updated as canonical template with ## Project-Specific Extensions section
• Rolled out to bob-wire (with page-structure extension), market-analyst, app.qpoint.io
• qflow and qmap converged from dev/experiments/ to cycles/ pattern with copy-based code extension
• Created cycles/CYCLES.md and HISTORY.md for qflow and qmap
• Migrated per-cycle CYCLE.md files from dev/experiments/ to cycles/ for both qflow (11 cycles) and qmap (15 cycles)
• Removed CYCLE.md files from experiment directories (narrative CYCLES.md kept as historical reference)
• Added sync process documentation to design's CLAUDE.md
• Added commit-on-close to Archive workflow with batch support and close c<N>: <Focus> message format
• Added Bash to cycle-manager tool list for direct git access
• Synced commit-on-close update to all 5 sister projects

All 6 projects now share an identical canonical cycle-manager template with 2-stage creation. qflow and qmap fully converged — each experiment has a cycles/c<N>.<name>/CYCLE.md for metadata while code stays in dev/experiments/. The dev/experiments/CYCLES.md files remain as rich historical narratives. Consolidation report in report.md.