Repository navigation
coding: tell a later attempt which files an earlier attempt already changed (#377) - #380
Merged
Merged
Conversation
Owner
Author
|
Adversarial review: no HIGH or MEDIUM findings. The note is added only for a revision after the first that has changed files from the pre-coding capture, and only for in-scope paths that pass ValidatePath. The paths are JSON-quoted, capped at 20, then 'and N more'. It's derived at run time, so the plan digest and the adapter protocol are unchanged, and the ledger records a note with the file count. LOW: changed files outside the approved scope are filtered out of the list silently. Scope audit catches them anyway. The branch is based on 56fb4c2; main has since gained only the docs-only #378. |
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.
Implements issue #377.
Molecule:
mol-377-0bca488ed1b2d9bd2682e0bdFormula:
forgecell-github-issueBase:
56fb4c2cbe6e4c807e0e7eeec843812e92c11a67Delivery:
c6e06cc5f92926cd23532984c3b6a16c1e3b99a1Awaiting exact-commit CI and human review. Harness-reported checks are not independent CI evidence. No merge, deployment or issue closure is authorized.