docs(status): add support tiers and claim-proof map#243
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Droid finished @EffortlessSteven's task —— View job Droid review validation complete ✓ Review Summary: Results:
|
| | Manifest-level topological publish planning | stable | Planner regression tests; `shipper plan`; roadmap #109 | engine | | ||
| | File-policy enforcement | stable/internal | `cargo xtask check-file-policy --mode blocking-allowlist`; `cargo xtask policy-report`; CI `Policy` job | release/ci | | ||
| | Rust 1.95 / 0.4 policy floor | stable/internal | Workspace lints; `cargo xtask check-lint-policy`; `cargo clippy --workspace --all-targets --all-features -- -D warnings` | rust/lints | | ||
| | No-panic production baseline | stable/internal | `cargo xtask no-panic check`; `policy/no-panic-baseline.toml` | rust/lints | |
There was a problem hiding this comment.
[P1] Incorrect no-panic baseline filename
The proof source for "No-panic production baseline" references policy/no-panic-baseline.toml, but the actual file is policy/no-panic-baseline.json. The no-panic-baseline.json is machine-generated and linguist-marked in .gitattributes; no-panic-baseline.toml does not exist in the repository. This will cause maintainers following the proof command to receive a file-not-found error.
| | No-panic production baseline | stable/internal | `cargo xtask no-panic check`; `policy/no-panic-baseline.toml` | rust/lints | | |
| | No-panic production baseline | stable/internal | `cargo xtask no-panic check`; `policy/no-panic-baseline.json` | rust/lints | |
| | Trusted Publishing default | planned/advisory | Future Trusted Publishing spec and #96 | release/ci | | ||
|
|
||
| ## Rules | ||
|
|
There was a problem hiding this comment.
[P1] Proof source references non-existent file
The claim "0.4.0 release readiness proof" lists docs/release/0.4.0-readiness.md as its proof source, but the docs/release/ directory does not exist and no such file is present in the repository. Since this file's purpose is to be the claim-to-proof map for Shipper, a proof source pointing to a file that cannot be found undermines the document's verifiability — even though the claim is correctly marked as planned until #195.
| | 0.4.0 release readiness proof | planned until #195 | Future `docs/release/0.4.0-readiness.md` (pending #195) | release/ci | |
Summary
docs/status/SUPPORT_TIERS.mdas the initial claim-to-proof mapScope boundary
This is PR 5 only: the support-tier model and initial claim map. It intentionally does not add ADRs, active goals, checker code, CI wiring, README claim changes, or #195 release proof work.
Validation
cargo fmt --all -- --checkcargo xtask check-file-policy --mode blocking-allowlistcargo xtask policy-report