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

zara-coding: bound direct repository snapshot paths #447

Open
nsaspy wants to merge 4 commits from rage/1-zara-coding-inspect-bound into main
pull from: rage/1-zara-coding-inspect-bound
merge into: nsaspy:main
Conversation 0 Commits 4 Files changed 2 +97
nsaspy commented 2026-09-08 02:19:58 +00:00
Owner
Copy link

Advances #1 by making the direct coding.repo.status / coding.repo.inspect snapshot surface obey the same bounded-evidence discipline as SPEC verification.

RAGE transaction

  • RED-first 55ebd43: prove inspection fails closed above 100 unique changed paths and deduplicates tracked/untracked overlap before enforcing the bound.
  • implementation feb5563: cap the canonical repository snapshot at 100 unique changed paths and raise an explicit incompatibility/error instead of returning an unbounded result.

This closes a plugin-owned bounded-interface gap without truncating evidence or pretending a partial snapshot is complete. No new authority, shell mode, or execution path.

Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and package builds before merge.

Advances #1 by making the direct `coding.repo.status` / `coding.repo.inspect` snapshot surface obey the same bounded-evidence discipline as SPEC verification. ## RAGE transaction - RED-first `55ebd43`: prove inspection fails closed above 100 unique changed paths and deduplicates tracked/untracked overlap before enforcing the bound. - implementation `feb5563`: cap the canonical repository snapshot at 100 unique changed paths and raise an explicit incompatibility/error instead of returning an unbounded result. This closes a plugin-owned bounded-interface gap without truncating evidence or pretending a partial snapshot is complete. No new authority, shell mode, or execution path. Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and package builds before merge.
fix(zara-coding): reject mixed-state repository inspection
Some checks failed
CI / test (pull_request) Failing after 17s
Details
190017ecf4
Some checks failed
CI / test (pull_request) Failing after 17s
Details
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/lib/zara_coding/domain.py
  • plugins/zara-coding/test/test_inspect_bound.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-inspect-bound:rage/1-zara-coding-inspect-bound
git switch rage/1-zara-coding-inspect-bound

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