Repository navigation
Description
Story
As a release engineer for the org agent fleet,
I want have scripts/cut-release.sh recognize feature-ideation as a releasable agent with the next/ring0/ring1/stable channels, and document it in the versioning + runbook docs,
so that feature-ideation can be cut and promoted through the same canary/ring tag model as pr-review and dev-lead, so callers pin once to a channel and promotion/rollback is a single tag move.
Acceptance Criteria
- valid_agent in scripts/cut-release.sh accepts
feature-ideation(alongside pr-review and dev-lead) and rejects unknown agents unchanged; its usage/error strings list feature-ideation. - release_ref and channel_ref produce
feature-ideation/vX.Y.Zandfeature-ideation/<channel>correctly, and a--dry-runfor feature-ideation prints the intended immutable + channel tag names without creating or pushing anything. - tests/test_cut_release.bats adds cases asserting feature-ideation is accepted and that release_ref/channel_ref format its tags correctly; the full bats file passes.
- docs/release/versioning.md documents the feature-ideation agent: its channel set {next, ring0, ring1, stable}, and an explicit note that — unlike pr-review/dev-lead whose reusables live in this repo — feature-ideation's reusable lives in petry-projects/.github, so its release/channel tags are cut against that repo.
- docs/release/runbook.md extends the 'Agents covered' line and the cut/promote/rollback examples to include feature-ideation.
- shellcheck scripts/cut-release.sh passes with no new findings.
Tasks / Subtasks
- Add
feature-ideationto the valid_agent case statement and update the usage/error messages in scripts/cut-release.sh. (AC: test issue from agent #1)- Confirm release_ref/channel_ref are agent-name-agnostic (they printf the name) so no change is needed beyond valid_agent.
- Make the feature-ideation dry-run path print the intended immutable + channel tag names without any mutation. Do NOT wire the live cross-repo push target yet — that mechanism is an open question reserved for a human decision; leave a TODO referencing it. (AC: Go-live improvements for PR review agent #2, Optimize review: small-PR and incremental fast paths #4)
- Extend tests/test_cut_release.bats with feature-ideation cases (valid_agent accepted; release_ref/channel_ref formatting). (AC: Add @claude delegation, auto-merge, and rebase handling #3)
- Update docs/release/versioning.md (What is versioned table + channels + cross-repo note) and docs/release/runbook.md (Agents covered + examples). (AC: Optimize review: small-PR and incremental fast paths #4, feat: add Copilot engine support via REVIEW_ENGINE toggle #5)
- Run shellcheck and the bats suite locally to confirm green. (AC: Add @claude delegation, auto-merge, and rebase handling #3, feat: feature ideation framework — adversarial proposer/challenger/synthesizer #6)
Dev Notes
- scripts/cut-release.sh structure: pure helpers (valid_agent, validate_version, release_ref, channel_ref) at top level (sourced by tests via a source-guard at the bottom), main() does the git tag/push. valid_agent currently matches
pr-review | dev-leadonly — addfeature-ideation. - release_ref()/channel_ref() are name-agnostic (
printf '%s/v%s'/printf '%s/%s'), so they already format feature-ideation tags once valid_agent allows the name. - CROSS-REPO WRINKLE: docs/release/versioning.md defines a 'release' as the reusable workflow PLUS the scripts it executes, moving together as one whole-repo commit — true for pr-review/dev-lead because those reusables live in THIS repo. feature-ideation's reusable lives in petry-projects/.github (see .github/workflows/feature-ideation.yml header: 'Reusable: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml'), so feature-ideation's release/channel tags must be cut against petry-projects/.github, not this repo's origin. main() currently hardcodes
git push origin. Suggested approach: add an optional remote/repo target (e.g. a--repo/remote arg) so feature-ideation tags push to petry-projects/.github; keep origin the default for pr-review/dev-lead. Do NOT bake the unresolved target mechanism into an AC — the dry-run (no mutation) is the testable surface here; confirm the target approach via the open question before wiring live pushes. - AGENTS.md 'Release channel tags & the mutable-ref exception' scopes the protective ruleset to
pr-review/**,dev-lead/**. feature-ideation's channel tags live on petry-projects/.github, so the ruleset bounding them is created there (untracked prerequisite). Add a sentence to this section noting feature-ideation channel pins are the same sanctioned exception and that their ruleset lives in the public repo. - Testing standard: bats unit tests source cut-release.sh (source-guard prevents main() from running) and exercise only the pure helpers — keep the new cases at that level (no git-backed flow in tests, matching the existing file's note).
- Pattern precedent: this mirrors the pr-review/dev-lead rollout in epic Initiative: Safe Release Strategy for Agentic Workflows (versioning · rings · canary) #495 (docs/initiatives/agentic-release-strategy.md) and the ci-failure-analyst generalization (open epics [Phase 1] Generalize cut-release.sh + the release standard to cover non-agent reusables #686/[Phase 2] Cut ci-failure-analyst initial release + channel tags and extend the release-channel ruleset #688).
Project Structure Notes
All touched files are in this repo: scripts/cut-release.sh, tests/test_cut_release.bats, docs/release/{versioning,runbook}.md, AGENTS.md. No new files. The only structural novelty is acknowledging an agent whose reusable lives in a different repo — captured as a documented cross-repo note rather than a structural change here.
References
- scripts/cut-release.sh#valid_agent
- tests/test_cut_release.bats
- docs/release/versioning.md#what-is-versioned
- docs/release/runbook.md#agents-covered
- AGENTS.md#release-channel-tags--the-mutable-ref-exception
- .github/workflows/feature-ideation.yml (header: Reusable in petry-projects/.github)
Likely target surface
scripts/cut-release.shtests/test_cut_release.batsdocs/release/versioning.mddocs/release/runbook.mdAGENTS.md
Story prepared by the BMAD Scrum Master (Bob) for epic #872. Status: ready-for-dev.
Activity
don-petry commentedon Jun 21, 2026
Dev-Lead Implementation Plan
Issue: #873 — [Phase 1] Extend cut-release.sh + release docs to cover the feature-ideation agent
Scope
Recognize
feature-ideationas a releasable agent inscripts/cut-release.sh(next/ring0/ring1/stable channels via the existing name-agnostic helpers), make its dry-run print the intended immutable + channel tag names with no mutation (cross-repo live push left as a TODO), and document it in the versioning + runbook docs and the AGENTS.md mutable-ref exception.Implementation Checklist
scripts/cut-release.sh: addfeature-ideationto thevalid_agentcase; update usage header + unknown-agent error string to list it. release_ref/channel_ref unchanged (already name-agnostic).scripts/cut-release.sh: add a TODO noting feature-ideation's reusable lives inpetry-projects/.github, so live channel pushes must target that repo (mechanism = open question; dry-run only for now).docs/release/versioning.md: add feature-ideation to the "What is versioned" table, document its channel set {next, ring0, ring1, stable}, and add the explicit cross-repo note (reusable in petry-projects/.github).docs/release/runbook.md: extend "Agents covered" and the cut/promote/rollback examples to include feature-ideation.AGENTS.md: add a sentence to "Release channel tags & the mutable-ref exception" noting feature-ideation channel pins are the same sanctioned exception and that their ruleset lives in the public repo.Tests to Write
tests/test_cut_release.bats:valid_agentacceptsfeature-ideation.tests/test_cut_release.bats:release_refformatsfeature-ideation/vX.Y.Z.tests/test_cut_release.bats:channel_refformatsfeature-ideation/<channel>(e.g. ring0).Test Command
bats tests/test_cut_release.bats(plusbash .dev-lead/scripts/dev-lead-lint.shandshellcheck scripts/cut-release.sh)don-petry commentedon Jun 21, 2026
Dev-Lead: Implementation Complete
Plan Execution
scripts/cut-release.sh: addedfeature-ideationtovalid_agent; updated usage header + unknown-agent error string. release_ref/channel_ref unchanged (already name-agnostic — confirmed).scripts/cut-release.sh: addedTODO(#872)cross-repo note + a guard that refuses a non-dry-run cut forfeature-ideation(so tags are never written to the wrong remote while the cross-repo push target is an open question).--dry-runprints the intended immutable + channel tags with no mutation.tests/test_cut_release.bats: addedvalid_agent(feature-ideation accepted),release_ref(feature-ideation/v1.4.0), andchannel_ref(feature-ideation/ring0) cases.docs/release/versioning.md: added feature-ideation to the "What is versioned" table, documented the{next, ring0, ring1, stable}channel set, and added a dedicated "Cross-repo: feature-ideation" section + dry-run example.docs/release/runbook.md: extended "Agents covered" and the cut/promote/rollback examples/notes for feature-ideation's cross-repo tags.AGENTS.md: added a paragraph to "Release channel tags & the mutable-ref exception" noting feature-ideation pins are the same sanctioned exception and that their ruleset lives inpetry-projects/.github.Test Results
17/17 pass, 0 failures.
bash .dev-lead/scripts/dev-lead-lint.sh→all checks passed(shellcheck on 72 files + agent-profile + CODEOWNERS validation).shellcheck scripts/cut-release.sh→ clean, no new findings.Manual dry-run verification:
Files Changed
scripts/cut-release.sh:feature-ideationaccepted byvalid_agent; usage/error strings updated; cross-repoTODO(#872)+ guard refusing live (non-dry-run) cuts.tests/test_cut_release.bats: +3 feature-ideation cases (valid_agent, release_ref, channel_ref).docs/release/versioning.md: table row, channel-set note, "Cross-repo: feature-ideation" section, dry-run example.docs/release/runbook.md: "Agents covered" + cut/promote/rollback cross-repo notes/examples.AGENTS.md: feature-ideation paragraph in the mutable-ref exception section.Notes
petry-projects/.github) is an open question reserved for a human decision and was deliberately not wired. Beyond the documented TODO, I added a guard that refuses a non-dry-runfeature-ideationcut so the script can never write tags to this repo'soriginby mistake;--dry-run(the testable surface in AC Go-live improvements for PR review agent #2) is fully supported.release-channel-tagsruleset boundingfeature-ideation/**must be created onpetry-projects/.github— documented in AGENTS.md and versioning.md, no action possible here.lint.ymlbats-list change is needed.feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…
feat: implement issue #873 — [Phase 1] Extend cut-release.sh + releas…