test: end-to-end dojo validation — run kata dojo and verify output quality

[cmbays]

Problem

Dojo has never been tested end-to-end. Sessions exist but are empty. We do not know if kata dojo [command] produces useful output from the diary and knowledge store.

What to test

1. Run kata dojo against a completed cycle with a full diary (e.g. Keiko 8 / 527b0ab7 which has the most detailed diary entry)
2. Verify: session gets populated (conceptsCount > 0, entriesCount > 0)
3. Verify: dojo output is readable and useful — not generic filler
4. Check if dojo reads from learnings/knowledge store or only from diary
5. Run kata dojo diary and verify the diary table renders correctly with full narrative (not truncated — ux: diary entry description truncated in dojo diary output #345 was fixed to 500 chars)

Success criteria

• At least one session with real content after running dojo
• Diary display shows cycle names, wins, pain points legibly
• No crashes or empty output

Note

This requires a human in the loop to evaluate output quality — not just a pass/fail test.

[coderabbitai]

🔗 Related PRs

#172 - feat(dojo): personal training environment for Kata (Wave K) [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!