📖 [Docs]: Move Agentic-Development from Frameworks into Capabilities (#109)

Agentic-Development framework moves from the standalone Frameworks
section into Capabilities, unifying the capability and framework
concepts under a single spec-and-design model. The framework now lives
alongside every other capability — Release Management, Dependency
Updates, Merge Automation, Downstream Release Propagation, VS Code
Extension Framework, PowerShell on GitHub, and Process-PSModule — all
documented consistently by spec (why and what) and design (how).

## Changed: Agentic-Development location and navigation

Agentic-Development now appears under Capabilities in the documentation
site navigation. All four pages (spec.md, design.md, index.md,
memory-template.md) retain their content, front matter, and internal
structure — only their storage location and navigation path changed. The
memory-template.md is still the canonical reference for teams setting up
an Agentic Development org-wide memory repository.

Links throughout the ecosystem that pointed to the old
`Frameworks/Agentic-Development/...` path now point to
`Capabilities/agentic-development/...`. The relative link depth is
unchanged — both old and new locations are two levels under `src/docs`,
so cross-document references like `../../Ways-of-Working/...` continue
to work without modification.

---
<details>
<summary>Technical details</summary>

- Folder moved via `git mv` to preserve commit history:
`src/docs/Frameworks/Agentic-Development/` →
`src/docs/Capabilities/agentic-development/`
- Folder name follows lowercase-kebab convention (matches
`release-management`, `dependency-updates`, `process-psmodule`, etc.)
- `src/zensical.toml`: Added Agentic Development group under
Capabilities nav (index.md, Spec, Design, Memory Repository Template);
removed from Frameworks nav
- Inbound links fixed:
`src/docs/Ways-of-Working/Repository-Type-Property.md` (2 occurrences)
updated to reference new path
- `src/docs/Frameworks/index.md`: Removed Agentic-Development entry;
Frameworks section now states retirement pending
- Auto-generated indexes regenerated: `Capabilities/index.md` and
`Frameworks/index.md` updated by `Update-DocumentationIndex.ps1`
- All validation passing: `Test-DocumentationLink.ps1` confirms all
links resolve; markdownlint reports 0 issues
- Rebased on main (commit c714245) after PR #110 merged Process-PSModule
to Capabilities; merge-tree confirms zero conflicts

</details>

<details>
<summary>Relevant issues</summary>

- Resolves #107
- #102

</details>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

…Frameworks/Agentic-Development/design.md …pabilities/agentic-development/design.mdsrc/docs/Frameworks/Agentic-Development/design.md renamed to src/docs/Capabilities/agentic-development/design.md src/docs/Frameworks/Agentic-Development/design.md renamed to src/docs/Capabilities/agentic-development/design.md

@@ -23,6 +23,7 @@ and design relate and evolve.
 | [VS Code Extension Framework](vscode-extension-framework/index.md) | How a VS Code extension is built, tested, versioned, packaged, and published — one GitHub-native pipeline, opt-in from a template and a single settings file. |
 | [PowerShell on GitHub](powershell-on-github/index.md) | How we make GitHub a first-class platform for PowerShell through reusable modules, actions, and capability gaps we close over time. |
 | [Process-PSModule](process-psmodule/index.md) | The end-to-end PowerShell module pipeline — what it must guarantee and how it is built, alongside reference documentation for configuration and deployment. |
+| [Agentic Development](agentic-development/index.md) | The framework for org-scoped docs and memory repositories that give agents project-specific standards, working knowledge, and behavior. |
 
 <!-- INDEX:END -->
 

…/Frameworks/Agentic-Development/index.md …apabilities/agentic-development/index.mdsrc/docs/Frameworks/Agentic-Development/index.md renamed to src/docs/Capabilities/agentic-development/index.md src/docs/Frameworks/Agentic-Development/index.md renamed to src/docs/Capabilities/agentic-development/index.md

@@ -99,7 +99,7 @@ Both current MSX initiative organizations use this pattern:
 | `PSModule` | `Action`, `Archive`, `Docs`, `Framework`, `FunctionApp`, `Memory`, `Module`, `Other`, `Template`, `Workflow` | `Memory` added to an existing, already-populated `Type` property; the ruleset condition changed from a repository-name allow-list (`~ALL`) to a `Type`-based exclude. |
 
 In both organizations, repositories with `Type: Memory` — the
-[Memory Repository Template](../Frameworks/Agentic-Development/memory-template.md)'s
+[Memory Repository Template](../Capabilities/agentic-development/memory-template.md)'s
 no-PR, direct-commit-to-`main` repositories — are excluded from the org-wide pull-request-
 required ruleset. That template's workflow only works because the ruleset stops matching
 `Memory`-typed repositories; without this, direct pushes to a memory repository's `main`
@@ -112,6 +112,6 @@ are rejected the same as on any other repository.
   rules attached to them.
 - [Repository Standard](Repository-Standard.md) — the mandatory/type-specific/
   repository-specific file-set distinction that `Type` also drives over time.
-- [Memory Repository Template](../Frameworks/Agentic-Development/memory-template.md) — the
+- [Memory Repository Template](../Capabilities/agentic-development/memory-template.md) — the
   concrete repository type whose no-PR workflow motivated excluding `Type: Memory` from the
   pull-request-required ruleset in both current organizations.

…s/Agentic-Development/memory-template.md …s/agentic-development/memory-template.mdsrc/docs/Frameworks/Agentic-Development/memory-template.md renamed to src/docs/Capabilities/agentic-development/memory-template.md src/docs/Frameworks/Agentic-Development/memory-template.md renamed to src/docs/Capabilities/agentic-development/memory-template.md

@@ -49,7 +49,6 @@ Each area below carries its own index. Start here, read the descriptions, and fo
 | [Ways of Working](Ways-of-Working/index.md) | How work happens across the ecosystem — for humans and agents alike. |
 | [Coding Standards](Coding-Standards/index.md) | The shared baseline every repository inherits, and the per-language standards that build on it. |
 | [Capabilities](Capabilities/index.md) | The capabilities the ecosystem builds, each documented by a spec (why and what) and a design (how and what). |
-| [Frameworks](Frameworks/index.md) | The complete, end-to-end frameworks the ecosystem ships — opinionated automation a project adopts wholesale to go from source to shipped. |
 | [Dictionary](Dictionary/index.md) | Shared vocabulary for the MSX ecosystem — the terms a reader or agent meets across these docs. |
 
 <!-- INDEX:END -->

…s/Frameworks/Agentic-Development/spec.md …Capabilities/agentic-development/spec.mdsrc/docs/Frameworks/Agentic-Development/spec.md renamed to src/docs/Capabilities/agentic-development/spec.md src/docs/Frameworks/Agentic-Development/spec.md renamed to src/docs/Capabilities/agentic-development/spec.md

@@ -154,14 +154,11 @@ nav = [
       {"Repository Structure" = "Capabilities/process-psmodule/repository-structure.md"},
       {"Principles and Practices" = "Capabilities/process-psmodule/principles-and-practices.md"},
     ]},
-  ]},
-  {"Frameworks" = [
-    "Frameworks/index.md",
     {"Agentic Development" = [
-      "Frameworks/Agentic-Development/index.md",
-      {"Spec" = "Frameworks/Agentic-Development/spec.md"},
-      {"Design" = "Frameworks/Agentic-Development/design.md"},
-      {"Memory Repository Template" = "Frameworks/Agentic-Development/memory-template.md"},
+      "Capabilities/agentic-development/index.md",
+      {"Spec" = "Capabilities/agentic-development/spec.md"},
+      {"Design" = "Capabilities/agentic-development/design.md"},
+      {"Memory Repository Template" = "Capabilities/agentic-development/memory-template.md"},
     ]},
   ]},
   {"Dictionary" = "Dictionary/index.md"},