feat(agent-actions): auto-close a contributor's PR over the open-PR cap (#2270)

[JSONbored]

Summary

• Stacked on feat(settings): add contributorOpenPrCap/contributorOpenIssueCap config (#2270) #2467 (base branch is that PR's branch, not main — this PR's diff is only the enforcement delta; it will retarget to main once feat(settings): add contributorOpenPrCap/contributorOpenIssueCap config (#2270) #2467 merges).
• Adds the actual enforcement for feat(agent-actions): configurable per-contributor open PR/issue cap with auto-close over the limit #2270: a new closeKind: "contributor_cap" short-circuit in planAgentMaintenanceActions, mirroring the existing contributor-blacklist block exactly (fires ahead of merit/CI/AI analysis, exempt from the close-precision breaker via the same !== "heuristic" check, owner/admin/automation-bot never touched).
• The webhook-time check counts the author's other open PRs on the repo (otherOpenPullRequests, already-fetched live-DB-backed data — no new query added) plus the incoming PR, ranked by PR number (GitHub's own creation order, not webhook-arrival order) so a burst of near-simultaneous opens still ranks deterministically. Only the PR(s) pushing the count over the cap close; older ones stay open.
• Adds the paired contributorCapLabel setting (default "over-contributor-limit") through the full config-as-code chain (migration 0090, schema, DB round-trip, .gittensory.yml parsing + precedence, OpenAPI, docs) since the label needed to be configurable per feat(agent-actions): configurable per-contributor open PR/issue cap with auto-close over the limit #2270's own text, and it's tightly coupled to this enforcement action rather than the PR1 contract.

Known scope limit (documented, not a gap I missed): this is live webhook-time enforcement only. If a maintainer lowers the cap after a contributor already has more PRs open than the new cap allows, nothing retroactively re-evaluates those pre-existing PRs in this PR — that's a periodic-sweep backstop, tracked as follow-up work on #2270. It isn't required for the core ask (stopping a new PR that pushes someone over the limit).

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked an issue (feat(agent-actions): configurable per-contributor open PR/issue cap with auto-close over the limit #2270).

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally — 100% line coverage and full branch coverage on every changed line (verified via the v8/lcov report against the exact diff, including the "contributor exactly at cap, not over" branch).
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries — planner-level short-circuit tests in test/unit/agent-actions.test.ts (label/close/comment shape, owner/admin/bot exemption, autonomy gating, interaction with a simultaneous blacklist match), full webhook-pipeline integration tests in test/unit/queue.test.ts (over-cap close, at-cap no-close, disabled-by-default no-op), DB round-trip + manifest-parsing tests for contributorCapLabel.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics — the close comment interpolates only the author's own public login and their own public open-PR count, run through sanitizePublicComment.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — N/A, no auth/session/CORS surface touched.
• API/OpenAPI/MCP behavior is updated and tested where needed — RepositorySettings OpenAPI schema regenerated (npm run ui:openapi).
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. — N/A, no UI change.
• Visible UI changes include a UI Evidence section. — N/A, no visible UI change.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs — .gittensory.yml.example updated; CHANGELOG.md untouched.

Notes

• Next in the feat(agent-actions): configurable per-contributor open PR/issue cap with auto-close over the limit #2270 sequence: issue-side enforcement (the first eventName === "issues" actuation branch — issues currently have zero auto-close path), then the global env-var default + the named-contributor whitelist noted in the comment on feat(agent-actions): configurable per-contributor open PR/issue cap with auto-close over the limit #2270.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	6b5f728	Commit Preview URL Branch Preview URL	Jul 02 2026, 07:57 AM

[gittensory-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-02 08:06:33 UTC}

19 files · 1 AI reviewer · no blockers · readiness 73/100 · CI pending · unknown

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review

Review summary
The diff wires contributor open-item cap enforcement through the planner, PR processor, issue webhook path, settings schema, migration, OpenAPI, docs, and focused regression tests. The core enforcement is deterministic and correctly short-circuits before merit/CI/AI paths, with owner/admin/bot exemptions preserved in the planner and issue path. I do not see a reachable breaking defect in the provided diff; the main remaining concerns are maintainability and small defensive gaps around label validation/default drift.

Nits — 7 non-blocking

• nit: src/github/backfill.ts:2591 says fetchLiveIssueState's caller fails open to stored state, but maybeCloseIssueOverContributorCap excludes undefined live checks from the count, so the comment should match the actual fail-safe behavior.
• nit: src/queue/processors.ts:1889 still computes and enqueues over-cap sibling wakes for owner/admin/automation authors even though the planner later exempts them, which can create avoidable regate jobs for exempt authors.
• nit: src/signals/focus-manifest.ts:817 accepts any string for settings.contributorCapLabel; an empty string or whitespace-only label will make the label action fail at GitHub even though the close can still proceed.
• nit: src/db/repositories.ts:503 and src/db/repositories.ts:629 duplicate the contributor-cap default string instead of reusing DEFAULT_CONTRIBUTOR_CAP_LABEL, increasing drift risk with src/settings/agent-actions.ts.
• Update src/github/backfill.ts:2591 to document that fetchLiveIssueState returns undefined on errors and that this cap caller treats undefined as not counted.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	⚠️ 2 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (size label size:L; no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 65 registered-repo PR(s), 55 merged, 548 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 65 PR(s), 548 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 65 PR(s), 548 issue(s).
• Related work: Titles/paths share 9 meaningful terms. (issue #2270)
• Related work: Titles/paths share 8 meaningful terms. (issue #2462, issue #2270)

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Review top overlaps.
• Add a concise scope and risk note.
• No action.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[codecov]

Codecov Report

❌ Patch coverage is 99.07407% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.95%. Comparing base (cdef1c5) to head (c48ee80).
⚠️ Report is 32 commits behind head on main.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/queue/processors.ts	98.24%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #2479    +/-   ##
========================================
  Coverage   95.95%   95.95%            
========================================
  Files         226      228     +2     
  Lines       25387    25677   +290     
  Branches     9234     9335   +101     
========================================
+ Hits        24359    24639   +280     
- Misses        417      426     +9     
- Partials      611      612     +1     

Files with missing lines	Coverage Δ
src/db/repositories.ts	96.52% <100.00%> (+<0.01%)	⬆️
src/db/schema.ts	69.46% <ø> (ø)
src/github/backfill.ts	96.49% <100.00%> (+<0.01%)	⬆️
src/github/pr-actions.ts	100.00% <100.00%> (ø)
src/openapi/schemas.ts	100.00% <ø> (ø)
src/services/agent-action-executor.ts	94.77% <100.00%> (+1.97%)	⬆️
src/settings/agent-actions.ts	93.60% <100.00%> (+0.80%)	⬆️
src/signals/focus-manifest.ts	99.25% <100.00%> (+0.01%)	⬆️
src/queue/processors.ts	91.96% <98.24%> (+0.21%)	⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.