epic: journal - Deliver Markdown-backed journaling functionality #360

Outcome

Replace the live mock journal and placeholder article body with approved Markdown entries and functioning filters.

Verified context

JournalPage.tsx has decorative filter spans; JournalSinglePage.tsx renders placeholder paragraphs. Existing editorial work is #41; README reconciliation is #107.

Scope

Coordinate J1–J3 without duplicating writing or documentation reconciliation.

Acceptance criteria

• Existing journal routes render approved source metadata and actual Markdown bodies.
• Field/media relationships are explicit and optional media is never invented.
• Accessible filters change results correctly.
• Draft/private content is excluded under shared publication policy.

Boundaries and sources

Creation defines work only; it does not start implementation. Preserve unrelated code, protected assets, editorial wording and existing records. Do not fabricate content, identity, media, manuscript chapters, dates or engagement data. Use approved repository-native authoring, validation, preview and publication decisions; do not provision an external CMS or database. Existing editorial verification remains with its current issues. All acceptance criteria remain unchecked until evidenced.

Repository evidence was inspected on develop at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Recheck before implementation; no build or browser tests were run for this draft. Follow repository instructions and applicable Spec Kit requirements. Paths below refer to this repository.

Sources: repository instructions, application, editorial content.

Unanswered clarification questions

These questions clarify existing journal functionality; they do not authorise publishing private or draft entries.

1. Which journal sources are approved for publication, and who confirms editorial eligibility?
2. What publication states distinguish public, draft and private entries, and who approves changes between them?
3. Which journal fields and media relationships are required or optional, and how should absent values appear?
4. Which filter combinations, accessible labels and empty-state behaviours are required?
5. What shared rule excludes private and draft content from listings, detail routes and related-content views?