From 314ccbcd9de38b75cbe000c0b39c373c18fb0ae9 Mon Sep 17 00:00:00 2001
From: sneak <sneak@sneak.berlin>
Date: Sun, 9 Aug 2026 00:43:49 +0000
Subject: [PATCH] docs: remove stale migration-002 reference from TODO.md

Follows the schema fold: the variant_content table and last_accessed_at
column are now part of 001_initial_schema.sql, not a separate migration.
---
 TODO.md | 25 ++++++++++++-------------
 1 file changed, 12 insertions(+), 13 deletions(-)

diff --git a/TODO.md b/TODO.md
index 250904e..f432faa 100644
--- a/TODO.md
+++ b/TODO.md
@@ -28,19 +28,18 @@ P1: implement blocked networks configuration to extend SSRF protection
   framework (explicit values used exactly with no floor, `0` disables
   the disk cache entirely, omitted defaults to max(75% of free space
   on the filesystem containing `<state_dir>/cache/`, 500 MiB), logged
-  at startup); processed variants are now tracked in the database
-  (migration 002 adds `variant_content` and an LRU timestamp on
-  `source_content`) so total usage is two SUMs, never a directory scan
-  on the hot path; a background goroutine evicts globally
-  least-recently-used entries (variants and source blobs merged) to
-  the limit, woken by a periodic ticker and by write-pressure
-  notifications from stores; a source blob and ALL of its
-  `source_metadata` references are deleted in one transaction before
-  the file is unlinked, so multi-referenced blobs are never removed
-  while referenced and rows never point at deleted files; a startup
-  reconciliation pass adopts untracked variant files, drops rows for
-  missing files, removes unreachable source blobs, and sweeps stale
-  temp files
+  at startup); processed variants are now tracked in the database (a
+  new `variant_content` table and an LRU timestamp on `source_content`)
+  so total usage is two SUMs, never a directory scan on the hot path; a
+  background goroutine evicts globally least-recently-used entries
+  (variants and source blobs merged) to the limit, woken by a periodic
+  ticker and by write-pressure notifications from stores; a source
+  blob and ALL of its `source_metadata` references are deleted in one
+  transaction before the file is unlinked, so multi-referenced blobs
+  are never removed while referenced and rows never point at deleted
+  files; a startup and periodic reconciliation pass adopts untracked
+  variant files, drops rows for missing files, removes unreachable
+  source blobs, and sweeps stale temp files
 - 2026-08-07 validate configuration on startup, fail fast on bad
   config (closes #52): a config value that is set but unparseable or
   invalid aborts startup naming the key and value (defaults apply only