Restructure products into top-level PowerShell and GitHub Actions sections

- PowerShell-Modules/ replaced by PowerShell/ with sub-sections: Modules, Scripts, DSC
- Each sub-section has its own index and Standards page
- PowerShell module standards moved from Agents/Standards/ to PowerShell/Modules/Standards.md
- GitHub Actions standards moved from Agents/Standards/ to GitHub-Actions/Standards.md
- Agents/Standards/index.md updated to link to canonical locations
- GitHub Actions promoted to top-level nav entry (was nested under Projects)
- Projects nav group removed
- zensical.toml nav updated throughout

Author: MariusStorhaug

docs/Agents/Standards/index.md

@@ -10,8 +10,8 @@ Per-language and per-platform standards referenced by the [Builder](https://gith
 
 ## Available standards
 
-- **[PowerShell Modules](PowerShell-Module.md)** — module layout, naming, parameter design, style, tests.
-- **[GitHub Actions](GitHub-Actions.md)** — workflow security, SHA pinning, permissions, OIDC, the Zizmor checklist.
+- **[PowerShell Modules](../../PowerShell/Modules/Standards.md)** — module layout, naming, parameter design, style, tests.
+- **[GitHub Actions](../../GitHub-Actions/Standards.md)** — workflow security, SHA pinning, permissions, OIDC, the Zizmor checklist.
 
 > More standards will be added as PSModule adopts more languages and platforms. Each new standard follows the same shape: principles → concrete rules → examples.
 

docs/Agents/Standards/GitHub-Actions.md docs/GitHub-Actions/Standards.mddocs/Agents/Standards/GitHub-Actions.md renamed to docs/GitHub-Actions/Standards.md

@@ -0,0 +1,5 @@
+# DSC
+
+PowerShell Desired State Configuration (DSC) resources for declarative system configuration.
+
+> This section is coming soon. Standards and conventions for DSC resources will be documented here.

docs/PowerShell-Modules/index.md

@@ -0,0 +1,9 @@
+# Modules
+
+PSModule modules are reusable PowerShell libraries published to the PowerShell Gallery. They are built with the [PSModule framework](https://github.com/PSModule/PSModule) and follow a consistent layout, naming, and versioning convention.
+
+## What's covered
+
+- **[Standards](Standards.md)** — Repository layout, naming, style, parameter design, comment-based help, and SOLID applied to PowerShell modules.
+- **[Test Specification](Test-Specification.md)** — How we write Pester tests: structure, hierarchy, and naming conventions.
+- **[Versioning](Versioning.md)** — How changes to the public interface determine the SemVer version bump.

docs/PowerShell/DSC/index.md

@@ -0,0 +1,11 @@
+# Script Standards
+
+Standards for writing standalone PowerShell scripts in the PSModule ecosystem.
+
+> This page is a stub. Standards will be documented here as conventions stabilise.
+
+## General principles
+
+- Scripts follow the same naming, style, and parameter conventions as module functions. See [Module Standards](../Modules/Standards.md) as the baseline.
+- Scripts that grow beyond a single responsibility should be promoted to module functions.
+- All scripts must run on PowerShell (cross-platform) — not Windows PowerShell 5.1.

…cs/Agents/Standards/PowerShell-Module.md docs/PowerShell/Modules/Standards.mddocs/Agents/Standards/PowerShell-Module.md renamed to docs/PowerShell/Modules/Standards.md docs/Agents/Standards/PowerShell-Module.md renamed to docs/PowerShell/Modules/Standards.md

@@ -0,0 +1,7 @@
+# Scripts
+
+Standalone PowerShell scripts used for automation, tooling, and developer workflows across the PSModule ecosystem.
+
+## What's covered
+
+- **[Standards](Standards.md)** — How we write, name, and structure PowerShell scripts.