Docs: correct stale CI Miri description in AGENTS.md - #65
Draft
chbaker0 wants to merge 1 commit into
Draft
Conversation
The expensive/Miri job is conditionally skipped when a PR touches no Miri inputs, and a daily cron forces the full suite for nightly-drift coverage; AGENTS.md described it as running on every push/PR.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #64.
What changed
Corrects the CI Miri (
expensive) job description inAGENTS.md, in both the "Project status" and "Verifying changes" sections. Metadata-only; no code changes.Why
The docs described Miri as running on every push/PR, but
.github/workflows/ci.ymlshows otherwise:shared/**,Cargo.lock,Cargo.toml,.cargo/config.toml,rust-toolchain,ci.yml) — adorny/paths-filtergate.schedule:cron (06:00 UTC) forces the full Miri suite unconditionally to catch dateless-nightlydrift the path filter can't see — relevant to the heavily-documented nightly-drift hazard, and previously undocumented.Both behaviors predate the last metadata touch, so this is a standing documentation gap rather than a fresh regression. See #64 for the full audit, including minor items intentionally left as-is and two "flag, don't implement" tooling breadcrumbs.
🤖 Generated with Claude Code
Generated by Claude Code