[Phase C2] Persona / past-session picker UI

[terisuke]

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

Problem

After Phase C1 lands, the user has durable history of personas, projects, and sessions — but no UI surface to navigate it. Memory must be visible to be useful. Today, even the existing profile_id is generated and forgotten; there is no "previously analyzed" reuse path in the UI.

Scope

• Top bar: persona switcher (てりすけ / 宇宙野クラウディア / + Add persona). Switching changes the default question set and format on the next session start.
• Left rail: project list. Each project expands into its articles (article = brief + draft history).
• Selecting a past article rehydrates the right-side artifact panel (brief card + draft history).
• "Start new article from this persona" reuses the current canonical guide for that persona without re-analysing sources.
• Persona detail page: list of articles already analysed, last-analysed timestamp, "re-analyse from sources" button.

Acceptance criteria

• Switching personas changes the question set and the default format on the next session start.
• Re-opening yesterday's session restores the transcript exactly (depends on Phase A1 transcript + C1 storage).
• Adding a third persona via the UI persists to SQLite and survives a restart.
• Past style guides can be selected without re-fetching sources.
• Empty state (no personas, fresh install) onboards the user to seed terisuke or cloudia.

Dependencies

• C1 (SQLite), B4 (persona seeds), A1 (transcript renderer).

[terisuke]

Planning update after #17/#22/#24/#25: dependencies are now mostly satisfied except C1. This issue should wait for #26, then implement persona/history navigation over persisted projects, sessions, style guides, and drafts. It no longer needs to wait on B4/B5/source acquisition.

[terisuke]

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

Implemented for #27:

• saved style guides and brief sessions are exposed through GET /api/workflow/artifacts / GET /api/history;
• focused read endpoints exist for GET /api/author-style, GET /api/brief-sessions, GET /api/briefs, and GET /api/briefs/{id};
• the web UI now has 履歴から再開, saved style-guide/session selectors, and open/clear/refresh controls;
• opening a saved session restores persona/format, transcript state, completed brief, and draft-generation readiness.

Remaining #27 scope stays open: add-persona authoring UI, full project/article browsing, and broader restart/edit persistence semantics.

[terisuke]

Progress update from PR #84: the history picker now includes project/article/draft selectors backed by SQLite read APIs, in addition to the saved style-guide/session first cut. Keeping this issue open unless the owner accepts a narrower first-cut closure, because add-persona authoring UI and broader edit-persistence semantics remain outside the current implementation.

[terisuke]

Implemented and merged via PR #86.

What landed for #27:

• GET /api/personas now returns built-in personas plus persisted custom personas.
• POST /api/personas creates custom personas with validation.
• Memory JSON-backed storage and SQLite persist custom personas; SQLite reopen behavior is covered.
• The web UI includes an add-persona flow and selects the new persona in both current and history selectors.
• Browser E2E covers add-persona, selector update, reload behavior, and persona-scoped history.

Validation before merge:

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

Remaining custom persona update/delete and richer source management stay under #14 or a future follow-up, not this C2 acceptance.