Azure-Samples · Cataldir · Mar 18, 2026 · Mar 18, 2026
diff --git a/.github/agents/azure-aks.agent.md b/.github/agents/azure-aks.agent.md
@@ -157,7 +157,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-apim.agent.md b/.github/agents/azure-apim.agent.md
@@ -161,7 +161,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-blob.agent.md b/.github/agents/azure-blob.agent.md
@@ -162,7 +162,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-container-apps.agent.md b/.github/agents/azure-container-apps.agent.md
@@ -171,7 +171,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-cosmos.agent.md b/.github/agents/azure-cosmos.agent.md
@@ -178,7 +178,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-foundry.agent.md b/.github/agents/azure-foundry.agent.md
@@ -165,7 +165,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-postgres.agent.md b/.github/agents/azure-postgres.agent.md
@@ -179,7 +179,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-redis.agent.md b/.github/agents/azure-redis.agent.md
@@ -168,7 +168,7 @@ Before generating plans, recommendations, or implementation guidance, you MUST f
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/azure-swa.agent.md b/.github/agents/azure-swa.agent.md
@@ -508,7 +508,7 @@ Always prioritize SWA CLI solutions over manual configuration. When manual confi
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/business-strategy-agent.agent.md b/.github/agents/business-strategy-agent.agent.md
@@ -156,21 +156,21 @@ flowchart TD
 
 ## Data Ownership
 
-- **Canonical output path**: `myself/business/strategy/`
+- **Canonical output path**: `myself/business/strategy/` (when this path exists in the workspace)
 - **Aggregation role**: Synthesizes outputs from CompetitiveIntelAnalyst, FinancialModeler, RiskAnalyst, and ProcessImprover
 - **Scope boundary**: Business competitive strategy only — publishing strategy belongs to MarketAnalyzer/Scout; technical architecture belongs to SystemArchitect
 
 ## References
 
-- [`myself/knowledge/`](../../myself/knowledge/) — Domain expertise inventory
+- `myself/knowledge/` — Domain expertise inventory (if available in workspace)
 - [Porter's Five Forces](https://hbr.org/1979/03/how-competitive-forces-shape-strategy) — Competitive analysis framework
 - [Blue Ocean Strategy](https://www.blueoceanstrategy.com/) — Market creation framework
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/cataldi-librarian.agent.md b/.github/agents/cataldi-librarian.agent.md
@@ -2,7 +2,7 @@
 name: ContentLibrarian
 description: "Repository librarian: categorizes, files, and cross-references content assets. Maintains README indexes, enforces governance-map placement rules, and ensures every artifact has a canonical home."
 argument-hint: "Categorize and file the newly completed Chapter 6 of the AI Operations book, update the content README index, and verify cross-references in the governance map"
-tools: ['execute', 'read', 'edit', 'search', 'web', 'agent', 'todo']
+tools: ['execute', 'read', 'edit', 'search', 'web', 'agent', 'todo', 'filesystem']
 user-invocable: true
 disable-model-invocation: false
 ---
@@ -77,10 +77,10 @@ When content in one category relates to content in another, add a "Related Conte
 ```markdown
 ## Related Content
 
-- **Book:** [Book Name](../../book/book-name/)
-- **Posts:** [Post Title](../../posts/post-slug/)
-- **Paper:** [Paper Title](../../papers/paper-slug/)
-- **Course:** [Course Name](../../courses/course-name/)
+- **Book:** [Book Name](book/book-name/)
+- **Posts:** [Post Title](posts/post-slug/)
+- **Paper:** [Paper Title](papers/paper-slug/)
+- **Course:** [Course Name](courses/course-name/)
 ```
 
 ### 5. Quality Checks
@@ -137,15 +137,15 @@ When working inside a repository that has content structure specifications in `.
 
 ## References
 
-- [`.github/governance-map.md`](../../.github/governance-map.md) — Repository governance and folder responsibilities
-- [`README.md`](../../README.md) — Repository model
-- [`docs/REPOSITORY-SURFACES.md`](../../docs/REPOSITORY-SURFACES.md) — Surface area map
+- [`.github/governance-map.md`](.github/governance-map.md) — Repository governance and folder responsibilities
+- [`README.md`](README.md) — Repository model
+- [`docs/REPOSITORY-SURFACES.md`](docs/REPOSITORY-SURFACES.md) — Surface area map
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/code-guidelines-agent.agent.md b/.github/agents/code-guidelines-agent.agent.md
@@ -309,16 +309,16 @@ output:
 
 ## References
 
-- [`.github/instructions/paradigm-priority.instructions.md`](../../.github/instructions/paradigm-priority.instructions.md) — Paradigm selection rules
-- [`.github/instructions/pattern-reasoning.instructions.md`](../../.github/instructions/pattern-reasoning.instructions.md) — Pattern reasoning
-- [`.github/instructions/refactoring-techniques.instructions.md`](../../.github/instructions/refactoring-techniques.instructions.md) — Refactoring techniques
+- [`.github/instructions/paradigm-priority.instructions.md`](.github/instructions/paradigm-priority.instructions.md) — Paradigm selection rules
+- [`.github/instructions/pattern-reasoning.instructions.md`](.github/instructions/pattern-reasoning.instructions.md) — Pattern reasoning
+- [`.github/instructions/refactoring-techniques.instructions.md`](.github/instructions/refactoring-techniques.instructions.md) — Refactoring techniques
 - [OWASP Top 10](https://owasp.org/www-project-top-ten/)
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/competitive-intelligence-agent.agent.md b/.github/agents/competitive-intelligence-agent.agent.md
@@ -154,20 +154,20 @@ flowchart TD
 
 ## Data Ownership
 
-- **Canonical output path**: `myself/business/competitive-intelligence/`
+- **Canonical output path**: `myself/business/competitive-intelligence/` (when this path exists in the workspace)
 - **Scope boundary**: Business competitive intelligence only — publishing competition belongs to CompetitiveAnalyzer; market trend data for books belongs to MarketAnalyzer
 
 ## References
 
-- [`myself/knowledge/`](../../myself/knowledge/) — Domain expertise
+- `myself/knowledge/` — Domain expertise (if available in workspace)
 - [Crayon Competitive Intelligence](https://www.crayon.co/blog) — CI best practices
 - [SCIP Framework](https://www.scip.org/) — Strategic and competitive intelligence
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/data/team-mapping.md b/.github/agents/data/team-mapping.md
@@ -8,6 +8,8 @@ Canonical shared-agent registry generated from enabled agent families in `repos/
 - Canonical source metadata: enabled shared agent families in `repos/asset-map.yaml`
 - Generated mirrors: `.github/instructions/team-mapping.instructions.md` and managed delegation blocks in `.github/copilot-instructions.md`
 
+## Shared Agents
+
 | Agent Name | File |
 | --- | --- |
 | `azure-aks` | `.github/agents/azure-aks.agent.md` |
@@ -29,7 +31,6 @@ Canonical shared-agent registry generated from enabled agent families in `repos/
 | `pr-evaluator` | `.github/agents/pr-evaluator.agent.md` |
 | `process-management-agent` | `.github/agents/process-management-agent.agent.md` |
 | `python-specialist` | `.github/agents/python-specialist.agent.md` |
-| `report-generator` | `.github/agents/report-generator.agent.md` |
 | `risk-analysis-agent` | `.github/agents/risk-analysis-agent.agent.md` |
 | `rust-specialist` | `.github/agents/rust-specialist.agent.md` |
 | `system-architect` | `.github/agents/system-architect.agent.md` |

diff --git a/.github/agents/enterprise-connectors.agent.md b/.github/agents/enterprise-connectors.agent.md
@@ -25,6 +25,10 @@ You are an **enterprise integration engineer** specialized in building **REST/Gr
 
 Before generating plans, recommendations, or implementation guidance, you MUST first consult the highest-authority documentation for this domain (official product docs/specs/standards and repository canonical governance sources). If documentation is unavailable or ambiguous, state assumptions explicitly and request missing evidence before proceeding.
 
+### MCP Runtime Scope
+
+When MCP servers have been published by `scripts/sync-agents.ps1`, treat them as user-scoped capabilities that are available from any repository on the same machine. Still resolve files, governance, manifests, and private/public eligibility from the active repository before implementing or wiring connector behavior.
+
 ## Core Principles
 ### 1. Connector Architecture
 
@@ -150,15 +154,15 @@ When working inside a repository that has connector specifications in `.github/a
 
 ## References
 
-- [`config/mcp/`](../../config/mcp/) — MCP configuration
-- [`config/mcp/README.md`](../../config/mcp/README.md) — MCP architecture guide
-- [`scripts/mcp-servers/`](../../scripts/mcp-servers/) — MCP server implementations
+- [`config/mcp/`](config/mcp/) — MCP configuration
+- [`config/mcp/README.md`](config/mcp/README.md) — MCP architecture guide
+- [`scripts/mcp-servers/`](scripts/mcp-servers/) — MCP server implementations
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.
 

diff --git a/.github/agents/financial-modeling-agent.agent.md b/.github/agents/financial-modeling-agent.agent.md
@@ -148,20 +148,20 @@ flowchart TD
 
 ## Data Ownership
 
-- **Canonical output path**: `myself/business/financial-models/`
+- **Canonical output path**: `myself/business/financial-models/` (when this path exists in the workspace)
 - **Scope boundary**: Business financial modeling only — personal income/royalty tracking belongs to FinanceTracker
 
 ## References
 
-- [`myself/knowledge/`](../../myself/knowledge/) — Economics and finance expertise
+- `myself/knowledge/` — Economics and finance expertise (if available in workspace)
 - [Damodaran Online](https://pages.stern.nyu.edu/~adamodar/) — Valuation resources
 - [McKinsey Valuation](https://www.mckinsey.com/business-functions/strategy-and-corporate-finance/our-insights/valuation) — Corporate finance
 
 ---
 
 ## Agent Ecosystem
 
-> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](../../.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
+> **Dynamic discovery**: Consult [`.github/agents/data/team-mapping.md`](.github/agents/data/team-mapping.md) when available; if it is absent, continue with available workspace agents/tools and do not hard-fail.
 >
 > Use `#runSubagent` with the agent name to invoke any specialist. The registry is the single source of truth for which agents exist and what they handle.