Skip to content

ci: add canonical FCRP credential boundary - #221

Draft
safal207 wants to merge 2 commits into
mainfrom
agent/fcrp-boundary-rollout-20260814
Draft

ci: add canonical FCRP credential boundary#221
safal207 wants to merge 2 commits into
mainfrom
agent/fcrp-boundary-rollout-20260814

Conversation

@safal207

@safal207 safal207 commented Aug 14, 2026

Copy link
Copy Markdown
Owner

FCRP credential-boundary rollout

Adds the thin caller workflow for the canonical ContractGraph-QA credential-boundary scanner.

  • Consumer repository: safal207/ProofPath
  • Provider workflow ref: cc1d1e227bbb1a25776819e6f2829bfb7a66ee58
  • Explicit scanner-ref: cc1d1e227bbb1a25776819e6f2829bfb7a66ee58
  • Permissions: contents: read only
  • This PR does not add, read, or rotate credentials.
  • The branch is intentionally isolated; merge only after the provider and consumer checks are reviewed.

Routing follows RESONANCE Signal 013: journal → divergence classification → minimum verification lanes → native contract → verifier/path check → append-only result.

@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 31c145b6-1584-47bb-b658-bc135925460e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

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.

1 participant