docs(agent-context): move the renames section after the migration workflow list

The section split the numbered workflow, leaving step 3 (Apply) detached after it.
Conformance fixtures regenerated.

Author: dmealing

agent-context/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.

fixtures/agent-context-conformance/csharp/expected/.claude/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.

fixtures/agent-context-conformance/java-kotlin-react-tanstack/expected/.claude/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.

fixtures/agent-context-conformance/java-react/expected/.claude/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.

fixtures/agent-context-conformance/python/expected/.claude/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-verify/references/migration.md

@@ -114,6 +114,18 @@ meta migrate baseline --from-db --db postgresql://... --dialect postgres
    below), and an ambiguous rename-vs-drop+add aborts unless you declare the rename
    or choose with `--on-ambiguous`. It never guesses.
 
+3. **Apply** the pending migrations against the DB; migration history is tracked in
+   a ledger table:
+
+   ```bash
+   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
+                                                              # generate ...and apply it
+   meta migrate apply-pending --db postgresql://... --dialect postgres
+                                                              # replay committed migrations, no diff (fresh DB / CI)
+   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
+   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
+   ```
+
 ## Renames and destructive changes
 
 A renamed field or object is a renamed column or table, and the diff cannot tell that
@@ -147,18 +159,6 @@ meta migrate --dialect postgres --slug rename-stop   --rename-table stop=port_ca
 `docs/features/migrations-and-drift.md`, "Renames and populated tables", covers what a
 rename carries with it (constraint names, views) and changes that need a backfill.
 
-3. **Apply** the pending migrations against the DB; migration history is tracked in
-   a ledger table:
-
-   ```bash
-   meta migrate --dialect postgres --slug add-user-shipping --db postgresql://... --apply
-                                                              # generate ...and apply it
-   meta migrate apply-pending --db postgresql://... --dialect postgres
-                                                              # replay committed migrations, no diff (fresh DB / CI)
-   meta migrate --db postgresql://... --rollback <target>     # run down.sql for migrations newer than <target>
-   meta migrate --db postgresql://... --rollback ""           # roll back everything (empty target)
-   ```
-
 ## Dialects
 
 - `postgres` (default) — native `ALTER`s.