forked from mtusi2026/mtusi2026lab2
reconcile-inject.sh and reconcile_check.py come from the prepared kit: the first breaks either side on purpose (an object without a row, a removed object, another size, the same size with other bytes, an old intent with and without its object), the second is an oracle outside the API that classifies every row and object from psql and rc, hashes objects with --deep and reports ready attachments lost against a saved set. reconcile_track.py demo uploads through the balancer, links some attachments to messages, injects each class on both sides with old and fresh variants, and checks that a deep dry-run finds exactly what was injected and changes nothing, that apply fixes exactly that and a second apply does nothing, that broken rows and their message links survive in quarantine with metadata 200 and content 404, that a restored object heals, that a second pass is skipped while the lock is held, and that passes in a loop during 75 s of uploads lose nothing. Intents are injected 300 s old, between the reconciler grace and the API sweep grace, so only the reconciler removes them. reconcile_track.py cost snapshots docker stats of the whole host, pins S3, PostgreSQL and the reconciler to their own CPUs, fills the stand to each N with seed_storage.py run in the API image (parallel PutObject and COPY), and records three dry runs per N and mode with a median table. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27