[Phase 4] Document the initiative→implementation cross-repo path: pipeline diagram + driver runbook

[github-actions]

Story

As a maintainer / operator,
I want have the in-repo pipeline diagram and the driver runbook show the initiative→implementation cross-repo path and how to enroll/operate the fleet driver,
so that operators understand the cross-repo release path and can enroll, arm, and run the fleet driver confidently.

Acceptance Criteria

1. docs/initiatives/idea-to-initiative-pipeline.md's 'Fleet enablement' section is extended to show the initiative→implementation half cross-repo: the per-repo initiative-driver stub dispatching the central driver with target_repo, mirroring the existing planner-stub fleet diagram.
2. docs/initiatives/agentic-release-strategy-orchestration.md (the driver runbook) documents the target_repo parameterization, the per-repo stub, and how a fleet repo enrolls + arms an epic cross-repo.
3. The docs restate the safety properties unchanged by fleet-enablement (initiative:auto master switch, dev-lead:hands-off / initiative:hold, MAX_IN_FLIGHT cap, the PAT requirement) and the no-new-LLM-cost bound, and cross-reference (not duplicate) the ci-standards.md §10 enrollment runbook updated in Story 2.

Tasks / Subtasks

• Extend the Fleet enablement section/diagram in idea-to-initiative-pipeline.md to include the driver stub → central driver (target_repo) leg. (AC: test issue from agent #1)
• Add a target_repo / fleet-enrollment subsection to agentic-release-strategy-orchestration.md's runbook. (AC: Go-live improvements for PR review agent #2)
• Restate the safety gates + cost bound and cross-link the cross-repo ci-standards §10 runbook. (AC: Add @claude delegation, auto-merge, and rebase handling #3)

Dev Notes

• Both files are in THIS repo (docs/initiatives/), so this story is dev-lead-authorable. The cross-repo ci-standards.md §10 enrollment runbook is updated in Story 2 (hands_off, in petry-projects/.github) — cross-reference it here, do not duplicate it.
• Match the existing ASCII-diagram style in idea-to-initiative-pipeline.md (the 'Fleet enablement (any org repo)' block already shows the planner stub → reusable → central planner leg; add the symmetric driver leg).
• The orchestration doc already has a 'How the driver works' diagram and an 'Operating the driver (runbook)' section — extend those rather than starting fresh.

Project Structure Notes

Docs-only, in .github-private. No code or workflow changes.

References

• docs/initiatives/idea-to-initiative-pipeline.md#fleet-enablement
• docs/initiatives/agentic-release-strategy-orchestration.md#operating-the-driver-runbook

Likely target surface

• docs/initiatives/idea-to-initiative-pipeline.md
• docs/initiatives/agentic-release-strategy-orchestration.md

Story prepared by the BMAD Scrum Master (Bob) for epic #882. Status: ready-for-dev.

[don-petry]

Dev-Lead Implementation Plan

Issue: #887 — [Phase 4] Document the initiative→implementation cross-repo path: pipeline diagram + driver runbook

Scope

Docs-only: extend the Fleet enablement diagram in idea-to-initiative-pipeline.md with the symmetric initiative-driver leg (per-repo driver stub → central driver -f target_repo=<fleet repo>), and add a target_repo/fleet-enrollment subsection to the driver runbook in agentic-release-strategy-orchestration.md — restating the unchanged safety gates + no-new-LLM-cost bound and cross-referencing (not duplicating) ci-standards.md §10.

Implementation Checklist

• docs/initiatives/idea-to-initiative-pipeline.md — extend the "Fleet enablement (any org repo)" ASCII diagram + notes to add the driver-stub → central-driver(target_repo) leg, symmetric to the existing planner-stub leg. (AC test issue from agent #1)
• docs/initiatives/agentic-release-strategy-orchestration.md — add a "Fleet enablement: target_repo & cross-repo enrollment" subsection extending the "How the driver works" diagram and "Operating the driver (runbook)" section: document target_repo parameterization, the per-repo stub, and how a fleet repo enrolls + arms an epic cross-repo. (AC Go-live improvements for PR review agent #2)
• Restate the unchanged safety properties (initiative:auto master switch, dev-lead:hands-off/initiative:hold, MAX_IN_FLIGHT cap, the PAT requirement) and the no-new-LLM-cost bound; cross-link the cross-repo ci-standards.md §10 enrollment runbook (do not duplicate it). (AC Add @claude delegation, auto-merge, and rebase handling #3)

Tests to Write

• None — pure documentation change with no observable behavioral change (Phase 2 exception per CLAUDE.md/dev-lead workflow).

Test Command

bash ".dev-lead/scripts/dev-lead-lint.sh" (shellcheck + agent frontmatter; no test suite covers docs)

[don-petry]

Dev-Lead: Implementation Complete

Plan Execution

• Extended the "Fleet enablement (any org repo)" ASCII diagram in idea-to-initiative-pipeline.md with the symmetric initiative-driver leg: per-repo initiative-driver.yml stub → initiative-driver-reusable.yml → central driver -f target_repo=<fleet repo> → cross-repo dev-lead release, plus a "two legs are symmetric" note and an updated target_repo / regression-detection bullet (now naming initiative-driver-canary.yml). (AC test issue from agent #1)
• Added a "Fleet enablement: cross-repo enrollment (target_repo)" section to agentic-release-strategy-orchestration.md documenting the target_repo parameterization, the per-repo stub, and how a fleet repo enrolls + arms an epic cross-repo; also added a target_repo bullet under "How the driver works". (AC Go-live improvements for PR review agent #2)
• Restated the unchanged safety properties (initiative:auto master switch, dev-lead:hands-off/initiative:hold, MAX_IN_FLIGHT cap, the PAT requirement) and the no-new-LLM-cost bound in a "Safety & cost are unchanged by fleet enablement" subsection, and cross-referenced — not duplicated — the petry-projects/.github → standards/ci-standards.md §10 enrollment runbook (Story 2). (AC Add @claude delegation, auto-merge, and rebase handling #3)

Test Results

Docs-only change with no observable behavioral change → Phase 2 (test-first) skipped per the workflow's documentation exception. No test suite covers prose docs. Verification used the required repo lint plus the markdownlint baseline rules enforced in CI:

[lint] shellcheck on 74 file(s)...
[lint] validating 4 agent profile(s)...
[lint] validating .github/CODEOWNERS...
[lint] all checks passed

Also confirmed: no trailing whitespace, no hard tabs in the changed files; markdownlint config (.markdownlint-cli2.jsonc) has no new violations (line-length 400 not exceeded; no duplicate headings; MD022/MD031/MD032 disabled in baseline). markdownlint-cli2 is not installed locally so it could not be executed directly.

Files Changed

• docs/initiatives/idea-to-initiative-pipeline.md: extended Fleet enablement diagram + notes with the driver leg, symmetry note, target_repo clarification, and driver-canary regression note.
• docs/initiatives/agentic-release-strategy-orchestration.md: added the cross-repo target_repo bullet under "How the driver works" and a full "Fleet enablement: cross-repo enrollment" section incl. the unchanged safety/cost restatement and the §10 cross-reference.

Notes

The reusable/channel-tag name (initiative-driver-reusable.yml / @initiative-driver/stable) and the §10 enrollment runbook are owned by petry-projects/.github (Story 2, hands_off); these docs intentionally reference them rather than define them, matching the existing planner-leg convention. No code or workflow changes.