Rollout: feature-ideation channel/ring rollout fleet-wide (#866)

[don-petry]

Operational tracker for the fleet-wide canary rollout of feature-ideation — the outer, cross-repo half of Initiative petry-projects/.github-private#866. The in-repo .github-private half (epic #872: fold enhancement mode, deprecate idea-enhancer, repin .github-private → feature-ideation/next) is DONE; this issue owns the remaining 8-repo rollout that #872 explicitly left as untracked prerequisites.

Mirrors the shape of the idea→initiative rollout tracker #515. The release-channel standard and the template/audit channel-ify are separate work (#606) — this issue is the operational rollout only.

Current state (verified 2026-07-04)

Channel tag on .github	Exists?
feature-ideation/next	✅ (+ immutables v1.0.0, v1.1.0)
feature-ideation/ring0	❌ not cut
feature-ideation/ring1	❌ not cut
feature-ideation/stable	❌ not cut

Repo	Assigned ring	Current pin	On-channel?
.github-private	next	@feature-ideation/next	✅
.github	ring0	@3500ed2 # v1	❌
TalkTerm	ring1	@v1	❌
markets	stable	@c2bece # v1	❌
broodly	stable	@c2bece # v1	❌
google-app-scripts	stable	@c2bece # v1	❌
bmad-bgreat-suite	stable	@v1 (bare)	❌
ContentTwin	stable	no feature-ideation.yml	❌

⛔ Hard blocker

• feature-ideation: discussion-triggered run fails at workflow setup (zero jobs) — discussion→dispatch bridge #571 — discussion→dispatch bridge fails at setup (zero jobs). Every Ideas-Discussion-triggered feature-ideation run currently fails at compile. This blocks live per-ring validation and therefore all ring promotion below. Must be fixed first.

Work items

A. Cut the missing channel tags on petry-projects/.github

• Cut feature-ideation/ring0, feature-ideation/ring1, feature-ideation/stable via scripts/cut-release.sh (same mechanism as next). Depends on Story (B): channel-ify feature-ideation + pr-auto-review [#604] #606 adding feature-ideation to RING_REUSABLES in scripts/lib/ring-pins.sh.

B. Repin the fleet, one repo at a time, walking the rings (each via PR)

• .github → @feature-ideation/ring0
• TalkTerm → @feature-ideation/ring1
• markets → @feature-ideation/stable
• broodly → @feature-ideation/stable
• google-app-scripts → @feature-ideation/stable
• bmad-bgreat-suite → @feature-ideation/stable (replace bare @v1)

C. Onboard the repos that lack the workflow

• ContentTwin — add feature-ideation.yml stub with tailored project_context, enable Discussions + Ideas category, pin @feature-ideation/stable.
• bmad-bgreat-suite — confirm Discussions + Ideas category enabled (workflow present but on bare @v1).

D. Widen the standard from BMAD-only → "Discussions + Ideas category"

• Update the ci-standards §9 clause (and scripts/compliance-audit.sh check_centralized_workflow_stubs) so feature-ideation is required on all repos with Discussions + an Ideas category, not just repos with a _bmad/ marker. Coordinate the audit change with Story (B): channel-ify feature-ideation + pr-auto-review [#604] #606 (which flips the feature-ideation entry to the RING sentinel).

E. Per-ring validation before each promotion (#866 acceptance)

• For each ring, run dry_run then a live run against a real, already-open, un-enhanced Ideas Discussion; confirm: exactly one enhancement comment, idempotency marker written, second run is a no-op, bot-authored ideas skipped. Candidates listed in chore: sync 1 org-standard workflow stub(s) from petry-projects/.github #866.
• Health-check each ring (per Rollout: idea→initiative pipeline — staged ring rollout #515 promotion gate: no new failures vs baseline) before promoting to the next.

Acceptance (rolls up to #866)

• All 8 repos pinned to their assigned feature-ideation/{next,ring0,ring1,stable} channel; the 2 missing repos onboarded with tailored project_context.
• ci-standards §9 widened + compliance-audit enforces it.
• Per-ring dry-run + live validation recorded; each ring health-checked before promotion; documented rollback = revert a channel tag to its prior immutable feature-ideation/vX.Y.Z.

Refs: initiative petry-projects/.github-private#866 · in-repo epic petry-projects/.github-private#872 (DONE) · template/audit channel-ify #606 · blocker #571 · pattern #515.

[don-petry]

Update — #571 blocker cleared; next-ring caller fixed ✅

The hard blocker (#571, discussion→dispatch bridge failing at setup) is fixed and merged:

• fix(feature-ideation): route caller inputs through a prep job (#571) #615 — fixed the canonical template + added the lint-caller.sh guard (fails any job-level reusable with: referencing the inputs context) wired into CI, so the anti-pattern can't regress into future repins.
• fix(feature-ideation): route caller inputs through a prep job (#571) .github-private#1113 — fixed the next-ring dogfood caller and its compliance test.

Live-validated on .github-private (next ring): a real Ideas Discussion now produces a working run (redispatch → dispatch, jobs created) instead of a zero-job startup failure.

Impact on this rollout

• Item B/C repins & onboards must now re-sync each repo's caller to the fixed template shape (prep job → needs.prep.outputs.*). The other repos' callers still carry the latent inputs.* pattern until repinned — lint-caller.sh will catch any that don't.
• The stable-ring enrollment gate (markets/broodly/google-app-scripts/ContentTwin/bmad-bgreat-suite) is no longer blocked by feature-ideation: discussion-triggered run fails at workflow setup (zero jobs) — discussion→dispatch bridge #571.

Remaining work items A–E unchanged; the blocker checkbox can be marked done.