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

zara-coding: add one-shot repository SPEC check #457

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-check-repository into main
pull from: rage/1-zara-coding-check-repository
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 direct end-to-end acceptance path built only from the canonical pieces now on main.

Adds read-only coding.spec.check-repository(path, source):

  • validates/freezes declarative SPEC source through the fixed trusted zara-coding registry;
  • does not inspect the repository if compilation is rejected;
  • on successful freeze, captures a fresh allowed-root repository snapshot and delegates to coding.spec.verify-repository / Prolog-RLM spec_verify/4;
  • returns compile and verification outcomes as separate structured evidence, without inventing a synthetic success claim;
  • grants no plan/execution/repair authority and requires no mutation approval.

TDD RED 4da79c1e; implementation 593a8cf4; surface/failure-path agreement e37e80e7; docs b0ef7b40.

This is intentionally the direct no-effects path. Planning/execution and GitHub/context/memory/shell composition remain behind Zara Core #400 rather than being duplicated here. No Core, Android, dotfiles, other-repo, or external todo changes.

Advances #1 with a direct end-to-end acceptance path built only from the canonical pieces now on `main`. Adds read-only `coding.spec.check-repository(path, source)`: - validates/freezes declarative SPEC source through the fixed trusted zara-coding registry; - does not inspect the repository if compilation is rejected; - on successful freeze, captures a fresh allowed-root repository snapshot and delegates to `coding.spec.verify-repository` / Prolog-RLM `spec_verify/4`; - returns compile and verification outcomes as separate structured evidence, without inventing a synthetic success claim; - grants no plan/execution/repair authority and requires no mutation approval. TDD RED `4da79c1e`; implementation `593a8cf4`; surface/failure-path agreement `e37e80e7`; docs `b0ef7b40`. This is intentionally the direct no-effects path. Planning/execution and GitHub/context/memory/shell composition remain behind Zara Core #400 rather than being duplicated here. No Core, Android, dotfiles, other-repo, or external todo changes.
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-check-repository:rage/1-zara-coding-check-repository
git switch rage/1-zara-coding-check-repository

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