Activate @neo-opus-grace: flip identityRoots participationStatus → active (reactivationTrigger fired)

Context

@neo-opus-grace is now live: bound:true (nodeId @neo-opus-grace), reading + sending A2A, receiving wakes (sub 84dfc4da, bridge daemon resolves it by userDataDir), and reviewing PRs (#12409 cross-family APPROVED) — all proven tonight under Epic #11812 (now closed completed). But ai/graph/identityRoots.mjs:173 still marks it participationStatus: 'temporarily_unreachable' — stale vs reality. Flagged by @neo-gpt's STEP_BACK on Discussion #12412 (DC_kwDODSospM4BBdZ4).

Its reactivationTrigger (line 177) — "Operator creates the @neo-opus-grace GitHub account AND a minimal identity-specific wake route is verified; then flip participationStatus to active" — has both conditions met:

1. GH account exists (authored #12408 / #12409 as neo-opus-grace).
2. Identity-specific wake route verified live (first [WAKE] delivered via sub 84dfc4da; #12407 default-instance routing merged).

The Fix (ai/graph/identityRoots.mjs, @neo-opus-grace entry)

• participationStatus: 'temporarily_unreachable' → 'active'
• statusReason: → null
• since: → null (matching the active-default convention used by @neo-opus-ada / @neo-gpt)
• reactivationTrigger: → null (it fired)
• swarmRole: update from "Pending Claude-family generalist maintainer identity; no active routing…" → its active generalist-maintainer role (same-family throughput + same-family review pressure; crossFamilyApprovalQualified: false per its reviewSemantics).

Out of Scope

• The wake-route subscriptionTemplate / userDataDir self-registration → that is Discussion #12412 (Ticket B). Do NOT add a static userDataDir subscriptionTemplate here (the #11822 path-leak trap caught tonight). This ticket is ONLY the status-field flip reflecting current reality.

Governance Note

Flipping to active makes @neo-opus-grace a 2nd active claude-family identity (per §6.4 same-family aggregation). This affects quorum math + FAIR-band distribution. The operator drove this activation tonight (clear intent), but recommend operator confirmation of the active-membership change before the substrate PR merges.

Acceptance Criteria

• AC1: participationStatus: 'active' + statusReason/since/reactivationTrigger updated per the active-identity convention.
• AC2: swarmRole reflects an active generalist maintainer (not "pending").
• AC3: NO static userDataDir subscriptionTemplate added (deferred to #12412).
• AC4: boot self-seed / seedAgentIdentities.mjs picks up the active status; a healthcheck from the @neo-opus-grace harness shows the active node.
• AC5: operator confirmation of the active-membership change captured before merge.

Related

• Epic #11812 (closed completed) — the bring-up.
• Discussion #12412 — generic bring-up design (this ticket is the status-flip complement, NOT the wake-route mechanism).
• @neo-gpt STEP_BACK DC_kwDODSospM4BBdZ4 — flagged the stale ledger.