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

zara-coding: verify worktree cleanup through SPEC #452

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-worktree-absent into main
pull from: rage/1-zara-coding-worktree-absent
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 a second dependency-ready local verification slice after #111.

RAGE transaction

  • RED-first 2dd9659: define a trusted worktree_absent/1 verification contract.
  • implementation 00f6a12 + 8ae02a4: register the pure provider/evaluator and project absence from the same bounded current Git worktree inventory already used by repository verification.

Contract

  • worktree_absent accepts exactly one structured path argument.
  • absence is derived only from the current bounded worktree inventory; inventory overflow/malformed evidence already fails closed before verification.
  • a matching registered worktree yields present:true and therefore fails the assertion; no match yields present:false and passes.
  • no Prolog filesystem collection, assertz, shell, mutation, worker identity claim, or plugin-private authorization path is introduced.

This gives cleanup/completion SPECs a way to prove a task worktree is gone without pretending Git's coordination locks establish principal ownership. Cross-plugin worker/principal composition remains correctly blocked on Zara Core #400.

Exact-head CI must pass whitespace, Zara compatibility, the full generated registry/plugin Nix gate, and package builds before merge.

Advances #1 with a second dependency-ready local verification slice after #111. ## RAGE transaction - RED-first `2dd9659`: define a trusted `worktree_absent/1` verification contract. - implementation `00f6a12` + `8ae02a4`: register the pure provider/evaluator and project absence from the same bounded current Git worktree inventory already used by repository verification. ## Contract - `worktree_absent` accepts exactly one structured `path` argument. - absence is derived only from the current bounded worktree inventory; inventory overflow/malformed evidence already fails closed before verification. - a matching registered worktree yields `present:true` and therefore fails the assertion; no match yields `present:false` and passes. - no Prolog filesystem collection, `assertz`, shell, mutation, worker identity claim, or plugin-private authorization path is introduced. This gives cleanup/completion SPECs a way to prove a task worktree is gone without pretending Git's coordination locks establish principal ownership. Cross-plugin worker/principal composition remains correctly blocked on Zara Core #400. Exact-head CI must pass whitespace, Zara compatibility, the full generated registry/plugin Nix gate, and 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-worktree-absent:rage/1-zara-coding-worktree-absent
git switch rage/1-zara-coding-worktree-absent

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-worktree-absent
git switch rage/1-zara-coding-worktree-absent
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-worktree-absent
git switch rage/1-zara-coding-worktree-absent
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-worktree-absent
git switch main
git merge --squash rage/1-zara-coding-worktree-absent
git switch main
git merge --ff-only rage/1-zara-coding-worktree-absent
git switch main
git merge rage/1-zara-coding-worktree-absent
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!452
No description provided.