- evidence for replay, conflict, replay through a new API process and
after restarting API and storages, keys table, key race,
X-Instance-Id in responses and logs, explicit and invalid
instance_id and key TTL, test runs
- stand evidence: make wipe_data leaves the lab 2 volume intact, build
from a fresh git clone passes smoke, bench restore stage sends with
Idempotency-Key
- REPORT.md: X-Instance-Id, idempotency design, IDEMPOTENCY_TTL_SECONDS
mapping, limitations and evidence rows
- tasks.md: mark the change tasks done, add follow-ups from verify
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- carry the lab 2 solution over and plan lab 3 (PLAN.md, OpenSpec
change instance-id-idempotency)
- rename the compose project to mtusi-lab3 and the image to :lab3
- add X-Instance-Id to every response and instance_id to every log
record ([app] instance_id, hostname by default)
- require Idempotency-Key on POST messages: keys table in Postgres,
key and message in one transaction, replay returns the same 201,
another body gets 409, TTL from [idempotency] ttl_seconds
- send the key from student-tests, k6 scenarios and the skill driver;
add idempotency, X-Instance-Id, key race and fault tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>