📖 [Docs]: Module repository page becomes the Repository Standard aligned with MSX (#96)

The PSModule module-repository page is now the organization's
**Repository Standard**. It states plainly that it applies to the
PSModule organization and is the standard for PowerShell module
repositories, and that it operates at the same altitude as the MSX
Enterprise Repository Standard: MSX sets the enterprise-wide default,
and this standard adds to and adjusts that default for PowerShell module
repositories. This builds on #101, which already reshaped the
required-file baseline to match how PSModule repositories actually work;
this PR completes the rename to `Repository-Standard.md`, adds the
explicit MSX-altitude framing, and refines a few file descriptions.

## Changed: The page is now the Repository Standard

The page previously titled "PowerShell module repository defaults" is
now "Repository Standard". Its scope and intro say it is the PSModule
organization's standard for PowerShell module repositories, and a new
layering statement links to the [MSX Enterprise Repository
Standard](https://msxorg.github.io/docs/Ways-of-Working/Repository-Standard/)
so readers know which rules are inherited from MSX and which this
standard adds or overrides. The file was renamed from
`Repository-Defaults.md` to `Repository-Standard.md`, and every
navigation entry and cross-page link now points to the new page.

## Changed: Clearer file descriptions

The descriptions for `.github/dependabot.yml` (both tables),
`.github/pull_request_template.md`, `.gitattributes`, and `.gitignore`
are reworded to explain what each file does for a PowerShell module
repository, and the "linters and release automation read
repository-local files" line is softened to apply only when the module
uses those linters or generates releases. The required-file baseline
itself — MSX-aligned, without `.github/copilot-instructions.md`,
`.github/release.yml`, or the linter files — already landed via #101;
`AGENTS.md`, `CLAUDE.md`, and `.github/PSModule.yml` remain required.

---
<details>
<summary>Technical details</summary>

- Renamed `src/docs/Modules/Repository-Defaults.md` →
`src/docs/Modules/Repository-Standard.md` with `git mv` (rename
preserved, history intact).
- Updated references in `src/zensical.toml` (nav label + path),
`src/docs/Modules/index.md`, `src/docs/Modules/Module-Types.md`, and
`src/docs/Modules/Process-PSModule/module-build-validation.md`.
- Rewrote the H1, scope, and added the altitude/layering statement;
reconciled the prior "initiative implementation" framing with the
MSX-altitude framing.
- Merged `origin/main` (bringing in #101). Two content conflicts in the
layout and required-files tables were resolved by keeping #101's
corrected `Process-PSModule.yml` caller-workflow row,
`.github/release.yml`, and `.github/linters/` rows in the descriptive
layout table, and keeping this PR's more detailed `dependabot` rewording
in both tables. No conflict markers remain; the required-files baseline
matches #101.
- Delivered as three micro-commits plus one merge commit (no
conventional-commit prefixes, Copilot App co-author trailer).

| Changed surface | Standards checked | Framework docs checked | Result
|
| --- | --- | --- | --- |
| `src/docs/Modules/**` (docs) | MSX Repository Standard, PR Format |
PSModule module docs | Aligned |
| `src/zensical.toml` (nav) | Documentation Model | Zensical nav |
Aligned |

- Validation: `zensical build --clean` → "No issues found"; markdownlint
(repo config) → clean.

</details>

<details>
<summary>Relevant issues (or links)</summary>

- Fixes #95

</details>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

src/docs/Modules/Module-Types.md

@@ -103,4 +103,4 @@ The `Hashtable` module demonstrates the full set: `ConvertFrom-Hashtable`, `Conv
 ## Where this connects
 
 - [PowerShell module standard](Standards.md): layout, private functions, and the mandatory context parameter.
-- [Repository Defaults](Repository-Defaults.md): repository files, README shape, and agent onboarding.
+- [Repository Standard](Repository-Standard.md): repository files, README shape, and agent onboarding.

src/docs/Modules/Process-PSModule/module-build-validation.md

@@ -29,7 +29,7 @@ Do not repeat the shared workflow here. Follow the shared branch → draft PR 
 
    Check:
 
-   - `README.md` still answers the start-page questions and reflects any user-visible behavior, prerequisites, or setup changes from [Repository Defaults](../Repository-Defaults.md#readme-default)
+   - `README.md` still answers the start-page questions and reflects any user-visible behavior, prerequisites, or setup changes from [Repository Standard](../Repository-Standard.md#readme-default)
    - the relevant public command-group overview page (`src/functions/public/<Group>/<Group>.md`) exists or is updated when the change affects that group's purpose or usage, per [PowerShell module standard](../Standards.md#repository-layout)
    - any module-level documentation under `docs/` or other published surfaces is updated when the change adds or changes guidance that should not live only in comment-based help
 
@@ -90,5 +90,5 @@ Do not repeat the shared workflow here. Follow the shared branch → draft PR 
 - [PowerShell module standard](../Standards.md)
 - [Module types](../Module-Types.md)
 - [Module Anatomy](module-anatomy.md)
-- [Repository Defaults](../Repository-Defaults.md)
+- [Repository Standard](../Repository-Standard.md)
 - [MSX Coding Standards](https://msxorg.github.io/docs/Coding-Standards/)

src/docs/Modules/Repository-Defaults.md src/docs/Modules/Repository-Standard.mdsrc/docs/Modules/Repository-Defaults.md renamed to src/docs/Modules/Repository-Standard.md

@@ -1,21 +1,23 @@
-# PowerShell module repository defaults
+# Repository Standard
 
-This page defines the default repository contract for PowerShell module repositories in the PSModule organization. It describes what a newly created or maintained module repository should look like before module-specific code, tests, documentation, and managed repository files are considered.
+This is the PSModule organization's Repository Standard. It applies to the PSModule organization and is the standard for PowerShell module repositories. It describes what a newly created or maintained module repository should look like before module-specific code, tests, documentation, and managed repository files are considered.
 
-The implementation standard still lives in [PowerShell module standard](Standards.md). Type-specific conventions for integration (API) and data modules live in [Module types](Module-Types.md). This page covers repository defaults: files, metadata, README shape, release integration, placeholder handling, shared community files, and managed-file distribution.
+This standard operates at the same altitude as the [MSX Enterprise Repository Standard](https://msxorg.github.io/docs/Ways-of-Working/Repository-Standard/): MSX sets the enterprise-wide default, and this standard adds to and adjusts that default for PowerShell module repositories. Rules this standard does not change are inherited from the MSX default; where this standard adds or overrides a rule, it governs PowerShell module repositories.
+
+The implementation standard still lives in [PowerShell module standard](Standards.md). Type-specific conventions for integration (API) and data modules live in [Module types](Module-Types.md). This page covers the repository standard for module repositories: files, metadata, README shape, release integration, placeholder handling, shared community files, and managed-file distribution.
 
 ## Scope
 
-These defaults apply to repositories whose primary artifact is a PowerShell module published through the PSModule framework.
+This standard applies to repositories whose primary artifact is a PowerShell module published through the PSModule framework.
 
-They do not apply directly to:
+It does not apply directly to:
 
 - GitHub Action repositories such as `Build-PSModule`, `Invoke-Pester`, or `Publish-PSModule`.
 - Documentation repositories such as `PSModule/docs`.
 - Template repositories other than `Template-PSModule`.
 - Test, archive, service, or infrastructure repositories that are not published as module artifacts.
 
-Two baseline expectations still apply to every PSModule repository, including the types listed above. Each repository stands on its own: it carries its own governance and community files instead of relying on the organization `.github` fallback, and each repository ships the [agent onboarding files](#agent-onboarding-files) so an agent can work in it without prior context. What differs by type is the concrete file set and layout: the required files, README shape, and framework wiring on the rest of this page are module defaults, and non-module repositories keep only the equivalent baseline appropriate to their own type. This repository, `PSModule/docs`, follows those two baseline expectations itself.
+Two baseline expectations still apply to every PSModule repository, including the types listed above. Each repository stands on its own: it carries its own governance and community files instead of relying on the organization `.github` fallback, and each repository ships the [agent onboarding files](#agent-onboarding-files) so an agent can work in it without prior context. What differs by type is the concrete file set and layout: the required files, README shape, and framework wiring on the rest of this page are the module standard, and non-module repositories keep only the equivalent baseline appropriate to their own type. This repository, `PSModule/docs`, follows those two baseline expectations itself.
 
 Each initiative should keep its own repository standards in its central documentation repository. For the PSModule organization, this repository is the source of truth.
 
@@ -88,11 +90,11 @@ Module repositories use the PSModule framework layout:
 | `.github/workflows/Process-PSModule.yml` | Caller workflow that runs the module's CI/CD by calling the shared Process-PSModule workflow. |
 | `.github/release.yml` | Release-note and changelog categorization for GitHub releases. |
 | `.github/linters/` | Linter configuration used by the framework's linting stage, including `.markdown-lint.yml` and `.powershell-psscriptanalyzer.psd1`. |
-| `.github/dependabot.yml` | Dependency and supply-chain update configuration. |
+| `.github/dependabot.yml` | Configures ecosystem-appropriate dependency-update pull requests. For PowerShell module repositories the `github-actions` ecosystem is expected; add any other ecosystems the module actually develops in. |
 | `.github/CODEOWNERS` | Ownership routing for reviews and protected areas. |
-| `.github/pull_request_template.md` | PR Manager-compatible pull request template. |
-| `.gitattributes` | Git line-ending and file handling defaults. |
-| `.gitignore` | Shared ignore rules. |
+| `.github/pull_request_template.md` | Scaffolds pull requests in the MSX PR Format (PR Manager) style — an icon + change-type + user-facing-outcome title, user-facing description sections, an optional technical-details block, and a related-issues block. |
+| `.gitattributes` | Normalizes line endings and declares text/binary handling so the module can be developed and built consistently on Linux, macOS, and Windows. |
+| `.gitignore` | Ignores files that must never be committed, tailored to the PowerShell-module ecosystem: operating-system files, editor and developer-tooling files, PowerShell and Pester test-harness artifacts, and all local build outputs and files created during build and test. |
 | `src/` | Module source compiled into the shipped artifact. |
 | `src/functions/public/` | Exported commands, grouped by domain. |
 | `src/functions/private/` | Internal helper commands, grouped by domain. |
@@ -132,7 +134,7 @@ Name the caller file `Process-PSModule.yml`, matching [`PSModule/Template-PSModu
 Every module repository must carry the same baseline community, governance, and automation files. GitHub's organization-level `.github` community-file fallback is useful for display defaults, but it is not enough as the long-term PSModule standard because:
 
 - agents and humans need the files in the repository they are changing, not only inherited through GitHub UI behavior;
-- tools such as Dependabot, linters, CODEOWNERS, and release automation read repository-local files;
+- tools such as Dependabot and CODEOWNERS read repository-local files — as do linters and release automation when the module uses those linters or generates releases;
 - reviews need diffs against the actual managed file in the target repository;
 - repository-local files make the standard portable to other initiatives such as MSXOrg, where each initiative should define its own standards and managed files;
 - central fallback files in `PSModule/.github` do not provide a reliable enforcement or update workflow across all repositories.
@@ -149,15 +151,12 @@ Required baseline files for module repositories:
 | `CODE_OF_CONDUCT.md` | Community participation rules. |
 | `AGENTS.md` | Cross-tool agent instructions pointing to the canonical guidance in `PSModule/docs`. |
 | `CLAUDE.md` | Claude Code entry point that imports `AGENTS.md`. |
-| `.github/dependabot.yml` | Supply-chain maintenance for GitHub Actions and any other Dependabot ecosystem the repository actually uses. |
+| `.github/dependabot.yml` | Configures ecosystem-appropriate dependency-update pull requests. For PowerShell module repositories the `github-actions` ecosystem is expected; add any other ecosystems the module actually develops in. |
 | `.github/CODEOWNERS` | Review routing for source, docs, and GitHub workflow files. |
-| `.github/pull_request_template.md` | Consistent PR Manager-style PR descriptions and change classification. |
-| `.github/release.yml` | Release-note and changelog categorization where the repository creates GitHub releases. |
+| `.github/pull_request_template.md` | Scaffolds pull requests in the MSX PR Format (PR Manager) style — an icon + change-type + user-facing-outcome title, user-facing description sections, an optional technical-details block, and a related-issues block. |
 | `.github/PSModule.yml` | Module workflow defaults and overrides. |
-| `.github/linters/.markdown-lint.yml` | Markdown linting defaults. |
-| `.github/linters/.powershell-psscriptanalyzer.psd1` | PSScriptAnalyzer defaults. |
-| `.gitattributes` | Git attribute defaults. |
-| `.gitignore` | Shared ignore rules. |
+| `.gitattributes` | Normalizes line endings and declares text/binary handling so the module can be developed and built consistently on Linux, macOS, and Windows. |
+| `.gitignore` | Ignores files that must never be committed, tailored to the PowerShell-module ecosystem: operating-system files, editor and developer-tooling files, PowerShell and Pester test-harness artifacts, and all local build outputs and files created during build and test. |
 
 Repositories can add local files, but they should not remove these baseline files unless the repository is explicitly outside the module standard.
 

src/docs/Modules/index.md

@@ -10,7 +10,7 @@ This section is the local source of truth for:
 
 ## Sections
 
-- [Repository Defaults](Repository-Defaults.md)
+- [Repository Standard](Repository-Standard.md)
 - [Standards](Standards.md)
 - [Module types](Module-Types.md)
 - [Test Specification](Test-Specification.md)

src/zensical.toml

@@ -19,7 +19,7 @@ watch = ["includes"]
 nav = [
   {"Modules" = [
     "Modules/index.md",
-    {"Repository Defaults" = "Modules/Repository-Defaults.md"},
+    {"Repository Standard" = "Modules/Repository-Standard.md"},
     {"Standards" = "Modules/Standards.md"},
     {"Module types" = "Modules/Module-Types.md"},
     {"Test Specification" = "Modules/Test-Specification.md"},