forked from mtusi2026/mtusi2026lab2
Evidence comes from the stand started from an empty state and from a fresh clone: the public smoke, the contract checks, lint and 325 own tests, the storage layout with an out-of-API comparison of a stored object against its metadata, failover of each replica under writes, the upload failover scenario, persistence with StartedAt of every service including S3, the S3 outage scenario and 22 S3 privacy and bootstrap checks. The storage evidence script now covers the attachment tables and the S3 secrets. REPORT.md follows the lab 4 template: launch from a clean clone, architecture with the source of truth for each fact, the write order between PostgreSQL and S3 and what each failure leaves behind, where each upload limit applies, roles and services, the .env.example mapping, grade 3 rows and the grade 3 failure table. The design notes the botocore Expect header that hung uploads behind the port proxy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>