epic: events - Deliver Markdown-backed event functionality #356

Outcome

Deliver approved event functionality distinguishing historical attendance from confirmed public appearances.

Verified context

The active book-site events page is hardcoded; richer legacy event views/types exist but are not integrated. Existing editorial work includes #39 and page capture #224.

Scope

Coordinate E1–E3 without assuming bookings, future dates or restoration of the old portfolio.

Acceptance criteria

• Approved event/edition model maps sources and appropriate existing views.
• Historical participation cannot imply a confirmed appearance.
• Editable narrative and metadata use approved Markdown/schema contracts.
• Empty, invalid and unknown-event cases have regression coverage.

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 event publication without inventing dates, participation or confirmed appearances.

1. Which source records distinguish historical attendance from a confirmed public appearance?
2. What evidence and approval are required before presenting an event as a confirmed appearance?
3. Which event and edition fields are required or optional, and how should unknown information be represented?
4. Which existing views should display each event category, and how should empty, invalid or unknown records behave?
5. What publication rules apply to unconfirmed or incomplete event entries?