Skip to content

fix(positioning): point relays at canonical template - #2291

Merged
4444J99 merged 1 commit into
mainfrom
codex/psp-p00-w01-manifest
Aug 10, 2026
Merged

fix(positioning): point relays at canonical template#2291
4444J99 merged 1 commit into
mainfrom
codex/psp-p00-w01-manifest

Conversation

@4444J99

@4444J99 4444J99 commented Aug 10, 2026

Copy link
Copy Markdown
Member

Corrects the PSP program manifest so execution_chunks.relay_template names the canonical relay template. This addresses the manifest-pointer review finding on PR #2156 and supplies the implementation predicate for PSP-P00-W01 (#2159). Verification: python3 scripts/positioning-program.py --check; bash scripts/verify-scoped.sh.

Copilot AI lite review requested due to automatic review settings August 10, 2026 00:50
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 31 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8043f85e-920e-428c-8c33-36ad6a396045

📥 Commits

Reviewing files that changed from the base of the PR and between b604445 and bb1d670.

📒 Files selected for processing (1)
  • institutio/positioning/program.yaml

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

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

Multi-agent review roll call
@codex review

(CodeRabbit and Claude review automatically. Reviewers: post substantive findings only. Authors/agents: address every thread, push fixes to this branch, reply and resolve, then re-request review.)

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create a Codex account and connect to github.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Production Systems Program manifest to ensure execution_chunks.relay_template points at the canonical relay envelope template document, aligning the manifest’s pointer with the relay contract referenced by the positioning program tooling and execution chunk prompts.

Changes:

  • Repoint execution_chunks.relay_template from EXECUTION-CHUNKS.md to RELAY-TEMPLATE.md in the PSP program manifest.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@4444J99
4444J99 merged commit f86872f into main Aug 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants