Repository navigation
Fix generated-output warnings and validate explicit directory references with retained evidence - #94
Merged
Merged
Conversation
…ences; freeze fresh-source smoke plan
…and retain the failed replay
…verified delivery
…d artifact integrity checks
LE0-Lin
changed the title
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
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.
The published scanner warns about Vitest's explicitly declared generated contributor file in an unbuilt checkout. The new source recognizes a complete generated-output declaration for that one prose reference while continuing to check generator paths, actual Markdown destinations, commands and credentials. Directory prose is checked only with an explicit
./or../prefix plus a trailing slash; a regular file cannot satisfy it and there is no directory suffix fallback.The installed Linux replay retains the before/after observations and two earlier directory attempts. The first attempt failed on a bare build-output reference; a wider inspection exposed two more ambiguous package/install-time paths. The final scope leaves unprefixed directory names unresolved, keeps the original unchanged-text controls at 3/8, and tests four separate explicit-spelling variants (4/4 detected). Original selected natural occurrences stay at zero flags, whole-document comparison adds zero warnings, and the known generated-output warning disappears. These are development controls, not general accuracy results or upstream defects. A separate fixed three-repository collection yielded zero eligible path candidates; all exclusions and source bytes remain recorded.
Adds runtime, failure-path, provenance and report-integrity tests; automatic retention even for failed replay acceptance; English/Simplified/Traditional path-boundary documentation; a reader-oriented case study; and a mapping from Jason's public issue #46 requirements to existing functionality. The mapping establishes externally authored requirements without claiming adoption, independent review or time savings. No new messages are sent to maintainers.
Validation: full local source suite after final runtime scope changes (667 tests, 13 platform skips); final focused replay/artifact checks (4 passed); installed Linux CI replay and three-platform package checks passed on the same runtime fingerprint. Final CI also includes the new report-integrity test. Runtime version and published PyPI v0.26.1 remain unchanged; unreleased source is identified separately by fingerprint.