fix(db): make Blogs.BlogId the only blog ID and drop BlogNames

Blogs.BlogId was a one-time copy of BlogNames and nothing kept it
current: 12,238 blogs first seen after 2026-08-07 had a BlogNames ID
but a NULL Blogs.BlogId, so GetBlogs' join on BlogId silently skipped
them and their 23,148 notes.

- retire-blognames.sql: stub Blogs rows for the 17 unregistered note
  participants, backfill IDs (none renumbered), make ix_Blogs_BlogId
  UNIQUE, drop BlogNames, and add triggers that stop a Blogs row with
  a BlogId from being deleted, renamed or renumbered
- AddNote registers both blogs via RegisterBlog (Blogs row + MAX+1 ID)
  and every query resolves names through Blogs instead of BlogNames
- verify-db-schema.sql reports a DB that still has BlogNames (1e)
- Update TL.db.md, AGENTS.md and the DB Browser saved queries

Co-Authored-By: Claude Opus 5.5 <[email protected]>

verify-db-schema.sql

@@ -82,7 +82,8 @@ WITH expected(tbl, col, alter_stmt) AS (
     -- Blogs.BlogId (2026-08-07) is the single-hop join key into Notes. Deliberately NOT
     -- auto-fixable: an added-but-empty BlogId makes every engagement join return zero
     -- rows silently, which is worse than the hard error a missing column gives.
-    ('Blogs','BlogId',                'MANUAL REVIEW - see query 1d: run normalize-notes.sql'),
+    -- Since 2026-09-28 it is the only blog-ID authority (query 1e).
+    ('Blogs','BlogId',                'MANUAL REVIEW - see queries 1d/1e: run normalize-notes.sql, then retire-blognames.sql'),
 
     -- Notes (base columns: manual review if missing)
     -- Integer IDs since 2026-08-07. RootBlogName/NoteBlogName/Type are GONE, not renamed
@@ -101,11 +102,11 @@ WITH expected(tbl, col, alter_stmt) AS (
     -- placeholder. EnsureReplyTextColumnExists in DataAccess.cs adds it the same way.
     ('Notes','replyText',             'ALTER TABLE Notes ADD COLUMN replyText TEXT;'),
 
-    -- BlogNames / NoteTypes (the lookup tables Notes resolves its IDs through, 2026-08-07).
-    -- Not auto-fixable: an empty BlogNames does not mean "add the table", it means the
+    -- NoteTypes (the lookup table Notes resolves TypeId through, 2026-08-07).
+    -- Not auto-fixable: an empty NoteTypes does not mean "add the table", it means the
     -- Notes rows have nothing to resolve against. Rebuild with normalize-notes.sql.
-    ('BlogNames','BlogId',            'MANUAL REVIEW - see query 1d: run normalize-notes.sql'),
-    ('BlogNames','BlogName',          'MANUAL REVIEW - see query 1d: run normalize-notes.sql'),
+    -- BlogNames is not listed: it was dropped on 2026-09-28. Query 1e reports a file
+    -- that still has it.
     ('NoteTypes','TypeId',            'MANUAL REVIEW - see query 1d: run normalize-notes.sql'),
     ('NoteTypes','Type',              'MANUAL REVIEW - see query 1d: run normalize-notes.sql'),
 
@@ -123,7 +124,6 @@ actual(tbl, col) AS (
   SELECT 'Posts',           name FROM pragma_table_info('Posts')
   UNION ALL SELECT 'Blogs',           name FROM pragma_table_info('Blogs')
   UNION ALL SELECT 'Notes',           name FROM pragma_table_info('Notes')
-  UNION ALL SELECT 'BlogNames',       name FROM pragma_table_info('BlogNames')
   UNION ALL SELECT 'NoteTypes',       name FROM pragma_table_info('NoteTypes')
   UNION ALL SELECT 'DailyAPICount',   name FROM pragma_table_info('DailyAPICount')
   UNION ALL SELECT 'ApiKeyPoolState', name FROM pragma_table_info('ApiKeyPoolState')
@@ -146,7 +146,7 @@ ORDER BY (e.alter_stmt LIKE 'ALTER%') DESC, e.tbl, e.col;
 -- 1b. MISSING TABLES: expected tables that don't exist at all in this DB.
 --     Zero rows = good.
 WITH expected_tables(tbl) AS (
-  VALUES ('Posts'),('Blogs'),('Notes'),('BlogNames'),('NoteTypes'),('DailyAPICount'),
+  VALUES ('Posts'),('Blogs'),('Notes'),('NoteTypes'),('DailyAPICount'),
          ('ApiKeyPoolState'),('ApiKeyPoolMeta')
 )
 SELECT et.tbl AS missing_table
@@ -180,7 +180,6 @@ WITH expected(tbl, col) AS (
     ('Notes','RootBlogId'),('Notes','PostID'),('Notes','NoteBlogId'),('Notes','TimeStamp'),
     ('Notes','TypeId'),('Notes','DatetimeCrawled'),('Notes','DateModified'),('Notes','DateCreated'),
     ('Notes','replyText'),('Notes','IsActive'),
-    ('BlogNames','BlogId'),('BlogNames','BlogName'),
     ('NoteTypes','TypeId'),('NoteTypes','Type'),
     ('DailyAPICount','Date'),('DailyAPICount','APICount'),
     ('ApiKeyPoolState','KeyName'),('ApiKeyPoolState','RetryUntil'),
@@ -190,7 +189,6 @@ actual(tbl, col) AS (
   SELECT 'Posts',           name FROM pragma_table_info('Posts')
   UNION ALL SELECT 'Blogs',           name FROM pragma_table_info('Blogs')
   UNION ALL SELECT 'Notes',           name FROM pragma_table_info('Notes')
-  UNION ALL SELECT 'BlogNames',       name FROM pragma_table_info('BlogNames')
   UNION ALL SELECT 'NoteTypes',       name FROM pragma_table_info('NoteTypes')
   UNION ALL SELECT 'DailyAPICount',   name FROM pragma_table_info('DailyAPICount')
   UNION ALL SELECT 'ApiKeyPoolState', name FROM pragma_table_info('ApiKeyPoolState')
@@ -209,7 +207,7 @@ ORDER BY a.tbl, a.col;
 --
 --     This is the one failure SECTION 2 cannot fix. Notes.RootBlogName /
 --     NoteBlogName / Type were replaced by RootBlogId / NoteBlogId / TypeId
---     resolving through BlogNames and NoteTypes -- a data migration, not an
+--     resolving through (then) BlogNames and NoteTypes -- a data migration, not an
 --     ADD COLUMN. There is no compatibility view, so the current code fails
 --     outright ("no such column: RootBlogId") against such a file.
 --
@@ -223,6 +221,28 @@ WHERE lower(name) IN ('rootblogname','noteblogname','type')
 HAVING COUNT(*) > 0;
 
 
+-- 1e. BLOGNAMES NOT RETIRED: a backup from between 2026-08-07 and 2026-09-28, when
+--     BlogNames still held the IDs and Blogs.BlogId was an
+--     unmaintained copy. Zero rows = good.
+--
+--     The current code resolves every Notes ID through Blogs.BlogId and never writes
+--     BlogNames, so against such a file new blogs get IDs that can collide with
+--     BlogNames' and every blog missing from Blogs.BlogId stays invisible to GetBlogs.
+--
+--     Fix: back up, then run retire-blognames.sql (after normalize-notes.sql if 1d
+--     also reported). It checks itself and changes nothing if a check fails.
+SELECT 'BlogNames still exists (' || type || ') -- run retire-blognames.sql' AS blognames_not_retired
+FROM sqlite_master
+WHERE lower(name) = 'blognames'
+UNION ALL
+SELECT 'Blogs.BlogId is not UNIQUE -- run retire-blognames.sql'
+WHERE NOT EXISTS (SELECT 1 FROM pragma_index_list('Blogs') WHERE name = 'ix_Blogs_BlogId' AND "unique" = 1)
+UNION ALL
+SELECT 'BlogId guard trigger missing: ' || t.name || ' -- run retire-blognames.sql'
+FROM (SELECT 'trg_Blogs_BlogId_NoDelete' AS name UNION ALL SELECT 'trg_Blogs_BlogId_Immutable') t
+WHERE NOT EXISTS (SELECT 1 FROM sqlite_master m WHERE m.type = 'trigger' AND m.name = t.name);
+
+
 -- ============================================================================
 -- SECTION 2  --  FIX (opt-in, additive only)
 --
@@ -233,8 +253,8 @@ HAVING COUNT(*) > 0;
 -- subset. These are the 8 additive migration columns and nothing else; the
 -- likes high-water-mark reset is intentionally NOT included.
 --
--- Nothing here addresses query 1d. The Notes integer schema is a data migration
--- (normalize-notes.sql) and cannot be reached by adding columns.
+-- Nothing here addresses queries 1d or 1e. Those are data migrations
+-- (normalize-notes.sql, retire-blognames.sql) and cannot be reached by adding columns.
 -- ============================================================================
 
 -- ALTER TABLE Posts ADD COLUMN PostType TEXT;