docs: move Agentic-Development into Capabilities (rebased on main after #110)

- Folder moved: src/docs/Frameworks/Agentic-Development → src/docs/Capabilities/agentic-development
- Nav updated in zensical.toml: added under Capabilities alongside Process-PSModule, removed from Frameworks
- Frameworks nav now empty (both frameworks moved to Capabilities); Frameworks/index.md updated with retirement note
- Links fixed: Repository-Type-Property.md (2 occurrences) updated to new path
- Indexes regenerated: Capabilities/index.md and Frameworks/index.md auto-updated
- All validation passing: links resolve, markdownlint clean (112 files, 0 issues)

Rebased on main (commit c714245 after PR #110: Process-PSModule moved to Capabilities).

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

@@ -16,9 +16,8 @@ cover how it works, how to use it, and how to configure it.
 
 <!-- INDEX:START -->
 
-| Section | Description |
+| Page | Description |
 | --- | --- |
-| [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 -->
 

…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

@@ -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/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,15 +154,15 @@ nav = [
       {"Repository Structure" = "Capabilities/process-psmodule/repository-structure.md"},
       {"Principles and Practices" = "Capabilities/process-psmodule/principles-and-practices.md"},
     ]},
+    {"Agentic Development" = [
+      "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"},
+    ]},
   ]},
   {"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"},
-    ]},
   ]},
   {"Dictionary" = "Dictionary/index.md"},
 ]