Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 244572@bnt-lap001 Assistant-Session: 3b235e1a-ae45-4d0f-ae70-17a9bd78ece8
1.8 KiB
| id | type | title | domain | repo | status | owner | created | updated | related | state_hub_workstream_id | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ACTIVITY-WP-ADHOC-2026-10-19 | workplan | Activity Core owns recovery of lapsed ops_run leases | infotech | activity-core | active | claude-activity-core | 2026-10-19 | 2026-10-19 |
|
b75bd9fb-6308-5195-9a30-d264c0031bf2 |
Origin: rein-aharness REINAH-WP-0003-T05 open point on thread 27cd4c47. When
the worker's first heartbeat gets a 409 before dispatch, the run stays
claimed, because a worker must not close a lease it has lost. Activity
Core's position: that is correct, and recovery is Activity Core's job.
Expire claims that keep losing their lease
id: ACTIVITY-WP-ADHOC-2026-10-19-T01
status: done
priority: high
state_hub_task_id: "63ddf98f-c5e2-5130-8ca3-4a7573fb5c5b"
reopen_stale_claims returned every lapsed claim to open with no attempt
ceiling, so a row that kept losing its lease could cycle forever. New
expire_stale_claims in ops_run_queue.py, which runs before each claim and
behind POST /ops-runs/expire-leases, now reopens lapsed claims below
OPS_RUN_MAX_ATTEMPTS. At the ceiling it sets terminal expired, keeps the
owner for audit and records result.error. A late close on an expired row is
refused as state_conflict. The endpoint returns
{"reopened": n, "expired": m}. Contract documented in
docs/ops-run-queue.md, with three new tests in tests/test_ops_run_queue.py.
Release the expiry change to production
id: ACTIVITY-WP-ADHOC-2026-10-19-T02
status: wait
blocked_on: human-gate:image-release
priority: medium
state_hub_task_id: "d94bfae7-c5ad-585f-96a0-a93a1010c111"
Wait: this ships with the next image release through the normal GitOps path, the same release that carries repository grant v2 (ACTIVITY-WP-0046-T03). No rollout from this session.