📖 [Docs]: Owned automation can roll compatible releases out centrally

[Marius Storhaug (MariusStorhaug)]

Organization- and initiative-owned GitHub Actions and reusable workflows can now use a controlled floating major tag to receive compatible patch and minor releases centrally. External automation remains pinned to immutable full commit SHAs.

Changed: controlled owned-major references

Owned automation may use a major reference such as @v8 only when controlled release automation exclusively maintains the tag and keeps it within that compatible major line. Breaking releases create a new major and require a deliberate fleet campaign before consumers move.

---

Technical details

The canonical ownership-based rule is defined in src/docs/Coding-Standards/GitHub-Actions.md. Supporting supply-chain, dependency, PowerShell, repository, review, release-management, framework, and fleet-orchestration guidance now uses the same boundary.

Implementation plan progress: all planned documentation changes and validation are complete.

Changed surface	Standards checked	Framework docs checked	Result
src/docs/Coding-Standards/**	Security, Dependencies, GitHub Actions, PowerShell	Dependency Updates	Fixed in this PR
src/docs/Ways-of-Working/**	Repository Standard, Review	Fleet Orchestration	Fixed in this PR
src/docs/Capabilities/**	GitHub Actions, Security	Release Management, VS Code Extension Framework	Fixed in this PR

Validation completed with the documentation index check, local and cross-repository link checks, and all 95 Pester tests across 7 suites.

Issue convergence sweep: searched open MSXOrg/docs issues for controlled internal Action pinning; no additional convergent delivery issue was found.

Relevant issues (or links)

• Resolves Document controlled major tags for owned automation #175

Related work

• References 🪲 [Fix]: Update PSResourceGet to latest during Publish-PSModule PSModule/Process-PSModule#163