[Phase C3] Render brief and style guide as human-readable cards

[terisuke]

Tracked under ADR 0002 — Phase C. Detail: implementation plan §C3.

Problem

The completed brief is rendered as JSON.stringify(brief, null, 2) (static/js/script.js:178) and the style guide as raw Markdown inside a <pre> (static/index.html:99). The user explicitly flagged this: accumulated knowledge must be visible in a human-readable form, not as JSON dumps.

Scope

Replace JSON dump with a card stack:

Brief card components:

• Theme (heading)
• Reader (chip)
• Must-include (chip list)
• Exclusions (chip list)
• Opening episode (quote block)
• Tone / stance (badge)
• Expected reader action (callout)
• Per-deep-dive answer accordion (collapsed by default; one accordion per deep-dive target with the parent question label as the accordion title)

Style guide card components:

• First-person badge
• Recurring themes (chip list)
• Opening pattern (quote block)
• Conclusion pattern (quote block)
• Anti-patterns (warning callouts)
• Article count and last-analysed timestamp

Both cards have an Edit affordance that updates the underlying brief/guide and persists to SQLite.

Acceptance criteria

• No JSON visible to the end user during normal operation.
• Editing a brief field updates the in-memory session and persists to SQLite.
• Editing a style guide field versions the guide (does not destroy history) — depends on C1 versioning.
• Cards are accessible (keyboard navigation, ARIA labels).
• Cards work for all 5 formats (technical formats may add fields like target_stack badge).

Dependencies

• C1 (SQLite for edit persistence), B5 (format-aware fields).

[terisuke]

Planning update after #25: scope is still valid but should include format-specific brief fields from composed templates, such as target_stack / technical_proof / cloudia_viewpoint / homepage_cta. Editing and versioning should depend on #26 so card edits persist and style-guide edits create versions.

[terisuke]

First product cut is implemented in branch codex/issue27-28-history-artifacts and tracked for closure by #81.

Implemented for #28:

• style guides render as human-readable cards with profile/guide/article metadata;
• article briefs render as human-readable cards with theme, reader, opening, action, must-include, context, exclusions, structure, tone, custom answers, and deep-dive answers;
• raw Markdown/JSON remains available behind disclosure controls for audit/debug;
• validation is documented in docs/validation/issue-27-28-history-artifacts-2026-05-03.md.

Remaining #28 scope stays open: editable card persistence/versioning and project/article/draft artifact browsing.

[terisuke]

Progress update from PR #84: readable history cards now cover project, article, brief, current draft, draft versions, and source snapshots, while raw style/brief artifacts remain available behind disclosure controls. Keeping this issue open unless the owner accepts a narrower first-cut closure, because editable card persistence/versioning and real browser E2E remain follow-up work.

[terisuke]

Implemented and merged via PR #86.

What landed for #28:

• Human-readable brief cards can be edited with save/cancel/error states.
• Brief edits persist through PATCH /api/briefs/{id} using a fields payload and do not rewrite original interview answers.
• Human-readable style-guide cards can be edited with save/cancel/error states.
• Style-guide edits persist as new saved guide versions through PATCH /api/author-style/{id} / POST /api/author-style/{id}/versions.
• Browser E2E covers brief/style edit save, cancel, and backend error behavior without xfail/skip.

Validation before merge:

• node --check static/js/script.js
• go test ./...
• python3 -m pytest tests/e2e -q -> 11 passed
• git diff --check

Remaining full brief-version tables and project/article/draft editing stay under #14 or a future follow-up.