chore(db): regenerate skill package migration on current master

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/DATABASE.md

@@ -1256,7 +1256,7 @@ transaction boundary.
 
 `company_skill_repository_snapshots` retains its identity and company/content-hash
 uniqueness. Despite its historical name, it can also hold editable skill packages.
-Migration 0401 (`0401_icy_sister_grimm.sql`) adds `storage` (archive/manifest receipts) and `upload` (a bounded
+Migration 0402 (`0402_empty_overlord.sql`) adds `storage` (archive/manifest receipts) and `upload` (a bounded
 pending attempt). `file_inventory` remains the legacy payload, defaulting to `[]`.
 `company_skill_versions.package_snapshot_id` and `package_file_map` preserve the
 public version file inventory without storing its contents again. Existing repository

doc/skill-package-storage.md

@@ -10,7 +10,7 @@ locally authored/edited packages and unproven legacy packages keep a durable cop
 ## Automatic upgrade
 
 No data-migration command is required. The normal schema upgrade applies migration
-0401 (`0401_icy_sister_grimm.sql`). External writes and automatic conversion are enabled by default. Startup
+0402 (`0402_empty_overlord.sql`). External writes and automatic conversion are enabled by default. Startup
 restores pending work from indexed `migration_at` / `maintenance_at` columns. The
 shared delivery coordinator converts four snapshots and four versions per batch,
 reading one legacy body at a time. It verifies the hash, uploads, reads the objects