fabro/lib/apps
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
..
fabro-cli Preserve run creation error context 2026-08-24 12:22:38 -04:00
fabro-mcp-server Address Copilot review comments 2026-08-01 09:18:57 -04:00
fabro-server Register the SQLite blob activation bridge as a server migration 2026-08-24 14:02:35 -04:00
fabro-spa refactor: organize crates into three layers 2026-07-23 17:59:34 -04:00