Scott Werner f71d077221 Register the SQLite blob activation bridge as a server migration ... The activation module described itself as a temporary compatibility bridge but bypassed the structure the migrations strategy prescribes: no dated migrations/ file, no src/migrations.rs registry entry, no REMOVAL_DEADLINE, and no removal_deadline log field. The strategy doc's removal checklist (grep REMOVAL_DEADLINE, explicit registry ordering) would never have surfaced it, letting the bridge silently outlive its window as a second, parallel migration mechanism in serve.rs. The module now lives at migrations/2026082301_sqlite_blob_activation.rs, is registered and re-exported through src/migrations.rs like the two existing server migrations, carries a REMOVAL_DEADLINE eligibility floor (removal still requires the evidence and explicit approval in the module docs), and logs removal_deadline on every activation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-08-24 14:02:35 -04:00
..
apps	Register the SQLite blob activation bridge as a server migration	2026-08-24 14:02:35 -04:00
components	Size the blob activation disk preflight to the remaining import work	2026-08-24 14:02:35 -04:00
foundation	Make snapshot and backup publication durable across power loss	2026-08-24 14:02:35 -04:00
packages/fabro-api-client	Preserve run creation error context	2026-08-24 12:22:38 -04:00