⚙️ [Maintenance]: Agent guidance links point to documentation that exists

[Marius Storhaug (MariusStorhaug)]

Agents starting work in a module repository reach documentation that exists. AGENTS.md routes to the PSModule framework guidance published at psmodule.io/Process-PSModule and to the MSX organization standards at msx.no/docs, and every public destination resolves. Because the router is the first file an agent reads and the only place the repository names its standards, a module repository generated from this template now carries guidance an agent can actually follow.

Fixed: Router destinations resolve

Seven of the nine links returned 404. The five PSModule entries pointed into a psmodule.github.io/docs/ site that does not exist, and the MSX entries used an alias whose Agentic Development page had moved. The router now names the published pages that serve each topic:

Destination	Page
Creating a module from this template	psmodule.io/Process-PSModule/get-started/
Expected repository layout and required files	psmodule.io/Process-PSModule/reference/repository-standard/
Source layout and framework conventions	psmodule.io/Process-PSModule/guides/structuring-your-module/
The CI/CD pipeline	psmodule.io/Process-PSModule/reference/pipeline-stages/
PowerShell module coding standards	psmodule.io/Process-PSModule/reference/powershell-module-standard/
Agentic Development	msx.no/docs/Capabilities/agentic-development/
Ways of Working	msx.no/docs/Ways-of-Working/
Coding Standards	msx.no/docs/Coding-Standards/

Changed: The router discloses which destinations are private

PSModule/memory and MSXOrg/memory are private repositories, so they answer 404 to a reader without access. The router states that they are private, which distinguishes a destination that needs access from one that is broken.

---

Technical details

• Rewrote the two link lists in AGENTS.md. No other file changes.
• Link check on the result: all 8 public URLs return 200 following redirects; the 2 remaining 404s are the private memory repositories, now labelled as private in prose. The 2 relative links (README.md, CONTRIBUTING.md) resolve in the checkout.
• Verified with markdownlint-cli2 --config .github/linters/.markdown-lint.yml AGENTS.md: 0 issues.

Two independent causes, both worth recording:

• psmodule.github.io/docs/ is not a site. No PSModule/docs repository exists. Framework documentation lives in PSModule/Process-PSModule/docs/content/ and publishes per-repository to psmodule.io/<Repo>/. The entire path prefix, and the Modules/… paths beneath it, were invented — these links never worked.
• msxorg.github.io/docs/ is a redirecting alias. It answers 301 to msx.no/docs/, which is the canonical domain and the form PSModule's own documentation already uses. Ways-of-Working/Agentic-Development/ additionally moved to Capabilities/agentic-development/, so that entry was dead on both counts.

Page titles were checked against each replacement so the link text names the page it reaches, rather than describing a page that no longer exists under that name.

• Standards and framework alignment:

Changed surface	Standards checked	Framework docs checked	Result
AGENTS.md (repository router)	Markdown — links are checked; Agentic Development — the router	Process-PSModule published documentation	Fixed in this PR

• Issue convergence sweep: the one other open issue in this repository, PSModule/Template-PSModule#40, concerns the pull request template's ending blocks and is untouched by this diff. No additional issue is resolved.

Nothing in CI would have caught this. Test-CrossRepositoryLink.ps1 resolves github.com targets, and published-site URLs are explicitly out of scope — the gap the Markdown standard records as MSXOrg/docs#150. Both root causes are filed centrally so the fix does not stay local to this repository.

Relevant issues (or links)

Related work

• References MSXOrg/docs#186 — the docs site is cited by its redirecting alias rather than its canonical domain, across 13 occurrences in 7 files.
• References MSXOrg/docs#187 — an AGENTS.md router can ship with links that resolve to nothing; this repository is the motivating case.
• References MSXOrg/docs#150 — published-site URLs are not verified by the link checks.
• References PSModule/Template-PSModule#50 — the client route files, found in the same audit.

[psmodule-s-shelly]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

Build, test, and publish stages will be skipped for this PR.

If you believe this is incorrect, please verify that your changes are in the correct locations.