Preserve unique content in the README default

[Marius Storhaug (MariusStorhaug)]

What

Updates the module README default in PowerShell/Modules/Repository-Defaults.md so that standardizing a README does not delete unique information.

The README is published as the module's landing page on the docs site (for example psmodule.io/<ModuleName>); the per-command reference is generated separately from comment-based help. So the README is often the only published home for prerequisites, platform/dependency notes, authentication and setup guidance, operational behavior (caching, state, update/versioning), and upstream attribution. Deleting it to shorten the README removes it from the site entirely.

Changes to the standard

• Content preservation (keep / trim / relocate, never drop). Preserve unique content; only remove what is genuinely duplicated by the generated command reference.
• Publishing model made explicit. The README publishes as the landing page. Content may move out of the README only into another published home — a command group's overview page under src/functions/public/<Group>/<Group>.md, or comment-based help. A bare top-level docs/ folder is not published, so moving content there drops it from the site. A longer README is acceptable for feature-rich modules; do not shorten by deleting.
• Capabilities showcase is mandatory for implemented modules.
• Upstream attribution exception. Credit, acknowledgements, donation notes, and third-party license notices are retained.
• Fixed the copy/paste-hostile help example and extended README validation.

Gauge

Applied on two content-rich repos so the resulting READMEs can be used to judge the definition:

• 📖 [Docs]: README pages now use the standard module landing-page format NerdFonts#85 — keeps the full README (prerequisites, attribution, usage, caching, update semantics, uninstall) and adds a Documentation pointer.
• 📖 [Docs]: README pages now use the standard module landing-page format GitHub#638 — keeps the full README (use-cases, platforms, complete authentication guide incl. Azure Key Vault) and adds a Documentation pointer.

Follow-up: apply the definition to the remaining standardization PRs, and sync Template-PSModule's README.

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
HTML	Pass ✅
JAVASCRIPT_ES	Pass ✅
JAVASCRIPT_PRETTIER	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter