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

zara-coding: add detached worktree coordination locks #455

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

Advances #1 with a bounded local coordination primitive for linked coding worktrees.

RAGE transaction

  • RED-first commit fd5a21d: deterministic contract for lock/unlock coordination semantics.
  • implementation commits d892d5c + bc89b57.

Contract

  • exposes approval-gated coding.git.worktree.lock / coding.git.worktree.unlock
  • only operates on registered detached non-primary worktrees inside configured roots
  • requires a full caller-observed HEAD and refuses stale HEAD
  • lock reasons are explicit, bounded to 256 chars, and reject control characters
  • refuses already-locked/prunable worktrees
  • unlock requires the exact currently reported lock reason, catching accidental/stale release attempts
  • fixed argv only; no shell, branch movement, ref creation/deletion, worktree removal, or forced Git operation

Adversarial note

Git worktree lock reasons are observable coordination metadata, not authentication credentials. Matching a reason does not establish principal ownership. Zara's canonical approval remains the authority for both lock and unlock. Strong worker/principal ownership still belongs in the later composed task-state layer; this slice does not claim to solve that boundary by itself.

This is intentionally a local coordination building block while cross-plugin worker/orchestration composition remains blocked on Zara Core #400.

Gate

Exact-head CI remains authoritative: compatibility contract, registry/plugin suite, nix flake check, and package build must be green before merge.

Advances #1 with a bounded local coordination primitive for linked coding worktrees. ## RAGE transaction - RED-first commit `fd5a21d`: deterministic contract for lock/unlock coordination semantics. - implementation commits `d892d5c` + `bc89b57`. ## Contract - exposes approval-gated `coding.git.worktree.lock` / `coding.git.worktree.unlock` - only operates on registered detached non-primary worktrees inside configured roots - requires a full caller-observed HEAD and refuses stale HEAD - lock reasons are explicit, bounded to 256 chars, and reject control characters - refuses already-locked/prunable worktrees - unlock requires the exact currently reported lock reason, catching accidental/stale release attempts - fixed argv only; no shell, branch movement, ref creation/deletion, worktree removal, or forced Git operation ## Adversarial note Git worktree lock reasons are observable coordination metadata, not authentication credentials. Matching a reason does **not** establish principal ownership. Zara's canonical approval remains the authority for both lock and unlock. Strong worker/principal ownership still belongs in the later composed task-state layer; this slice does not claim to solve that boundary by itself. This is intentionally a local coordination building block while cross-plugin worker/orchestration composition remains blocked on Zara Core #400. ## Gate Exact-head CI remains authoritative: compatibility contract, registry/plugin suite, `nix flake check`, and package build must be green before merge.
Some checks failed
CI / test (pull_request) Failing after 17s
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-remove:rage/1-zara-coding-worktree-remove
git switch rage/1-zara-coding-worktree-remove

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