Daedalus and Talos integration test

.beans/nuzlocke-tracker-mz16--session-journal-blog-posts.md

@@ -1,10 +1,11 @@
 ---
 # nuzlocke-tracker-mz16
 title: Session Journal / Blog Posts
-status: draft
+status: completed
 type: epic
+priority: normal
 created_at: 2026-02-19T07:43:05Z
-updated_at: 2026-02-19T07:43:05Z
+updated_at: 2026-03-20T15:30:38Z
 ---
 
 Let users tell the story of their nuzlocke run through session journal entries (blog posts).
@@ -23,10 +24,15 @@ For each play session, users can write a short post to document what happened. P
 
 The journal becomes a chronological narrative of the nuzlocke run, with game data woven in automatically.
 
-## Open Questions
+## Decisions
 
-- [ ] What editor experience? (Markdown, rich text, block editor?)
-- [ ] How are images stored? (Local uploads, external links, cloud storage?)
-- [ ] What run events can be linked/embedded? (Team snapshots, deaths, catches, badge progress?)
-- [ ] Should posts be publishable/shareable, or private by default?
-- [ ] How does the journal UI look? Timeline view? Blog-style list?
+- **Editor:** Plain markdown textarea with preview
+- **Images:** Via markdown URL syntax (no uploads)
+- **Run linkage:** Entries belong to a run, optionally linked to a boss battle
+- **Visibility:** Private only (no sharing — deferred until user accounts exist)
+- **Templates:** Blank slate — no templates
+
+## Success Criteria
+
+- [x] Backend: journal entries CRUD API is complete (`nuzlocke-tracker-vmto`)
+- [ ] Frontend: journal list, editor, and view are functional (`nuzlocke-tracker-d68l`)