Drop the single-database split and re-baseline the control migrations

Every deployment has been through the per-blog split, so the code that
performed it (split.go, control migrations 00002–00007) is dead weight, and a
fresh install replaying six migrations only to drop the tables again was
silly. The control chain is now a single 00001_init.sql with the final users
and blogs shape, matching the blog chain.

Goose ignores versions recorded in the database that no longer exist in the
source, but refuses a future migration numbered below the database's highest
version. Databases that went through the split therefore need
`DELETE FROM goose_db_version WHERE version_id > 1` once; README and
AGENTS.md say so.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Sd8UPWrvyYCLj97JexNw3A

1 files changed, 0 insertions, 19 deletions

diff --git a/internal/db/migrations/control/00002_sections.sql b/internal/db/migrations/control/00002_sections.sql
deleted file mode 100644
index 388cb17..0000000
--- a/internal/db/migrations/control/00002_sections.sql
+++ /dev/null
@@ -1,19 +0,0 @@
--- +goose Up
--- Announcements: blog-wide notices shown on every page and post.
-CREATE TABLE sections (
-    id          bigserial PRIMARY KEY,
-    blog_id     bigint NOT NULL REFERENCES blogs(id) ON DELETE CASCADE,
-    title       text NOT NULL DEFAULT '',
-    body_md     text NOT NULL DEFAULT '',
-    body_html   text NOT NULL DEFAULT '',
-    placement   text NOT NULL DEFAULT 'above' CHECK (placement IN ('above', 'below', 'sidebar')),
-    style       text NOT NULL DEFAULT 'note' CHECK (style IN ('plain', 'note', 'warning')),
-    enabled     boolean NOT NULL DEFAULT true,
-    sort_order  integer NOT NULL DEFAULT 0,
-    created_at  timestamptz NOT NULL DEFAULT now(),
-    updated_at  timestamptz NOT NULL DEFAULT now()
-);
-CREATE INDEX sections_blog ON sections (blog_id, sort_order, id);
-
--- +goose Down
-DROP TABLE sections;