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

fix(zara-coding): bind task evidence to verifier provenance #223

Open
nsaspy wants to merge 12 commits from fix/zara-coding-evidence-provenance into main
pull from: fix/zara-coding-evidence-provenance
merge into: nsaspy:main
Conversation 0 Commits 12 Files changed 8 +300 -91
nsaspy commented 2026-09-08 02:18:49 +00:00
Owner
Copy link

Summary

Closes a false-success path at the Prolog task-state boundary.

  • add explicit evidence provenance (caller vs verifier) to the bounded JSON-line protocol
  • reject caller-authored passed evidence inside Prolog, not only at the public Python tool wrapper
  • require verifier-owned passing evidence for task completion
  • preserve public coding.task.record-evidence as caller-authored failed observations only
  • keep the internal TaskStateSession verifier path explicit and bounded
  • add direct SWI-Prolog regression coverage for forged/model provenance and caller-authored pass attempts
  • update protocol/unit tests to lock provenance semantics

This does not add Core composition or import Core internals. Future cross-plugin execution remains blocked on Zara Core #400.

Related: #1
Worker mailbox: #507

Required exact-head gates: zara-coding unittest suite, registry validation, nix flake check.

## Summary Closes a false-success path at the Prolog task-state boundary. - add explicit evidence provenance (`caller` vs `verifier`) to the bounded JSON-line protocol - reject caller-authored `passed` evidence inside Prolog, not only at the public Python tool wrapper - require verifier-owned passing evidence for task completion - preserve public `coding.task.record-evidence` as caller-authored failed observations only - keep the internal `TaskStateSession` verifier path explicit and bounded - add direct SWI-Prolog regression coverage for forged/model provenance and caller-authored pass attempts - update protocol/unit tests to lock provenance semantics This does not add Core composition or import Core internals. Future cross-plugin execution remains blocked on Zara Core #400. Related: #1 Worker mailbox: #507 Required exact-head gates: zara-coding unittest suite, registry validation, `nix flake check`.
docs(zara-coding): define completion criteria as verifier keys
Some checks failed
CI / test (pull_request) Failing after 31s
Details
CI / zara-avatar idle CPU budget (pull_request) Failing after 13m3s
Details
8a068a68f9
Some checks failed
CI / test (pull_request) Failing after 31s
Details
CI / zara-avatar idle CPU budget (pull_request) Failing after 13m3s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/zara-coding-evidence-provenance:fix/zara-coding-evidence-provenance
git switch fix/zara-coding-evidence-provenance

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 fix/zara-coding-evidence-provenance
git switch fix/zara-coding-evidence-provenance
git rebase main
git switch main
git merge --ff-only fix/zara-coding-evidence-provenance
git switch fix/zara-coding-evidence-provenance
git rebase main
git switch main
git merge --no-ff fix/zara-coding-evidence-provenance
git switch main
git merge --squash fix/zara-coding-evidence-provenance
git switch main
git merge --ff-only fix/zara-coding-evidence-provenance
git switch main
git merge fix/zara-coding-evidence-provenance
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!223
No description provided.