Repository navigation
Conversation
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.
Gate-3 release-audit finding (two independent rounds, dispatch tokens 7cf3acd0c77ea2f3 and a69f445acec9e55b) against the v0.44.1..HEAD delta, logged as a trap.d/ fragment per the non-blocking routing rule in skills/manager/phases/findings.md (ranking-table row:
misreports, can ship behind a trap.d fragment).What
#1083's pointer-store route in scripts/write-handoff.sh skips the pre-existing #750/#799 tracked/symlinked-ancestor write refusal, in the ordinary #776 subdirectory-project shape. Round 2 reproduced this with a control (not just reasoned): a tracked
.remember/remember.mdin a subdirectory project got silently overwritten through the pointer route, where the un-pointered path correctly refuses with "REFUSED: ... tracked".See the fragment body for the full repro, the doctor.sh secondary site, and the fix direction (derive
_WH_MEM_PROJfrom the pointer's own store rather than the cwd guess).Why this is not blocking the v0.45.0 release
The ranking table in skills/manager/phases/findings.md puts
misreportsin the "can ship behind a trap.d fragment" row, not the blocking row. gate3_disposition.py confirmedcarry-forward-and-proceedfor round 2.No code change in this PR -- documentation only, for a later curation pass to promote into a jit-context rule or a tracked issue.
[AI-generated]