chore(release): add SLSA Build L2 attestation workflow + docs#130
Conversation
Propagated from KooshaPari/phenotype-registry @ chore/l7-001-curation-snapshot (a1aa44660). Files: docs/boundary/<repo>.md, docs/intent/<repo>.md These are read-only governance docs; do not edit locally.
Mechanical: curated-prompts table reorder (date / SHA sort). No code changes. No new dependencies. Just a doc refresh. Refs: plans/2026-06-17-v7-dag-stable.md §L7-001
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reached
More reviews will be available in 57 minutes and 23 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
Note
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ba51e31257
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| }, | ||
| "raw": { | ||
| "source": { | ||
| "total": 0, |
There was a problem hiding this comment.
Regenerate the scorecard from the actual repository tree
This scorecard was generated as if HeliosLab has no source code (source.total is 0 here, and the same file also reports zero tests), but the checked tree contains a Cargo workspace plus Rust/TypeScript sources under src/, pheno-*, and crates/, along with docs tests. Any dashboard or gate that consumes audit_scorecard.json will publish a false D+ and hide the real source/test health, so this should be regenerated from the repo root with the Rust/TS paths included before committing.
Useful? React with 👍 / 👎.
|



User description
Adds the missing SLSA Build L2 release-attestation workflow, docs/slsa.md, docs/index.md, and the Release Artifacts section in README.md. Matches the pattern from the other 14 focus repos.
Refs: FLEET_100TASK_DAG_V4.md V6 SLSA wave.
CodeAnt-AI Description
Refresh repo governance docs and add an audit scorecard
What Changed
Impact
✅ Clearer repo scope✅ Easier onboarding for contributors✅ Faster governance reviews💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.