mkdocs build --strict on unity/v6.0 emits one warning:
WARNING - mkdocs_autorefs: cli/commands/cli-command-reference/services/update-dockerfile.md:
Could not find cross-reference target 'REMOVED'
'REMOVED' looks like a placeholder that leaked out of the CLI documentation generator — most likely a retired command or argument whose cross-reference target was replaced with the literal string rather than dropped.
This is in docs/cli/commands/cli-command-reference/, which is both auto-generated (AGENTS.md: do not edit the Markdown directly) and core-owned (synced by auto-sync-core). So the fix belongs upstream in the generator; editing the Markdown would be overwritten on the next core push and would regress on the next regeneration regardless.
Worth checking whether other branches carry the same warning and whether 'REMOVED' appears elsewhere in generated output — a single leaked placeholder suggests the generator has a path where a missing target is stringified instead of omitted.
Low severity: one broken cross-reference on one generated page. Filed mainly because it is the only real build warning on the branch, and a clean --strict build is worth having so that future warnings are visible rather than lost in known noise.
mkdocs build --strictonunity/v6.0emits one warning:'REMOVED'looks like a placeholder that leaked out of the CLI documentation generator — most likely a retired command or argument whose cross-reference target was replaced with the literal string rather than dropped.This is in
docs/cli/commands/cli-command-reference/, which is both auto-generated (AGENTS.md: do not edit the Markdown directly) and core-owned (synced byauto-sync-core). So the fix belongs upstream in the generator; editing the Markdown would be overwritten on the next core push and would regress on the next regeneration regardless.Worth checking whether other branches carry the same warning and whether
'REMOVED'appears elsewhere in generated output — a single leaked placeholder suggests the generator has a path where a missing target is stringified instead of omitted.Low severity: one broken cross-reference on one generated page. Filed mainly because it is the only real build warning on the branch, and a clean
--strictbuild is worth having so that future warnings are visible rather than lost in known noise.