claude: fold in old sow-tools

docs/migration-from-nwn-tool.md

@@ -1,9 +1,18 @@
-# Migrating from `nwn-tool` to Crucible (operator cutover)
+# Migrating from `nwn-tool` to Crucible (cutover — DONE)
 
 The legacy toolchain lives at `gitea/sow-tools` as a single `nwn-tool` binary
 (entry `cmd/nwn-tool`, logic under `internal/`). This repo is the Crucible
-rewrite. Per the migration hard rules, the `internal/` source is **not**
-transplanted automatically — the operator migrates it. This is the checklist.
+rewrite. The cutover below has been **performed**: the `internal/` packages are
+migrated and the `module`/`topdata`/`hak`/`wiki` builders delegate to them. The
+checklist is kept as the record of what was done.
+
+> **Status.** Steps 1–8 are complete. `depot` is the one remaining unwired
+> builder (no legacy source — it was shell `mc`/S3). The open follow-up is the
+> consumer flag contract: `sow-module` / `sow-topdata` / `sow-assets-manifest`
+> wrappers invoke `crucible-<name>` with `--manifest/--source/--out` style flags
+> (see [`consumer-contract.md`](consumer-contract.md)), whereas the migrated
+> commands use the legacy CWD/project model. Reconciling the two is the Phase-6
+> consumer task and is **not** part of this cutover.
 
 ## Why a clean scaffold first