feat: implement issue #820 — Per-repo caller stub + cross-repo redispatch

[don-petry]

Closes #820

Implemented by dev-lead agent. Please review.

Summary by CodeRabbit

• Chores
  • Enhanced the continuous integration testing infrastructure by including additional automated test coverage in the lint workflow.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0bb81582-9939-4a5d-8c77-7396cd98683b

📥 Commits

Reviewing files that changed from the base of the PR and between d5bbbae and f308a14.

📒 Files selected for processing (1)

• .github/workflows/lint.yml

---

📝 Walkthrough

Walkthrough

Adds tests/test_initiative_planner_redispatch.bats to the list of Bats test files passed to scripts/run-bats.sh in the bats job of the GitHub Actions Lint workflow. No other workflow steps or jobs are changed.

Changes

Lint Workflow Bats Registration

Layer / File(s)	Summary
Register redispatch Bats test in lint workflow .github/workflows/lint.yml	tests/test_initiative_planner_redispatch.bats is appended to the scripts/run-bats.sh invocation in the bats job so CI executes the initiative planner redispatch tests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• #820 (Per-repo caller stub + cross-repo redispatch): AC #5 explicitly requires adding tests/test_initiative_planner_redispatch.bats; this PR wires that test file into CI.
• Initiative: Fleet-enable the idea→initiative pipeline (Option A — per-repo stub → central planner) #817: This PR implements part of the fleet-enablement initiative's testing infrastructure by registering the redispatch Bats test in the lint workflow.
• Live idea:approved canary + Fleet Monitor coverage #822: This PR directly supports validating the idea:approved → dispatch path by enabling CI to run the redispatch Bats test.

Possibly related PRs

• petry-projects/.github-private#480: Same pattern — extends the bats job's scripts/run-bats.sh test list with a new .bats file (test_verify_auth_scopes.bats).
• petry-projects/.github-private#827: Adds/expands tests/test_initiative_planner_redispatch.bats itself, which this PR registers in CI.
• petry-projects/.github-private#805: Also updates the lint workflow's bats job scripts/run-bats.sh invocation to add a new Bats test file via the same mechanism.

Suggested labels

needs-human-review

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR only updates .github/workflows/lint.yml to add a test file reference, but issue #820 requires creating a new workflow stub, extending redispatch.sh with TARGET_REPO argument, and adding comprehensive test coverage—none of which are present in this changeset.	Implement all acceptance criteria from issue #820: create standards/workflows/initiative-planner.yml stub, extend redispatch.sh to accept TARGET_REPO argument, add documentation, and include test cases for the target_repo parameter.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title references issue #820 and describes the main feature (per-repo caller stub + cross-repo redispatch), which aligns with the actual changes to the lint workflow and test file additions.
Out of Scope Changes check	✅ Passed	The lint.yml workflow update adding the test file reference is in scope as it supports testing for the feature, but the absence of the main feature implementation (workflow stub and script changes) indicates this PR is incomplete rather than out-of-scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev-lead/issue-820-20260620-0519

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-20T06:25:27Z.

[donpetry-bot]

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: 3cc4de3f8a4acef7e890f6f8a05a8f48fdb3936f
Review mode: triage-approved (single reviewer)

Summary

One-line CI change: registers the existing tests/test_initiative_planner_redispatch.bats in lint.yml's bats run list so the redispatch regression test is actually executed in CI. The substantive issue #820 work for this repo (redispatch.sh TARGET_REPO/-f target_repo support and the test file itself) already landed on main; this PR wires the test into CI enforcement.

Linked issue analysis

Closes #820 (Per-repo caller stub + cross-repo redispatch). That story spans two repos: the public petry-projects/.github stub (AC #1, #3) and the .github-private redispatch.sh + test work (AC #2, #4, #5). On the .github-private side, redispatch.sh already carries full TARGET_REPO support (lines 28/36/60/63/65 at head) and tests/test_initiative_planner_redispatch.bats already exists in main but was NOT in lint.yml's bats list — so it never ran in CI. This PR adds that one missing registration line, so AC #5's regression test (covering both the dogfood default target_repo=petry-projects/.github-private and the TARGET_REPO=acme/widgets fleet override) is now enforced. Verified the test passes via the green bats check.

Findings

No issues. Change is a single additive line with correct backslash line-continuation, inserted in the existing alphabetically-grouped bats list. The referenced test file exists at head (3165 bytes) and passes. Secret-scanning MCP tool was not permitted in this environment; noted and skipped — the gitleaks CI check passed and the added content is a test-file path with no secret material.

CI status

All required checks green: Lint, ShellCheck/shellcheck, bats (confirms the newly-registered test runs and passes), unit-tests, CodeQL (actions + python), SonarCloud (Quality Gate passed, 0 new issues), Agent Security Scan, gitleaks secret scan, validate-agent-profiles, AgentShield. Advisory bots (Codex, Gemini, CodeRabbit) did not produce findings — they were rate-limited or unsupported for the file type, not failures. mergeStateStatus is BLOCKED pending the required org-leads human review.

---

Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

[don-petry]

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #828
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-06-20T07:18:26Z

[don-petry]

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-06-20T07:18:26Z

[don-petry]

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning

Issues addressed: 0
- Quality Gate passed: no actionable issues identified
Files changed: none
Skipped (informational): SonarCloud Quality Gate (informational pass report)
```
**Conclusion:** The PR has no actionable bot findings to address. The SonarCloud Quality Gate passed with zero issues, all CI checks are passing or in-progress without failures, and both reviewers have approved. No changes are needed.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-20T07:55:38Z.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-20T08:04:10Z.