Epic: Promote persona-mention to the fleet (reach incubator + auto-detect new repos)

[don-petry]

Scope

"Reach incubator + new repos" with the ideation/analysis capability. Three parallel
tracks that converge on incubator:

• Router (persona-mention) → the shared mention runtime BA rides. [promote persona-mention 1/3] Soak through the rings (next → ring0 → ring1 → stable) #783→[promote persona-mention 2/3] Wire into ring-pins + deploy + bootstrap #784→[promote persona-mention 3/3] Deploy sweep — reach incubator + all repos #785.
• business-analyst persona → rides the router; has its own prereqs. business-analyst persona: register in canary-rings.json + promote past draft (incubator prereq) #814.
• feature-ideation workflow → standalone scheduled pipeline; independent stub. feature-ideation → incubator: add caller stub (@v1-stable) + project_context + Discussions/Ideas #813.

Tracked stories (DAG)

Persona-mention router:

• [promote persona-mention 1/3] Soak through the rings (next → ring0 → ring1 → stable) #783 — SOAK (gate)
• [promote persona-mention 2/3] Wire into ring-pins + deploy + bootstrap #784 — WIRE (blocked by [promote persona-mention 1/3] Soak through the rings (next → ring0 → ring1 → stable) #783)
• [promote persona-mention 3/3] Deploy sweep — reach incubator + all repos #785 — SWEEP → incubator + all repos (blocked by [promote persona-mention 2/3] Wire into ring-pins + deploy + bootstrap #784)

business-analyst → incubator (rides the router):

• business-analyst persona: register in canary-rings.json + promote past draft (incubator prereq) #814 — register business-analyst in canary-rings.json + promote past draft (independent of [promote persona-mention 1/3] Soak through the rings (next → ring0 → ring1 → stable) #783; BA can't route in incubator until BOTH business-analyst persona: register in canary-rings.json + promote past draft (incubator prereq) #814 AND [promote persona-mention 3/3] Deploy sweep — reach incubator + all repos #785 land)

feature-ideation → incubator (standalone, parallel — NOT blocked by the router DAG):

• feature-ideation → incubator: add caller stub (@v1-stable) + project_context + Discussions/Ideas #813 — add feature-ideation caller stub @v1-stable + project_context + Discussions/Ideas

---

Today the persona mention framework is live ONLY in the next ring (.github-private). incubator and any new repo are outside it — a @petry-projects/<role> mention there does nothing (no stub → no dispatch). This Epic reaches the whole fleet and makes new repos auto-onboard.

Verified gap: persona-mention.yml exists in only .github-private; it is in neither deploy-standard-workflows.sh nor bootstrap-new-repo.sh (grep = 0 in both).

The DAG

#1 SOAK ── prove persona-mention through the rings (next → ring0 → ring1 → stable)
            cut/move the channel tags; watch each ring before advancing.   [GATE]
              │
#2 WIRE ── add persona-mention to: ring-pins.sh RING_REUSABLES +
   deploy-standard-workflows.sh + bootstrap-new-repo.sh. Makes compliance enforce
   the pin and the deploy sweep carry the stub.  (blocked by #1 cutting the tier tags)
              │
#3 SWEEP ── run deploy-standard-workflows.sh across the fleet → every repo (incl.
            incubator) gets persona-mention.yml at its ring pin; new repos get it
            at creation via bootstrap.  (after #2)

Stories

#1 — Soak persona-mention through the rings (GATE)

• next soak DONE + proven (qa-lead advisory, .github-private#1300; recursion guard held).
• Advance persona-mention/v1-ring0 → v1-ring1 → v1-stable via cut-release.sh persona-mention <ver> --channel <tier> [--promote], watching each ring before advancing (ring0=.github, ring1=TalkTerm/bmad-bgreat-suite, stable="*" per ring-pins.sh). Do NOT skip to stable.

#2 — Wire persona-mention into the fleet mechanisms (dev-lead-implementable)

• scripts/lib/ring-pins.sh — add persona-mention to RING_REUSABLES (compliance enforces @persona-mention/v1-<tier> per repo; deploy knows the tier). Only after Addressing PR comments #1 cuts the tier tags, else compliance demands a pin to a nonexistent tag.
• scripts/deploy-standard-workflows.sh — add persona-mention.yml to the deployed set, pinned per ring_tier_for_repo.
• scripts/bootstrap-new-repo.sh — seed persona-mention.yml so new repos auto-onboard.
• Acceptance: dry-run deploy shows incubator would get persona-mention.yml@persona-mention/v1-stable; bootstrap dry-run for a fresh repo includes it.

#3 — Deploy sweep (session/gated)

• Run the fleet apply so every repo — including incubator — gets the stub at its ring pin.
• Verify: incubator/.github/workflows/persona-mention.yml present; a smoke-test mention in incubator routes end-to-end.
• Note: deploy can't direct-push to ruleset-protected repos → PR + admin-merge / SKIP_OVERRIDES (add-to-project precedent).

Rubber-duck findings

1. stable's "*" resolves ring MEMBERSHIP, not deployment — the stub file is only placed by the Add coding standards & principles section to AGENTS.md #3 sweep. "Auto-detect new repos" is true ONLY once Add multi-agent isolation strategy using git worktrees #2 wires bootstrap-new-repo.sh.
2. Order in Add multi-agent isolation strategy using git worktrees #2: ring-pins needs the tier tags first (Addressing PR comments #1), or compliance demands a pin to nothing.
3. The runner is single-homed and already fleet-ready — Add multi-agent isolation strategy using git worktrees #2/Add coding standards & principles section to AGENTS.md #3 fan out only the ROUTER stub, not the runner. No runner change.
4. Secrets: stub needs GH_PAT_WORKFLOWS (org secret, fleet-wide already).
5. Blast radius: stable makes every repo's comments hit the router. Guards are proven, but hold stable for explicit go.

Acceptance criteria

• Addressing PR comments #1: v1-stable reached via healthy ring soak (not skipped).
• Add multi-agent isolation strategy using git worktrees #2: ring-pins + deploy + bootstrap carry persona-mention; tests green; dry-runs show incubator + new-repo coverage.
• Add coding standards & principles section to AGENTS.md #3: sweep run; incubator has the stub; a mention there routes end-to-end.
• New-repo: bootstrap a throwaway/dry-run → persona-mention.yml present.
• BA→incubator (business-analyst persona: register in canary-rings.json + promote past draft (incubator prereq) #814 + [promote persona-mention 3/3] Deploy sweep — reach incubator + all repos #785): business-analyst registered in canary-rings.json; persona past draft; an @petry-projects/business-analyst mention in incubator routes end-to-end (advisory posted).
• feature-ideation→incubator (feature-ideation → incubator: add caller stub (@v1-stable) + project_context + Discussions/Ideas #813): stub present at @feature-ideation/v1-stable; a dispatch run publishes to the incubator "Ideas" discussion.

Delivery uses the agreed approach: dev-lead implements the scoped stories, I define/monitor/validate; ring/stable promotion gated on explicit go. The canary promoter that moves the persona-mention tier tags now works (#807 fixed .github tag moves); gate reliability is being hardened in #810/#811.

Gated on your go for stable — fleet-wide activation, separate from the delivered persona onboarding.

[don-petry]

Added story: #836 — three workflows → standard deployable shims

Promotes initiative-driver, pr-auto-review, and feature-ideation into DEPLOYABLE_WORKFLOWS so the sweep carries them fleet-wide (the mechanism half; the actual sweep stays with the #2/#3 sweep stories).

• Make initiative-driver / pr-auto-review / feature-ideation standard deployable shims (+ canonical-PAT migration) #836 — add the three to deploy-standard-workflows.sh + migrate their bare GH_PAT_WORKFLOWS refs to the GH_PAT_DON_PETRY || … fallback chain.

Two notes:

• Supersedes the manual-add framing in feature-ideation → incubator: add caller stub (@v1-stable) + project_context + Discussions/Ideas #813 for feature-ideation: instead of hand-placing a stub per repo, feature-ideation becomes a sweep shim with a seed-if-absent + re-pin-in-place policy that preserves each repo's per-repo project_context (the original exclusion reason). feature-ideation → incubator: add caller stub (@v1-stable) + project_context + Discussions/Ideas #813's incubator-specific content (project_context text + Discussions/Ideas category setup) is still its own concern; Make initiative-driver / pr-auto-review / feature-ideation standard deployable shims (+ canonical-PAT migration) #836 only makes the delivery mechanism carry the stub.
• Also closes the last consumer-shim gap for GH_PAT_WORKFLOWS retirement (.github-private#1326): initiative-driver + pr-auto-review consumers converge on the sweep; feature-ideation's tuned copies are deferred to #1326's per-repo pass (they keep their body).