docs: list report.rs in CLAUDE.md architecture - #29
Open
cargo-affected-bot wants to merge 2 commits into
Open
Conversation
…port # Conflicts: # CLAUDE.md
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
1 participant
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.
src/report.rs(the--report-jsonartifact forrunandstatus, plus the cache-miss diagnostic that names which fingerprint component differs) is in the source tree but missing from CLAUDE.md's architecture list. New readers reach for the file from the existing entries (run.rscalls into it,status.rscalls into it) and find no overview pointer.This adds one line for
report.rsimmediately afterstatus.rs, matching the format of surrounding entries.Docs only — no code changes.
Note: PR #21 also refreshes a CLAUDE.md architecture entry (
shim.rsfor Windows). That one and this one are independent (either could be reverted without touching the other), so I've kept them as separate PRs per the repo's atomic-PR convention.