📖 [Docs]: Process-PSModule owns the documentation root

[Marius Storhaug (MariusStorhaug)]

Process-PSModule documentation now lives at the root of the site. Its lifecycle overview, getting-started material, guides, reference, specifications, and media no longer sit beneath a Modules/Process-PSModule source hierarchy.

Changed: The framework owns the root page

The root page now uses the Process-PSModule title, description, and lifecycle content as its primary documentation. It retains the non-duplicated PSModule and cross-organization context from the former root page, so readers land directly in the framework without losing the broader context.

Changed: Clear top-level documentation sections

The navigation now presents Process-PSModule, Getting started, Guides, Reference, Specification, and Modules at the top level. Reference combines the framework's operational contracts with its module-development standards. Modules is the standalone index for discovering the PSModule organization’s modules. Dictionary pages remain published for inline glossary links without occupying a visible navigation tab.

Fixed: The module index generator follows the new structure

The scheduled documentation update now fills the Modules page and publishes each generated module detail page below it. Catalog icons and module links resolve from their new root-level locations, so the next automated refresh updates the visible module index instead of the retired Catalog path.

---

Technical details

• Implementation plan progress: all steps in the scoped Task are complete.
• Moved get-started/, guides/, reference/, specification/, and media/ with git mv, preserving file history.
• Merged the former inner landing page into docs/content/index.md; its front matter, title, and framework content take precedence, while the non-duplicated root content remains below it.
• Moved the module-development standards into docs/content/reference/ and added them to the top-level Reference navigation.
• Replaced the Catalog navigation entry with Modules, whose top-level page is the module index.
• Update-ModuleList now writes generated pages to docs/content/Modules/Repositories/ and replaces the marker in docs/content/Modules/index.md; the V2 catalog template references assets at the correct depth.
• Added an isolated Pester regression test for the catalog generator and installed its declared GitHub module dependency in the action test workflow.
• Dictionary remains in Zensical's navigation graph because unlisted pages are not built; a scoped stylesheet hides its tab and drawer entries while preserving published glossary URLs.
• The strict clean Zensical build succeeds, the catalog Pester suite passes, PSScriptAnalyzer reports no findings, and all in-repository Markdown links resolve.
• Standards and framework alignment:

Changed surface	Standards checked	Framework docs checked	Result
docs/content/**	Documentation Model	Process-PSModule information architecture	Aligned
docs/zensical.toml	Documentation navigation	Zensical navigation indexes	Aligned
.github/actions/update-index/**	PowerShell testing and action conventions	Generated module catalog contract	Aligned
AGENTS.md	Agentic Development	Canonical framework guidance	Aligned

• Issue convergence sweep: reviewed the parent PBI and its current delivery leaves; this pull request implements only the scoped documentation-navigation Task.

Relevant issues (or links)

• Fixes Make Process-PSModule the documentation entry point #451
• Consolidate PSModule documentation into Process-PSModule and retire PSModule/docs #423