docs: migrate managed-file distribution from PSModule/Distributor to MSXOrg/Custo

[Marius Storhaug (MariusStorhaug)]

Summary

Updates Repository-Defaults.md to reflect the decision to use MSXOrg/Custo as the central distribution engine, replacing PSModule/Distributor.

Changes

• src/docs/Modules/Repository-Defaults.md — "Managed file distribution" section rewritten to:
  • Reference MSXOrg/Custo as the distribution runtime
  • Explicitly separate policy ownership (PSModule/docs) from distribution runtime (MSXOrg/Custo)
  • Preserve all existing behavioral semantics: managed-files/update branch, ⚙️ [Maintenance]: Sync managed files PR convention, overwrite behavior, explicit-delete semantics
  • Expand the migration note to cover the Distributor → Custo transition

Wording decisions for maintainer confirmation

1. "Custo source file sets" — the migration steps reference moving content changes into Custo. Confirm the terminology Custo uses for its canonical file sets (e.g., file-sets/, sources/, or another name).
2. Scope of migration note — the note covers both "Distributor-aligned repos" and "older distribution behavior". If there's a cutover date or a tracked issue for the migration work, linking it would help repositories know when they need to act.
3. Cross-link to Custo docs — if MSXOrg/docs or MSXOrg/Custo publishes its own distribution documentation, adding a cross-link from this page would strengthen the separation-of-concerns narrative. Should that link be added when those docs exist, or should a placeholder be added now?

Type of change

• Documentation update (no source code changes)

[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