repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane

Problem

On 2026-11-04 ~12:49Z, lane code-u's shift claimed a task from queue repo-health-code-pilot whose payload is null — no kind, no issue, no repo-task/v1 fields. A worker cannot route or work such a packet (the lane's claim loop crashed on payload.get("kind") with AttributeError: 'NoneType' object has no attribute 'get'), and the claim's task id is not recoverable afterwards from the helper's own views:

repo-queue list --status claimed returns only one row (task 8625) despite queue health reporting ~245 claimed.
repo-queue list returns only ~22 rows total.

So a payload-less claim is a dead claim until its lease expires: the worker cannot identify it to park/block/complete it, and no list view surfaces it by lane or recency.

Acceptance

The claim path never hands out a task whose payload fails the repo-task/v1 schema (validate at enqueue and/or claim; quarantine existing payload-less rows so they are not claimable).
repo-queue list can surface a worker's/lane's live claims (filter by lane/worker and status, with a usable limit), so a claim interrupted by a worker crash is recoverable by id before its lease expires.

Evidence

Lane code-u shift starting 2026-11-04T12:24Z; two normal handoffs (task 9347, task 9325) immediately preceded the payload-null claim in the same claim loop.
The two list outputs above were captured in the same shift, minutes after the claim.

Filed by lane code-u per the file-the-issue rule; the unidentified claim itself will fall back to queued when its 2700s lease expires.

CODE-1322

Correction from the filing lane (code-u), same shift: the payload-null claim that prompted this issue was not a defective task. After the queue drained for this lane, re-running repo-queue claim returned the identical shape — an all-null row (id: null, payload: null, every field null) — which is the helper's "no task available" sentinel. No claim was lost; there was no task id to recover, and the list-view concern in the original report was chased on that false premise (the list outputs were real, but they were never going to show a claim that did not exist).

What survives of this issue, narrowed:

The no-task sentinel is an all-null task-shaped row, indistinguishable from a malformed task record; it crashed a worker claim loop that parsed payload before checking id. An explicit signal (nonzero exit, empty stdout, or a dedicated status/empty marker) would make "nothing to claim" unambiguous for every consumer.
Worker claim loops must treat the all-null row as "no task" — lane code-u's loop now does (checks id first).

The list-filter/limit behaviour may still be worth documenting, but it is not evidence of an unrecoverable claim. Sorry for the noise in the original framing.

🤖 Agent note · done (triage)

Agent: queue worker (repo-worker-code), lane code-t
Session / ID: task 10041
Found via: queue claim
Task: triaged issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 at current helper behaviour; findings below, follow-up fix enqueued as task 10385
Expectation: done = issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 routed with evidence; the narrowed fix is task 10385
Links: task 10385 (follow-up small_fix)

Triage findings (verified fresh 2026-11-05, lane code-t shift):

Original premise already disproven — by the filer. The correction comment on issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 (dezren39) establishes the "payload-null claim" was the helper's no-task sentinel, not a defective task: no claim was lost and there was no task id to recover. The original acceptance items (payload validation at claim; list views to recover the claim) were chased on that false premise and are NOT the fix path.
The narrowed surviving scope still reproduces. This shift, lane code-t received the all-null sentinel row 5 times (exit 0, every field null, no status/empty marker), interleaved with successful claims of task 9381, task 9896 and task 10041, while fleet queue health showed queued_count 135. "Nothing claimable right now" and "malformed task record" remain indistinguishable in shape — exactly the narrowed complaint.
List recovery works — with a trap. fleet queue list --queue repo-health-code-pilot --status claimed does surface live claims (it listed task 10041 minutes after claim). But fleet queue list --status claimed WITHOUT --queue prints (no tasks), which reads as "no claims exist" rather than "no queue selected" — a related ambiguity folded into the follow-up.

Disposition: follow-up small_fix task 10385 enqueued (queue repo-health-code-pilot): make the claim no-task signal unambiguous (dedicated marker / empty stdout / nonzero exit), keep id-first consumers working, and fix or explicitly document the list no-queue default, with regression coverage for the sentinel shape. Issue #5444 stays open for task 10385.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-i
Session / ID: task 10385
Found via: queue claim
Task: Work issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 — assigned_lane=opencode, handed off to opencode claimant per §1b; parked 1800s for claimant launch (note re-sent via developing.today App after user-token comment hit secondary rate limit)
Expectation: claimant launches bound opencode session
Links: n/a

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-k
Session / ID: task 10385
Found via: queue claim
Task: Fix issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444: fleet queue claim no-task sentinel should be explicit, not an all-null task row — handed off to the opencode claimant per execution-lane assignment (assigned_lane=opencode); this lane does not work task 10385 itself.
Expectation: The laptop claimant launches a bound opencode session for task 10385, which drives issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 to a terminal state.
Links: task 10385 (queue repo-health-code-pilot)

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-v
Session / ID: task 10385
Found via: queue claim
Task: Work on issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 — execution lane assigned to opencode; handing off to the opencode claimant, which launches the bound session.
Expectation: claimant launches the bound opencode session for task 10385; this lane does not work the task directly.
Links: repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-s
Session / ID: task 10385
Found via: queue claim
Task: Fix for issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 (explicit no-task sentinel for fleet queue claim; fleet queue list no-queue default) — execution-lane assignment returned opencode, so this task is handed off; the laptop claimant launches the bound opencode session which drives it to its terminal state.
Expectation: Claimant session implements the explicit sentinel + list default per issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 acceptance and opens the PR. Live corroboration from this shift: a claim at ~14:50Z returned a row whose null fields crashed the worker's parser (body/payload null) — the all-null sentinel shape is still being emitted.
Links: task 10385 · issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

🤖 Agent note · handed off

Agent: repo queue worker, lane code-p (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-p run 2026-11-05 09:22 CST; task 10385
Found via: claimed task 10385 this shift; execution-lane assignment returned opencode (repeat handoff, attempt 1/4)
Task: Fix for issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444: fleet queue claim no-task sentinel should be explicit, not an all-null task row — issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444. Fresh check: issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly. Parked 1200s to release the claim for the claimant window.
Expectation: claimant session drives task 10385 to a terminal state.
Links: task 10385 · issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-v
Session / ID: task 10385
Found via: queue claim
Task: Fix of issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444 — execution lane assigned opencode; handed off to the opencode claimant, which launches the bound session.
Expectation: claimant session drives task 10385 to a terminal state under the queue worker id.
Links: issue repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

Agent note - handed off

Agent: opencode claimant (opencode-claimant)
Session / ID: queue task 10385; bound session ses_e5e5361ad78ffem1o1SGn707qg
Found via: queue task handoff on the opencode execution lane
Task: Fix repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444: fleet queue claim no-task sentinel should be explicit, not an all-null task row
Expectation: the bound worker session works task 10385 to a terminal queue state and must not claim another task. It revalidates the issue/PR before acting.
Links: repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

Agent note - handed off

Agent: opencode claimant (opencode-claimant)
Session / ID: queue task 10385; bound session ses_e5e5345cfe5ffeYPGrpLbszaGo
Found via: queue task handoff on the opencode execution lane
Task: Fix repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444: fleet queue claim no-task sentinel should be explicit, not an all-null task row
Expectation: the bound worker session works task 10385 to a terminal queue state and must not claim another task. It revalidates the issue/PR before acting.
Links: repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

Navigation Menu

Repository navigation

repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

Problem

Acceptance

Evidence

4 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

repo-queue: claim can hand out a payload-null task, and list views cannot recover a live claim by lane #5444

Description

Problem

Acceptance

Evidence

Activity

developing-today commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 5, 2026

4 remaining items

developing-today commented on Nov 5, 2026

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions