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

zara-coding: add bounded repo list and status surfaces #468

Open
nsaspy wants to merge 5 commits from rage/1-repo-list-status into main
pull from: rage/1-repo-list-status
merge into: nsaspy:main
Conversation 0 Commits 5 Files changed 5 +108 -7
nsaspy commented 2026-09-08 02:20:04 +00:00
Owner
Copy link

Advances #1 and closes two direct initial-surface gaps: repo.list and repo.status.

Slices

  • RED-first bounded local repository discovery
  • coding.repo.list scans only configured roots/immediate children, skips symlink children, caps returned repositories to 1..100, and fails if discovery exceeds 1,000 child entries
  • coding.repo.status is an explicit direct-surface alias over the existing allowed-root structured inspect evidence
  • no recursive filesystem crawl, shell command, Git mutation, or widened repository boundary

The implementation keeps coding.repo.inspect as the detailed evidence path while making the issue's direct status/list operations available without duplicating state or inventing a second repository model.

Gate

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

Advances #1 and closes two direct initial-surface gaps: `repo.list` and `repo.status`. ## Slices - RED-first bounded local repository discovery - `coding.repo.list` scans only configured roots/immediate children, skips symlink children, caps returned repositories to 1..100, and fails if discovery exceeds 1,000 child entries - `coding.repo.status` is an explicit direct-surface alias over the existing allowed-root structured inspect evidence - no recursive filesystem crawl, shell command, Git mutation, or widened repository boundary The implementation keeps `coding.repo.inspect` as the detailed evidence path while making the issue's direct status/list operations available without duplicating state or inventing a second repository model. ## Gate Merge only after exact-head CI passes compatibility contract tests, full registry/plugin tests, package builds, and Nix checks.
docs(zara-coding): document bounded repo discovery and status
Some checks failed
CI / test (pull_request) Failing after 22s
Details
0d8fbbb009
Some checks failed
CI / test (pull_request) Failing after 22s
Details
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/domain.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-repo-list-status:rage/1-repo-list-status
git switch rage/1-repo-list-status

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-repo-list-status
git switch rage/1-repo-list-status
git rebase main
git switch main
git merge --ff-only rage/1-repo-list-status
git switch rage/1-repo-list-status
git rebase main
git switch main
git merge --no-ff rage/1-repo-list-status
git switch main
git merge --squash rage/1-repo-list-status
git switch main
git merge --ff-only rage/1-repo-list-status
git switch main
git merge rage/1-repo-list-status
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!468
No description provided.