Align agent context paths with organization repositories #191

Context and request

Canonical agent documentation must use real repository identities. The Agentic Development design still names PSModule/docs, which does not exist, instead of the repository that owns PSModule process and standards.

Acceptance criteria

• The Agentic Development design identifies MSXOrg/docs and PSModule/Process-PSModule as the canonical documentation repositories.
• The framework does not prescribe where documentation repositories are cloned locally.
• The newly agreed repository router and AGENTS.md template from main remain unchanged.
• Related documentation uses the same repository model.
• Shared agent context is documentation-only.

Constraints and non-goals

• This change does not duplicate standards inside product repositories.
• This change does not prescribe a new router format, bootstrap implementation, or local filesystem layout.

Technical decisions

• Repository identity is authoritative.
• Runtime and development setup own local checkout placement.
• PSModule/Process-PSModule owns PSModule process and standards content.
• Existing Git freshness requirements remain unchanged.

Implementation plan

• Integrate the latest main changes.
• Preserve the newly agreed root router and canonical AGENTS.md template unchanged.
• Align the Agentic Development source-repository model.
• Remove prescribed local clone paths and remaining shared-context-store guidance.
• Validate documentation, indexes, links, formatting, and the explicit Copilot review loop.