zara-coding: add approval-gated detached worktree creation #462

Open
nsaspy wants to merge 7 commits from rage/1-zara-coding-worktree-add into main
Owner

Advances #1 with the next dependency-ready local Git slice without crossing Core composition boundaries.

Adds coding.git.worktree.add-detached:

  • canonical Zara approval metadata required;
  • target must be non-existing, inside configured repository roots, with an existing parent;
  • caller supplies a full SHA-1/SHA-256 object ID;
  • object must resolve directly to a commit (annotated tag/object indirection is refused);
  • fixed argv git worktree add --detach, bounded by the existing Git runner; no shell/eval;
  • no branch/ref creation or movement;
  • structured path/head/detached evidence returned.

RED-first test commit: 465a1b1d. Follow-up tests bind the operation to the existing repository boundary and approval contract. Registry metadata is unchanged because this advances the already-published zara-coding 0.1.0 surface.

Full registry/plugin/Nix CI required before merge. External todo work remains untouched.

Advances #1 with the next dependency-ready local Git slice without crossing Core composition boundaries. Adds `coding.git.worktree.add-detached`: - canonical Zara approval metadata required; - target must be non-existing, inside configured repository roots, with an existing parent; - caller supplies a full SHA-1/SHA-256 object ID; - object must resolve directly to a commit (annotated tag/object indirection is refused); - fixed argv `git worktree add --detach`, bounded by the existing Git runner; no shell/eval; - no branch/ref creation or movement; - structured path/head/detached evidence returned. RED-first test commit: `465a1b1d`. Follow-up tests bind the operation to the existing repository boundary and approval contract. Registry metadata is unchanged because this advances the already-published `zara-coding` 0.1.0 surface. Full registry/plugin/Nix CI required before merge. External todo work remains untouched.
Some checks failed
CI / test (pull_request) Failing after 18s
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/plugin.py
  • plugins/zara-coding/lib/zara_coding/worktree.py
  • plugins/zara-coding/test/test_plugin.py
  • plugins/zara-coding/test/test_worktree_add.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

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

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-add
git switch rage/1-zara-coding-worktree-add
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-worktree-add
git switch rage/1-zara-coding-worktree-add
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-worktree-add
git switch main
git merge --squash rage/1-zara-coding-worktree-add
git switch main
git merge --ff-only rage/1-zara-coding-worktree-add
git switch main
git merge rage/1-zara-coding-worktree-add
git push origin main
Sign in to join this conversation.
No description provided.