zara-coding: reject escaping changed paths at VERIFY boundary #439

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-verify-path-boundary into main
Owner

Advances #1 with defense-in-depth at the verifier seam. Even if observed evidence is tampered after collection, absolute or parent-traversing changed paths are rejected before Prolog-RLM receives them.

RAGE transaction

  • RED-first f89ca221: proves tampered escaping changed paths must fail before verifier execution.
  • implementation e342cf33: enforces repository-relative path identity inside _changed_path_payload().

No execution or authorization expansion. Exact-head compatibility, full registry/plugin checks, and generated Nix package builds remain mandatory before merge.

Advances #1 with defense-in-depth at the verifier seam. Even if observed evidence is tampered after collection, absolute or parent-traversing changed paths are rejected before Prolog-RLM receives them. ## RAGE transaction - RED-first `f89ca221`: proves tampered escaping changed paths must fail before verifier execution. - implementation `e342cf33`: enforces repository-relative path identity inside `_changed_path_payload()`. No execution or authorization expansion. Exact-head compatibility, full registry/plugin checks, and generated Nix package builds remain mandatory before merge.
Some checks failed
CI / test (pull_request) Failing after 17s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/1-zara-coding-verify-path-boundary:rage/1-zara-coding-verify-path-boundary
git switch rage/1-zara-coding-verify-path-boundary

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/1-zara-coding-verify-path-boundary
git switch rage/1-zara-coding-verify-path-boundary
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-verify-path-boundary
git switch rage/1-zara-coding-verify-path-boundary
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-verify-path-boundary
git switch main
git merge --squash rage/1-zara-coding-verify-path-boundary
git switch main
git merge --ff-only rage/1-zara-coding-verify-path-boundary
git switch main
git merge rage/1-zara-coding-verify-path-boundary
git push origin main
Sign in to join this conversation.
No description provided.