Configure agent workflow repo policy

[justin808]

Summary

• reconcile the explicitly registered policy key(s) in .agents/agent-workflow.yml
• preserve all command wrappers, AGENTS.md, CLAUDE.md, trust configuration, and unrelated policy keys

Generated by the policy-only fleet mode of bin/push-downstream from
shakacode/agent-workflows.

Validation

• agent-workflow-seam-doctor --root . --shared <agent-workflows-root>

QA Evidence

• QA lane: /root/source_evidence_checker; independent exact-head checker
• Scope checked: generated CPF repo-prefix policy diff, final nested-mapping boundary, and repository seam integrity
• Tested at: 3ecdec14bcf664ee5ace03ee6a11e42815390d25
• Automated checks: merged source deploy shows incorrectly names of containers, not workloads. works correctly, only incorrect info #255 seam doctor; exact one-file one-addition byte replay; exact-head hosted checks
• Manual checks: repo_prefix CPF matches merged registry; one style-only thread answered and resolved
• Findings: none
• QA required: yes
• QA required rationale: repository workflow seam change
• QA lane status: satisfied
• Release-blocking status: clear
• Process-gap disposition: script

[coderabbitai]

Warning

Review limit reached

@justin808, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a467e888-7759-4e2e-bf1d-d96dc675f33d

📥 Commits

Reviewing files that changed from the base of the PR and between 6496566 and 3ecdec1.

📒 Files selected for processing (1)

• .agents/agent-workflow.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent-workflows/repo-prefix

---

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.}

[claude]

Review Summary

What this PR does: Adds a single top-level key, repo_prefix: CPF, to .agents/agent-workflow.yml. This is an automated policy-reconciliation PR generated by the policy-only fleet mode of bin/push-downstream (from shakacode/agent-workflows), which syncs canonical policy keys into downstream repos while preserving repo-specific command wrappers, AGENTS.md/CLAUDE.md, and trust config.

Assessment: Low risk, mechanical, single-line config addition.

• Correctness: CPF is a sensible, unambiguous abbreviation for "Control Plane Flow," consistent with the repo name. No other file in the repo currently references repo_prefix, which is expected since it's consumed by the external portable shared-skill tooling rather than in-repo code.
• YAML structure: The key is syntactically valid — it sits at 0 indentation, correctly making it a top-level sibling of untrusted_contributor_intake rather than a nested child, despite appearing directly after that block.
• Security: No security implications — this is a plain config value, not a code path, and doesn't touch the trust-boundary logic documented for untrusted_contributor_intake.
• Performance: N/A for a one-line YAML config change.
• Test coverage: N/A — no executable logic introduced.

Minor nit (posted inline): Every other key in this file has either an inline value description or a comment block explaining its purpose/consumer. repo_prefix has neither, and its placement directly under the untrusted_contributor_intake comment block (which describes trust-boundary constraints that don't apply to repo_prefix) could read as if it inherits those constraints. Consider adding a short comment noting which shared skill/tool consumes this value, and/or moving it up next to the other top-level scalar keys for clarity.

Overall: safe to merge as-is; the placement/documentation nit is optional polish, not a blocker.

[greptile-apps]

Greptile Summary

Adds the repository prefix CPF to the agent workflow policy while leaving existing workflow and trust settings unchanged.

Confidence Score: 5/5

The PR appears safe to merge because the policy-only configuration change introduces no concrete failure.

The change adds one static repository prefix without modifying existing command wrappers, trust boundaries, or application runtime behavior.

Important Files Changed

Filename	Overview
.agents/agent-workflow.yml	Adds a single top-level repository prefix used by the external agent-workflow policy tooling; no concrete defect is evident.

_{Reviews (1): Last reviewed commit: "Configure agent workflow repo policy" | Re-trigger Greptile}