Make Process-PSModule the documentation entry point

[MariusStorhaug]

Context and request

Readers should enter the documentation through the Process-PSModule framework at the documentation root. The visible top-level site navigation is Process-PSModule, Getting started, Guides, Reference, Specification, and Modules. Reference combines framework contracts with module-development standards, while Modules is the standalone index of PSModule organization modules. Dictionary pages remain published for inline glossary links but are not directly navigable.

Acceptance criteria

• The Process-PSModule landing-page content is merged into docs/content/index.md, with the inner Process-PSModule title, description, and framework content taking precedence.
• get-started/, guides/, reference/, specification/, and media/ move from docs/content/Modules/Process-PSModule/ to docs/content/ with history preserved.
• The visible top-level navigation is Process-PSModule, Getting started, Guides, Reference, Specification, and Modules.
• Reference includes both Process-PSModule operational contracts and module-development foundations.
• Modules is the standalone page indexing PSModule organization modules.
• The catalog generator writes its table to docs/content/Modules/index.md and its generated module pages to docs/content/Modules/Repositories/.
• Dictionary pages remain generated and linkable but do not appear in visible navigation.
• The Zensical build succeeds without broken navigation or relative links.

Constraints and non-goals

This is a documentation information-architecture change only. It does not change the reusable workflow or reauthor the underlying standards. The previous nested Process-PSModule source paths are intentionally retired rather than retained as duplicate content.

Part of #423.

---

Technical decisions

• Move the existing Process-PSModule directories with git mv so their history follows the content.
• Merge the root and inner landing pages at docs/content/index.md; retain the revised root-level context where it does not duplicate the inner page, but use the inner page's front matter, title, and framework content as authoritative.
• Store module-development standards in docs/content/reference/ alongside Process-PSModule references and retain a foundations overview there.
• Repurpose docs/content/Modules/index.md as the standalone module index, replacing the separate Catalog navigation entry.
• Retarget Update-ModuleList and the V2 catalog template to the new Modules index, generated-page directory, and asset depth; cover the contract with an isolated Pester test.
• Keep Dictionary in Zensical navigation because the current generator builds only navigated pages; use a scoped stylesheet to hide its tab and drawer entries while retaining its linkable generated URLs.
• Update all moved-page relative links, navigation entries, and agent documentation links to the new locations.

Implementation plan

• Inventory the Process-PSModule directories, their inbound links, and their parent-relative links before moving them.
• Move the Process-PSModule directories to docs/content/ with git mv.
• Merge the two landing pages and update Zensical navigation, reference material, module index, catalog, and agent links.
• Retarget the catalog generator and add an action regression test for its new output paths.
• Remove Dictionary from visible navigation while retaining its published pages.
• Correct relative links in moved content and validate the complete site build.

[MariusStorhaug]

Completed the framework-first navigation and landing-page framing. The documentation build succeeds with the established content paths preserved.

[MariusStorhaug]

The scope changed after clarification: Process-PSModule content will move to the documentation root instead of retaining its nested source paths. The task now records the revised implementation plan and acceptance criteria.

[MariusStorhaug]

Completed the root-level relocation: the framework landing page and all workflow sections now live under docs/content, with the nested source hierarchy retired and its links updated.

[MariusStorhaug]

Clarified and completed the final navigation contract: Module-development material is part of Reference, while Modules is the standalone catalog-style module index. The navigation now has the seven requested top-level sections.

[MariusStorhaug]

Removed Dictionary from visible navigation while preserving its generated pages and direct glossary links.

[MariusStorhaug]

Completed the generator follow-up: the module catalog now writes to the promoted Modules index and generated module pages. Dictionary remains published but CSS-hidden because Zensical only generates navigated pages.