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

zara-coding: add bounded structured git log evidence #471

Open
nsaspy wants to merge 10 commits from rage/1-git-log-adapter into main
pull from: rage/1-git-log-adapter
merge into: nsaspy:main
Conversation 0 Commits 10 Files changed 5 +198 -13
nsaspy commented 2026-09-08 02:20:05 +00:00
Owner
Copy link

Advances #1 with two bounded read-only Git evidence slices.

Slices

  • RED-first contract for structured commit history
  • coding.git.log: fixed-format argv-only history capped to 1..100 commits
  • RED-first contract for structured local branch inventory
  • coding.git.branches: fixed-format local refs capped to 1..100 branches
  • both tools stay behind the existing allowed-root repository boundary
  • shared bounded-limit validation rejects invalid requests before spawning Git
  • docs cover the read-only evidence surfaces and security boundaries

No Git mutation, arbitrary shell/eval, caller-controlled Git options/formats, alternate assistant runtime, or approval bypass is introduced.

Gate

Merge only after exact-head CI passes compatibility gate contract tests, full registry/plugin tests, package builds, and Nix checks.

Advances #1 with two bounded read-only Git evidence slices. ## Slices - RED-first contract for structured commit history - `coding.git.log`: fixed-format argv-only history capped to 1..100 commits - RED-first contract for structured local branch inventory - `coding.git.branches`: fixed-format local refs capped to 1..100 branches - both tools stay behind the existing allowed-root repository boundary - shared bounded-limit validation rejects invalid requests before spawning Git - docs cover the read-only evidence surfaces and security boundaries No Git mutation, arbitrary shell/eval, caller-controlled Git options/formats, alternate assistant runtime, or approval bypass is introduced. ## Gate Merge only after exact-head CI passes compatibility gate contract tests, full registry/plugin tests, package builds, and Nix checks.
docs(zara-coding): document bounded branch evidence
Some checks failed
CI / test (pull_request) Failing after 21s
Details
60751a37cf
Some checks failed
CI / test (pull_request) Failing after 21s
Details
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/domain.py
  • plugins/zara-coding/lib/zara_coding/plugin.py
  • plugins/zara-coding/test/test_domain.py
  • plugins/zara-coding/test/test_plugin.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-git-log-adapter:rage/1-git-log-adapter
git switch rage/1-git-log-adapter

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-git-log-adapter
git switch rage/1-git-log-adapter
git rebase main
git switch main
git merge --ff-only rage/1-git-log-adapter
git switch rage/1-git-log-adapter
git rebase main
git switch main
git merge --no-ff rage/1-git-log-adapter
git switch main
git merge --squash rage/1-git-log-adapter
git switch main
git merge --ff-only rage/1-git-log-adapter
git switch main
git merge rage/1-git-log-adapter
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!471
No description provided.