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

[cmbays]

Problem

Diary entries for cycles without a human-readable name show cycleName=null or use UUID. One confirmed entry (208f3427 / Keiko 10) has cycleName: null.

In the dojo, diary entries are a primary source of historical context. A null or UUID cycle name makes diary entries unreadable and breaks any display that groups or labels by cycle.

Root cause

Cycles created before the --name flag (Keiko 10 #346) have no name. When diary is written, it copies whatever cycleName exists at the time. If cooldown runs before the cycle has a name, cycleName is null.

Fix

1. When writing a diary entry, fall back to a computed label if cycleName is null (e.g. 'Cycle NNN' based on completion order, or short ID)
2. Backfill existing diary entries where cycleName is null using cycle completion order
3. Encourage users to always set a name at staged launch (already supported via --name flag)

Larger question (needs-human)

Should every cycle require a name? Should kata keiko new prompt for one by default?

[coderabbitai]

🔗 Related PRs

#293 - fix: defer cycle file write until after all prompts complete in kata cycle new [merged]
#350 - feat: add --name flag to kata cycle staged launch (#346) [closed]

---

📝 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!