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

zara-coding: verify exact repository branch in trusted SPECs #456

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

Advances #1 by extending the existing repository verification evidence, not by adding another collector or command path.

Adds trusted repository_branch/1:

  • uses the exact branch label already returned by bounded RepositoryInspector.inspect() (DETACHED remains explicit);
  • projects branch into current observed repository evidence alongside HEAD and clean state;
  • carries branch over the existing stdin-only verifier payload;
  • binds it to the frozen requirement identity and evaluates exact root + branch equality with a pure Prolog evaluator;
  • keeps observer:none, fixed repository source/trust/freshness policy, and root+HEAD state identity;
  • does not execute Git from Prolog or widen plugin authority.

TDD RED 0ab38d25; evidence dd4a3415; verifier payload 56df7678; Prolog binding/evaluator 3a8afd59 / 55c0b7d7; regression fixtures 824b568e / 5a9288bd; docs 78e2e941.

No Core, Android, dotfiles, other-repo, or external todo changes. Full exact-head compatibility, registry/plugin, and Nix package gates required before merge.

Advances #1 by extending the existing repository verification evidence, not by adding another collector or command path. Adds trusted `repository_branch/1`: - uses the exact branch label already returned by bounded `RepositoryInspector.inspect()` (`DETACHED` remains explicit); - projects branch into current observed repository evidence alongside HEAD and clean state; - carries branch over the existing stdin-only verifier payload; - binds it to the frozen requirement identity and evaluates exact root + branch equality with a pure Prolog evaluator; - keeps `observer:none`, fixed repository source/trust/freshness policy, and root+HEAD state identity; - does not execute Git from Prolog or widen plugin authority. TDD RED `0ab38d25`; evidence `dd4a3415`; verifier payload `56df7678`; Prolog binding/evaluator `3a8afd59` / `55c0b7d7`; regression fixtures `824b568e` / `5a9288bd`; docs `78e2e941`. No Core, Android, dotfiles, other-repo, or external todo changes. Full exact-head compatibility, registry/plugin, and Nix package gates required 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-branch-assertion:rage/1-zara-coding-branch-assertion
git switch rage/1-zara-coding-branch-assertion

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