docs(configuration,cli[migrate]) Cross-link the migration surfaces

tony · tony · commit e90ed1113e97 · 2026-05-31T14:01:05.000-05:00
why: The migration story spans three pages (config schema, the migrate
command, and the migration notes); readers landing on one had no path to
the others.
what:
- Link the configuration migration subsection to the migration notes
- Add a 'See also' on the migrate command page pointing to the config
  schema and the migration notes
diff --git a/docs/cli/migrate.md b/docs/cli/migrate.md
@@ -74,3 +74,8 @@ $ vcspull migrate --all --write
 
 Migration is idempotent—running it again on an already-migrated file makes no
 changes.
+
+## See also
+
+- {ref}`configuration` — the `options:` block and its sync-tuning keys.
+- {ref}`migration` — the deprecation note for the top-level form.
diff --git a/docs/configuration/index.md b/docs/configuration/index.md
@@ -194,6 +194,9 @@ existing configs in place:
 $ vcspull migrate --write
 ```
 
+See {ref}`migration` for the deprecation note and {ref}`cli-migrate` for the
+command reference.
+
 (config-pin)=
 
 ## Repository pinning
