feat: require cycle name at launch — eliminate unnamed cycles and null cycleName in diary/context

[cmbays]

Problem

Cycle names are currently optional. When a cycle is created without a name:

1. kata cooldown "<cycleId>" must be used instead of the human-readable name
2. cycleName is null or absent in diary entries — "Missing cycle name" logged during cooldown
3. Agent context and formatAgentContext() output shows undefined or empty cycle name
4. The name→ID map in memory (MEMORY.md) has to be maintained manually as a workaround

Evidence

• Keiko 9 cycle (5af5196f) had no name — referred to as unnamed in all logs
• Cooldown diary entries showed cycleName: null which triggered a warning
• next-keiko-proposal-generator.ts has a logger.warn() for missing cycle name (added in Keiko 11)

Desired behavior

• kata keiko new should require a name (no --skip-name or empty default)
• kata keiko staged new should require a name at staging time
• kata keiko staged launch should enforce name is set before flipping to active
• The name should be persisted on the Cycle object and surfaced in:
  • kata cooldown (accept name OR id)
  • kata kiai context output
  • Diary entries (cycleName field)
  • formatAgentContext() output

Migration

Existing unnamed cycles are historical — no migration needed. Only enforce going forward.

Acceptance criteria

• kata keiko new errors if --name is not provided (or prompts interactively and rejects empty)
• kata keiko staged new same behavior
• cycleName is never null/undefined in diary entries for new cycles
• kata cooldown "<name>" works for all new cycles (name lookup by string)

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• ux: diary entries missing cycleName for unnamed cycles — dojo context broken #369

🔗 Related PRs

#293 - fix: defer cycle file write until after all prompts complete in kata cycle new [merged]
#321 - feat: LLM-driven next-keiko proposals after cooldown complete [merged]
#350 - feat: add --name flag to kata cycle staged launch (#346) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!