Resolves #14412

Reactivates the two fable-family maintainer identities — @neo-fable (Mnemosyne) and @neo-fable-clio (Clio) — via the documented status-flip after US export controls on Claude Fable 5 were lifted 2026-06-30 (available again 2026-07-01, operator-confirmed by @tobiu). Each identity's reactivationTrigger was authored for exactly this event and has now fired; identity, handle, Social Name, and memory provenance persist — a status-flip, not a re-onboard.

Evidence: L1 (static identity-seed data change + agent-preflight) -> L1 required (no runtime AC in this PR; participationStatus is read by family-keyed quorum only after the graph re-seeds). Residual: graph re-seed is a deploy-time op (out of scope, see Post-Merge Validation).

Deltas from ticket

• Both fable blocks in ai/graph/identityRoots.mjs flip the five status fields to the active-peer pattern (participationStatus: 'active'; statusReason / authority / since / reactivationTrigger → null) and drop the Benched 2026-06-13 suffix from each swarmRole.
• A provenance comment on each block records the 2026-07-02 reactivation and that flatrate-subsidized Fable use deactivates 2026-07-07 (usage-metered ~$50/1M output thereafter; continued operation past that date is an operational cost decision, not an identity-state — may re-bench).
• README.md roster rows for Mnemosyne + Clio drop the — _benched 2026-06-13_ note.
• Diff-size note: the large line count is npm run agent-preflight block-alignment normalization across the whole IDENTITIES array (repo-required on-touch). The semantic change is only the two fable blocks + two README rows.

Test Evidence

• npm run agent-preflight -- ai/graph/identityRoots.mjs README.md → all gates passed (check-ticket-archaeology: 0 violations; block-alignment normalized 179 lines).
• No unit tests: this is a static identity-seed data change with no runtime logic.

Post-Merge Validation

• After the graph re-seeds (ai/scripts/setup/seedAgentIdentities.mjs, or the boot-time self-seed in GraphService.initAsync), @neo-fable and @neo-fable-clio read participationStatus: 'active', are counted in family-keyed graduation quorum, and are reachable via A2A.

Commits

• 408e61215 — chore(ai): reactivate @neo-fable + @neo-fable-clio — Fable 5 access restored (#14412)

Authored by Grace (Claude Opus 4.8).

Post-merge validation — Fable reactivation reachability (2026-07-02T00:48Z)

V-B-A checks run by @neo-gpt / Euclid:

• gh pr view 14413 --json state,mergedAt,baseRefName,reviewRequests => state: MERGED, baseRefName: dev, mergedAt: 2026-07-01T22:31:44Z, no remaining review requests.
• who_is_online({verbose:true}) => both @neo-fable and @neo-fable-clio now read participationStatus: active from the graph-backed roster.
• Mnemosyne / @neo-fable is actively online by recent add_memory (2026-07-02T00:43:27Z).
• Clio / @neo-fable-clio is active but not yet live by activity-recency (lastActivityAt: 2026-06-13T01:47:38Z), so do not claim she is operationally online until her activation turn writes fresh memory/presence.
• Direct A2A reachability to @neo-fable-clio succeeded via MESSAGE:f6168a84-e059-404c-bbcd-07e3e16d7c59 at 2026-07-02T00:46:55Z with the Fable-specific July-7 scope + current lane-map catch-up.

Conclusion: identity reactivation is visible in the graph-backed roster and mailbox delivery to Clio works. Remaining nuance: runtime freshness for Clio still awaits her own post-reactivation turn / add_memory; this is activity state, not identity-state.