feat(agent): monitor open PRs and wire into decision packs - #72
Merged
JSONbored merged 11 commits intoJun 1, 2026
Merged
Conversation
JSONbored
requested changes
May 29, 2026
Owner
There was a problem hiding this comment.
@monsterdavidliu-ux the feature direction is useful, but it still needs integration and conflict cleanup.
Required:
- Resolve the real merge conflict in
src/scoring/preview.ts. - Wire open-PR monitor output into decision packs and agent planning, not only a standalone route/tool.
- Add session-actor access protection for contributor-specific monitor data, matching the private advisory access pattern.
- Preserve the pending-merge scenario behavior and rerun full validation.
Add contributor open-PR monitor across registered repos with public-safe
classifications, cleanup-first guidance, and pending-merge projections.
- REST GET /v1/contributors/{login}/open-pr-monitor and MCP gittensory_monitor_open_prs
- Session-actor access protection matching private decision-pack routes
- Embed openPrMonitor in contributor decision packs and agent planning actions
- Resolve preview.ts merge with main pending-pr scenario fields
Fixes JSONbored#36
monsterdavidliu-ux
force-pushed
the
feat/36-contributor-open-pr-monitor
branch
from
May 31, 2026 13:26
a3fc2d8 to
d6a3f63
Compare
Cover agent orchestrator monitor actions, decision-pack guidance merge, REST session access, MCP contributor guard, and rate-limit route class.
node:sqlite prepared statements lack columns(); derive column order from row keys instead. Add a regression test for empty raw() results.
Cover agent context snapshot freshness warnings and regenerate the UI OpenAPI spec after open-pr-monitor schema changes.
monsterdavidliu-ux
force-pushed
the
feat/36-contributor-open-pr-monitor
branch
from
June 1, 2026 14:36
a792517 to
71dbed7
Compare
JSONbored
self-requested a review
June 1, 2026 17:51
JSONbored
approved these changes
Jun 1, 2026
JSONbored
left a comment
Owner
There was a problem hiding this comment.
@monsterdavidliu-ux This is ready from my side on the current refresh. The open-PR monitor is wired into scoring scenarios, decision packs, agent orchestration, API, MCP, OpenAPI, and tests, and the active-vs-historical PR distinction is explicit enough for the reviewability/scoring model. Current checks are green and the merge tree is clean.
This was referenced Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
buildContributorOpenPrMonitorto classify a contributor's open PRs on registered repos (approved, failing checks, needs author, duplicate-prone, missing tests, maintainer lane, stale/withdraw, etc.) and return public-safe next-step packets from cached metadata only.GET /v1/contributors/{login}/open-pr-monitorand MCP toolgittensory_monitor_open_prs, with session-actor access protection matching private decision-pack routes.openPrMonitorin contributor decision packs and agent planning (summary, next actions, orchestrator context) so the feature is not only a standalone route/tool.preview.tsmerge with main: keeppendingScenarioObserved/afterApprovedPrsMerge/afterStalePrsClosepending-merge scenario behavior.Review feedback addressed
src/scoring/preview.tsresolved againstmain.requireContributorAccesson REST and MCP contributor monitor paths.main.Test plan
PATH=/usr/bin:/bin:$PATH npm run test:ci(≥95% global branch coverage)openPrMonitorand agent planning consumes itFixes #36