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

zara-coding: verify worktree coordination locks through SPEC #453

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-worktree-verify into main
pull from: rage/1-zara-coding-worktree-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 by making linked-worktree lock state part of current observed repository evidence consumed by the existing Prolog-RLM SPEC/VERIFY path.

RAGE transaction

  • RED-first f348728: worktree lock assertion/evidence contract.
  • implementation commits project bounded worktree inventory, thread it through the pure verifier bridge, and add trusted worktree_locked assertion semantics.
  • follow-up fixes remove misleading ownership language: Git lock reasons are coordination metadata, not authentication.

Contract

  • worktree_locked requires an exact worktree path + full Git object ID and verifies only when the currently observed worktree is locked at that exact HEAD.
  • verifier collection is read-only and bounded to 100 registered worktrees.
  • lock reasons are deliberately excluded from SPEC evidence; the verifier sees only {path, head, locked}.
  • missing/path-moved/head-changed/unlocked worktrees produce failed verification rather than invented success.
  • observations continue through canonical rlm_verify:spec_verify/4; no assertz, shell, repair action, alternate runtime, or plugin-private authorization.

Security boundary

A successful worktree_locked assertion proves coordination lock state only. It does not prove worker identity or principal ownership. Canonical Zara approval remains the mutation authority; strong cross-plugin task ownership/composition remains blocked on Zara Core #400.

Exact-head CI must pass whitespace, current Zara compatibility contract, full registry/plugin nix flake check, and package builds before merge.

Advances #1 by making linked-worktree lock state part of current observed repository evidence consumed by the existing Prolog-RLM SPEC/VERIFY path. ## RAGE transaction - RED-first `f348728`: worktree lock assertion/evidence contract. - implementation commits project bounded worktree inventory, thread it through the pure verifier bridge, and add trusted `worktree_locked` assertion semantics. - follow-up fixes remove misleading ownership language: Git lock reasons are coordination metadata, not authentication. ## Contract - `worktree_locked` requires an exact worktree path + full Git object ID and verifies only when the currently observed worktree is locked at that exact HEAD. - verifier collection is read-only and bounded to 100 registered worktrees. - lock **reasons are deliberately excluded** from SPEC evidence; the verifier sees only `{path, head, locked}`. - missing/path-moved/head-changed/unlocked worktrees produce failed verification rather than invented success. - observations continue through canonical `rlm_verify:spec_verify/4`; no `assertz`, shell, repair action, alternate runtime, or plugin-private authorization. ## Security boundary A successful `worktree_locked` assertion proves coordination lock state only. It does not prove worker identity or principal ownership. Canonical Zara approval remains the mutation authority; strong cross-plugin task ownership/composition remains blocked on Zara Core #400. Exact-head CI must pass whitespace, current Zara compatibility contract, full registry/plugin `nix flake check`, and package builds before merge.
Some checks failed
CI / test (pull_request) Failing after 18s
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-verify:rage/1-zara-coding-worktree-verify
git switch rage/1-zara-coding-worktree-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-worktree-verify
git switch rage/1-zara-coding-worktree-verify
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-worktree-verify
git switch rage/1-zara-coding-worktree-verify
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-worktree-verify
git switch main
git merge --squash rage/1-zara-coding-worktree-verify
git switch main
git merge --ff-only rage/1-zara-coding-worktree-verify
git switch main
git merge rage/1-zara-coding-worktree-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!453
No description provided.