nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

zara-coding: verify exact changed paths through SPEC #451

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-changed-path-verify into main
pull from: rage/1-zara-coding-changed-path-verify
merge into: nsaspy:main
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-08 02:19:59 +00:00
Owner
Copy link

Advances #1 with another dependency-ready local verification slice.

RAGE transaction

  • RED-first a935464: require bounded changed-path evidence plus a pure repository_changed_path/1 provider.
  • implementation b5011e8, 03e9a00, 048cb92, 6aec205, 5accd73: project at most 100 current changed paths, carry only structured path strings across the Prolog bridge, and reconcile exact path membership through canonical pure SPEC verification.
  • focused bridge coverage fd00541 proves the payload shape and bound.

Contract

  • exact repository-relative path membership against current HEAD; tracked and untracked paths come from the existing repository snapshot.
  • maximum 100 changed paths in verification evidence; malformed/NUL/oversized evidence fails closed before Prolog.
  • root identity is preserved in the assertion/evaluator so evidence from another repository cannot satisfy it.
  • no patch contents, arbitrary Git args, shell, filesystem collection from Prolog, mutation, or repair authority.

Cross-plugin PLAN/BUILD/EXECUTE remains blocked on Zara Core #400; this slice only strengthens local observed verification.

Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and all package builds before merge.

Advances #1 with another dependency-ready local verification slice. ## RAGE transaction - RED-first `a935464`: require bounded changed-path evidence plus a pure `repository_changed_path/1` provider. - implementation `b5011e8`, `03e9a00`, `048cb92`, `6aec205`, `5accd73`: project at most 100 current changed paths, carry only structured path strings across the Prolog bridge, and reconcile exact path membership through canonical pure SPEC verification. - focused bridge coverage `fd00541` proves the payload shape and bound. ## Contract - exact repository-relative path membership against current `HEAD`; tracked and untracked paths come from the existing repository snapshot. - maximum 100 changed paths in verification evidence; malformed/NUL/oversized evidence fails closed before Prolog. - root identity is preserved in the assertion/evaluator so evidence from another repository cannot satisfy it. - no patch contents, arbitrary Git args, shell, filesystem collection from Prolog, mutation, or repair authority. Cross-plugin PLAN/BUILD/EXECUTE remains blocked on Zara Core #400; this slice only strengthens local observed verification. Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and all package builds before merge.
Some checks failed
CI / test (pull_request) Failing after 16s
Details
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-changed-path-verify:rage/1-zara-coding-changed-path-verify
git switch rage/1-zara-coding-changed-path-verify

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-changed-path-verify
git switch rage/1-zara-coding-changed-path-verify
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-changed-path-verify
git switch rage/1-zara-coding-changed-path-verify
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-changed-path-verify
git switch main
git merge --squash rage/1-zara-coding-changed-path-verify
git switch main
git merge --ff-only rage/1-zara-coding-changed-path-verify
git switch main
git merge rage/1-zara-coding-changed-path-verify
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara-plugins!451
No description provided.