Repository navigation
Address audit remediation bundle - #114
Conversation
|
Warning Review limit reached
Next review available in: 24 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (39)
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 |
|
@codex review please |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a2ec1683c7
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Self-Code Review Findings@codex please confirm this review finding before merge.
Additional checks run during review:
|
|
Resolved the P3 topic-shelf reference drift in cbb7b5e. Updated CLI, fixtures, Target IR, documentation, and tests topic shelves to cite the split xtask owners ( |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cbb7b5e37d
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex self-audit follow-up for latest local fixes:
|
Activity Summary@codex follow-up review requested for the post-thread fixes.
RED evidence:
GREEN evidence:
Thread state: 4/4 PR review threads resolved via GraphQL. Local worktree clean before push; branch pushed to |
|
Summary
Testing
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b909cdb386
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if with_date.contains(" #[test]\n fn alpha_changelog_dates_match_release_policy()") { | ||
| " #[test]\n fn alpha_changelog_dates_match_release_policy()" | ||
| } else { | ||
| "fn alpha_changelog_dates_match_release_policy()" | ||
| }; |
There was a problem hiding this comment.
Preserve the existing changelog-date test attribute
When release-prep runs against the current xtask/src/tests.rs, the target function is top-level (#[test] immediately before fn alpha_changelog_dates_match_release_policy()), not indented. This fallback marker matches only the fn, so insert_before_once inserts the new boundary test between the existing #[test] and that function; the old attribute then attaches to the new stub and the alpha changelog/date guard stops running, even though the command also adds a new date case there. Match the unindented attribute-plus-function pair, or insert before the attribute, so scaffolding does not silently disable the existing guard.
Useful? React with 👍 / 👎.
Summary
Addresses the audit omnibus as twelve focused remediation slices, each committed separately with RED/GREEN evidence and a self-review before moving to the next item.
Closes #84
Closes #85
Closes #86
Closes #87
Closes #88
Closes #91
Closes #92
Closes #93
Closes #94
Closes #95
Closes #99
Closes #100
What Changed
inputRootconfinement for path, path-list, directory, and glob inputs.Serializestructs while preserving byte-for-byte goldens.unwrap/expectinedict-cliproduction targets and documented the parserself.expecthelper as fallible parsing vocabulary.cargo deny checksupply-chain gate anddeny.tomlpolicy.cargo xtask cli-goldens --check/--writeand wired check mode intocargo xtask verify.cargo xtask release-prep <version>for mechanical release-prep scaffolding.xtaskout of the single-file shape into focused modules plus relocated tests.RED/GREEN Evidence
cargo test -p edict-cli input_root_rejects_path_outside_configured_rootfailed before root confinement existed.cargo test -p edict-cli,cargo xtask contract-check,cargo xtask verify.bash -lc '! rg -n "record\\[" crates/edict-cli/src/main.rs'failed while records were still mutated by JSON indexing.cargo test -p edict-cli, contract-check, markdown checks.unwrap/expectlint policy and parserself.expectdocs failed.cargo clippy -p edict-cli --lib --bin edict -- -D warnings, CLI tests.test -f deny.tomlfailed.cargo deny check, CI YAML parse checks,cargo xtask contract-check.rg -n 'format!\\("\\.\\{extension\\}"\\)' crates/edict-cli/src/main.rsfound the per-file allocation.cargo xtask cli-goldens --checkfailed as an unknown command.cargo xtask cli-goldens --check,cargo xtask cli-goldens --write,cargo test -p xtask,cargo xtask verify.cargo test -p xtask release_prep_scaffolds_version_policy_changelog_and_test_stubfailed missing release-prep scaffolding.cargo test -p xtask, xtask clippy, contract-check, markdown checks,cargo xtask verify.test -f ARCHITECTURE.mdfailed.cargo xtask verify.test -f docs/topics/core-ir/canonical-encoding.mdfailed.cargo xtask verify.test -f docs/design/crate-scope-v0.11.mdfailed.cargo xtask verify.test -f docs/design/schema-as-sot-codegen.mdfailed.cargo xtask verify.test -f xtask/src/tests.rsfailed before the split. Self-review RED:cargo test -p xtask release_prep_scaffolds_version_policy_changelog_and_test_stubfailed because release-prep still targetedxtask/src/main.rs.cargo test -p xtask release_prep_,cargo test -p xtask,cargo clippy -p xtask --all-targets -- -D warnings, contract-check, markdown checks,cargo xtask verify.cargo xtask verifyexposedgit diff --checkfailure from a trailing blank line in the new CLI fixture.cargo xtask verify.Final Verification
cargo xtask verifypassed on a clean tree after the final commit.cargo test -p xtaskpassed after the xtask split.cargo clippy -p xtask --all-targets -- -D warningspassed after the xtask split.cargo xtask contract-checkpassed with 21 topic shelves.Notes
Fix: remove CLI fixture trailing blank line) because the full gate found whitespace drift after the Document the CLI trust boundary + optional input-path root confinement #95 fixture landed.xtask/src/main.rs(3,052-line single file) into modules + split tests #85 self-review found and fixed a real split regression: release-prep now writes generated boundary tests toxtask/src/tests.rs, not dispatch-onlyxtask/src/main.rs.