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

zara-coding: expose pure repository SPEC verification #458

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

Advances #1 immediately after #105 by exposing the already-merged pure repository verification path as a read-only Zara tool.

This slice:

  • adds coding.spec.verify-repository(path, frozen_spec);
  • resolves and inspects the repository only through the existing bounded RepositoryInspector and configured allowed roots;
  • turns that exact current snapshot into source_class=repository, trust_class=observed, freshness=current evidence;
  • delegates reconciliation to the canonical Prolog-RLM spec_verify/4 bridge merged in #105;
  • does not add approval because verification is read-only and grants no effect authority;
  • fails closed when repository inspection or Prolog-RLM is unavailable.

TDD: RED 666e0b78; implementation 3646c54d; focused test corrections/surface agreement dd21af66, 1aacd042.

No planning/execution runtime, arbitrary shell, provider registration, Core changes, Android changes, dotfiles changes, or external todo work. Full compatibility/registry/plugin/Nix gate required before merge.

Advances #1 immediately after #105 by exposing the already-merged pure repository verification path as a read-only Zara tool. This slice: - adds `coding.spec.verify-repository(path, frozen_spec)`; - resolves and inspects the repository only through the existing bounded `RepositoryInspector` and configured allowed roots; - turns that exact current snapshot into `source_class=repository`, `trust_class=observed`, `freshness=current` evidence; - delegates reconciliation to the canonical Prolog-RLM `spec_verify/4` bridge merged in #105; - does not add approval because verification is read-only and grants no effect authority; - fails closed when repository inspection or Prolog-RLM is unavailable. TDD: RED `666e0b78`; implementation `3646c54d`; focused test corrections/surface agreement `dd21af66`, `1aacd042`. No planning/execution runtime, arbitrary shell, provider registration, Core changes, Android changes, dotfiles changes, or external todo work. Full compatibility/registry/plugin/Nix gate 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-verify-tool:rage/1-zara-coding-verify-tool
git switch rage/1-zara-coding-verify-tool

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