Archived change docs alignment

Author: djm81

…ocs-cli-command-alignment/.openspec.yaml …ocs-cli-command-alignment/.openspec.yamlopenspec/changes/docs-cli-command-alignment/.openspec.yaml renamed to openspec/changes/archive/2026-03-20-docs-cli-command-alignment/.openspec.yaml openspec/changes/docs-cli-command-alignment/.openspec.yaml renamed to openspec/changes/archive/2026-03-20-docs-cli-command-alignment/.openspec.yaml

@@ -5,13 +5,14 @@ TBD - created by archiving change docs-01-modules-docs-canonical-site. Update Pu
 ## Requirements
 ### Requirement: Modules docs site is the canonical home for official bundle documentation
 
-The modules documentation site SHALL present itself as the canonical published home for official bundle and module-specific deep documentation.
+The modules documentation site SHALL present itself as the canonical published home for official bundle and module-specific deep documentation, and its command examples SHALL match the currently mounted CLI surface shipped with the official modules.
 
-#### Scenario: Reader opens modules landing page
+#### Scenario: Reader follows a command example from the modules docs
 
-- **WHEN** a reader opens the modules docs landing page
-- **THEN** the page states that official bundle and module-specific deep guidance is owned by `specfact-cli-modules`
-- **AND** the page does not describe the GitHub Pages project-path URL as the long-term canonical public identity.
+- **WHEN** a reader copies a command example from the modules docs reference or installation pages
+- **THEN** the example uses a command path that is currently mounted in `specfact --help`
+- **AND** the example does not rely on removed top-level shims such as flat `sync`, `repro`, `validate`, or `enforce` command groups when the mounted path is nested under another group
+- **AND** official bundle install examples use the current published module ids from `specfact-cli-modules`
 
 ### Requirement: Modules docs expose shared cross-site navigation