* fix(claim): verify claim-family writes by re-read under a degraded server (bd-zccb9)
From wyvern incident wy-ejph3: under a degraded dolt sql-server the exit
status of a claim is not truth in either direction — a reported success
can roll back with the abandoned connection (phantom claim), and a
printed connection error can mask an applied write (wy-x543k).
New verifiedClaimWrite resolves claim-family outcomes against the DB
instead of trusting exit status: reported success is verified by
re-read and fails loudly on mismatch; an indeterminate commit-phase
loss (errCommitPhase) is settled by re-read — applied becomes success,
verified-rolled-back is replayed once. Wired into ClaimIssue,
UnclaimIssue, UnclaimIssueIfAssignee, and ClaimReadyIssue (bespoke:
claimed ID only known post-body; a replay may legitimately claim a
different issue). Wisps and non-server mode exempt.
Metrics: bd.claim_verify_lost_total, bd.claim_verify_recovered_total
(op, outcome=applied|replayed).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(proposal): CAS conditional update design for bd-wsqvw (from fly)
Design handoff from wyvern's wheelhouse hostile-review (epic wy-mdi5h):
generalize the claim-side CAS into --if-assignee/--if-status guards on
'bd update', covering the X->Y reassign and status-guarded
claim-on-behalf transitions that --claim and unclaim --if-assignee
cannot express. Authored by fly; committed so the untracked doc
survives workspace cleanup. Depends on bd-zccb9 (verify-after-write).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(claim): ready-claim replay leg keeps verify semantics (bd-zccb9, lion review)
The bespoke ClaimReadyIssue path's replay returned raw on any error, so a
replayed write dying at commit phase skipped the verify pass — reintroducing
the wy-x543k false-failure on attempt two, and potentially orphaning an
applied claim on a DIFFERENT ready issue than the first attempt selected.
The replay now falls through to verify on errCommitPhase-with-selection,
exactly like verifiedClaimWrite's leg: applied -> recovered success,
verified rollback -> honest 'did not land' (budget already spent).
Extracted the resolution loop as verifiedReadyClaim so injection tests can
drive the write seam; sixth test mirrors ConvertsAppliedIndeterminate on
the replay leg.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>