epic: persona journey audit — one canonical journey per persona, walked on current build

[roballred]

Phase 0.5 epic. Depends on 0.4 (#514) landing (journey:* labels available).

Approach (per user decision, 2026-05-18)

• Sub-issue cadence: epic-only now; sub-issues created on demand immediately before each persona walk.
• Depth per walk: full walk, file every gap as its own issue (not stop-at-first-blocker).

Scope

For each of the 16 personas in business-architecture/personas/:

1. Define one canonical end-to-end journey the persona is expected to complete with GovEA. The journey lives in docs/persona-journeys/<persona-id>.md.
2. Walk the journey on the current build using seeded data.
3. Document the outcome of each step (works / partial / blocked / missing entirely).
4. For each blocker, partial result, or missing feature, file a new gap issue with:
   • A reproducer (steps to observe the gap on a fresh seed).
   • The capability ID that should own the fix.
   • Labels: track:core (default for journey gaps) and journey:<persona-id>.
   • Link back to the persona's sub-issue and to this epic.

Personas (16)

agency-ea-coordinator, budget-performance-analyst, business-stakeholder, cms-administrator, cms-viewer, consultant-si, data-modeler, department-director, domain-architect, early-maturity-practice-lead, elected-official, enterprise-architect, enterprise-data-architect, instance-administrator, junior-ea-analyst, programme-director.

Acceptance (epic-level)

• 16 markdown reports under docs/persona-journeys/, one per persona, each with step-by-step outcomes.
• All gap issues filed carry: reproducer, capability ID, track:core, journey:<persona-id>, and a link to this epic.
• A summary section in the epic body (or a follow-up docs/persona-journeys/README.md) tallying gaps per persona and per capability.

Acceptance (per sub-issue)

• docs/persona-journeys/<persona-id>.md exists and lists the canonical journey + step results.
• Every gap surfaced in the walk has a filed issue, cross-linked.
• Sub-issue is closed when the report is complete and all gap issues are filed (not when gaps are fixed — fixing is downstream).

Traceability

Capability: all (audit, not implementation)
Personas: all 16
Phase plan: Phase 0.5
Depends on: #514 (Phase 0.4 — journey labels)