Template separates repository guidance from central policies #55

Problem

Template-PSModule needs one local contribution guide, while organization-wide Code of Conduct, security, and support policies are centrally managed by PSModule/.github. Local policy copies would become unmanaged duplicates unless a repository intentionally deviates.

The template also carries .github/release.yml, but Process-PSModule owns module release generation and does not use GitHub's generated-release-notes configuration.

Impact

Repositories created from the template can inherit duplicate policy files and unused release configuration, obscuring which source owns each behavior.

Acceptance criteria

• .github/CONTRIBUTING.md exists and no root CONTRIBUTING.md duplicate remains.
• The contributing guide links to the centrally managed PSModule Code of Conduct, support guidance, and security policy.
• Local .github/CODE_OF_CONDUCT.md, .github/SECURITY.md, and .github/SUPPORT.md copies are absent unless a repository intentionally deviates.
• .github/release.yml is absent because Process-PSModule owns module releases.
• .github/PSModule.yml remains the repository-local Process-PSModule settings surface.
• The README explains the policy inheritance and release ownership boundaries.
• Repository validation passes.

Superseded direction

An earlier revision of this issue proposed local copies of every policy. The clarified PSModule repository standard supersedes that model: organization policies remain central, while the repository owns only its contribution guidance unless it records an intentional policy deviation.