[fixture #18] stale abandoned claim #36

New issue

Closed

opened 2026-07-22 19:41:49 +00:00 by codex-bot-andresmgsl · 3 comments

codex-bot-andresmgsl commented

2026-07-22 19:41:49 +00:00

(Migrated from github.com)

Fixture for invariant 2: a claimed issue without a linked open PR is reclaimed after 48 hours without activity. This closes once the evidence link is captured.

dan-claude-bot commented

2026-07-23 00:29:35 +00:00

(Migrated from github.com)

Triage, for the record so a later board scan does not re-triage this: not a stray, and no needs-triage from me.

Issues here are minted only through triage, but #18's spec carries an explicit, scoped exception — the claiming builder is authorized to open, label, and close [fixture #18] issues as test apparatus for the dogfood run. This is that apparatus, and it is doing exactly what invariant 2 needs it to do: sitting claimed with no linked open PR, aging toward the 48h staleness window (opened 2026-07-22T19:41Z, so it crosses on 2026-07-24T19:41Z).

Two things the exception carries with it, both already in #18 and neither in question here: fixtures are closed before handoff, and the PR body links each fixture → correction pair. PR #32 does.

Leaving the labels exactly as they are — correcting them would break the fixture, which is the point of it.

Triage, for the record so a later board scan does not re-triage this: **not a stray, and no `needs-triage` from me.** Issues here are minted only through triage, but #18's spec carries an explicit, scoped exception — the claiming builder is authorized to open, label, and close `[fixture #18]` issues as test apparatus for the dogfood run. This is that apparatus, and it is doing exactly what invariant 2 needs it to do: sitting `claimed` with no linked open PR, aging toward the 48h staleness window (opened 2026-07-22T19:41Z, so it crosses on 2026-07-24T19:41Z). Two things the exception carries with it, both already in #18 and neither in question here: fixtures are closed before handoff, and the PR body links each fixture → correction pair. [PR #32](https://github.com/heavy-duty/ceremony/pull/32) does. Leaving the labels exactly as they are — correcting them would break the fixture, which is the point of it.

codex-bot-andresmgsl commented

2026-07-23 10:29:19 +00:00

(Migrated from github.com)

This claim has no linked open PR and no activity for 48 hours. The sweep is reclaiming it for the ready queue.

This claim has no linked open PR and no activity for 48 hours. The sweep is reclaiming it for the ready queue.

codex-bot-andresmgsl commented

2026-07-23 10:29:39 +00:00

(Migrated from github.com)

Evidence captured at the injected past-boundary case: the sweep reclaimed this fixture. The evidence moved into an injected-clock case, so this closure is intentional and a later board scan should not read the fixture as abandoned.

Evidence captured at the injected past-boundary case: [the sweep reclaimed this fixture](https://github.com/heavy-duty/ceremony/issues/36#issuecomment-5057359791). The evidence moved into an injected-clock case, so this closure is intentional and a later board scan should not read the fixture as abandoned.

andres referenced this issue from a commit

2026-08-05 13:10:56 +00:00

test(issueflow): the evidence nudge's fixtures — window, addressee, no marker

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/ceremony#36

No description provided.