@raishin/vanguard-frontier-agentic 2.8.0 → 2.10.0

package/.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
-    "version": "2.7.1"
+    "version": "2.9.0"
   },
   "plugins": [
     {
       "name": "vanguard-frontier-agentic",
       "source": "./",
-      "description": "All 448 cloud, security, compliance, platform, accounting, and finance agents in one install. Includes maestros, advisory reviewers, and live-mutation guards across 34 providers.",
+      "description": "All 473 cloud, security, compliance, platform, accounting, and finance agents in one install. Includes maestros, advisory reviewers, and live-mutation guards across 35 providers.",
       "category": "cloud",
       "tags": [
         "agents",

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vanguard-frontier-agentic",
-  "version": "2.7.1",
+  "version": "2.9.0",
   "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
   "author": {
     "name": "Raishin",
@@ -367,6 +367,31 @@
     "./agents/marketing/marketing-pixel-data-leakage-review-agent/harnesses/claude-code.agent.md",
     "./agents/marketing/martech-access-governance-review-agent/harnesses/claude-code.agent.md",
     "./agents/marketing/programmatic-supply-chain-integrity-review-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-administrator-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-ai-connector-mcp-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-ai-foundations-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-application-developer-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-audit-controls-sox-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-bi-reporting-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-data-governance-privacy-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-enterprise-architecture-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-erp-consultant-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-evidence-release-drift-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-financial-foundations-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-identity-access-role-permission-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-integration-migration-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-live-org-mutation-guard-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-maestro-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-oneworld-multisubsidiary-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-sandbox-nonproduction-governance-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-saved-searches-workbook-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-sdf-devops-release-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-sso-oauth-tba-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-suitecloud-developer-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-suiteflow-automation-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-suitefoundation-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-suitescript-secure-code-review-agent/harnesses/claude-code.agent.md",
+    "./agents/netsuite/netsuite-web-services-integration-agent/harnesses/claude-code.agent.md",
     "./agents/nvidia/nvidia-agentic-ai-platform-review-agent/harnesses/claude-code.agent.md",
     "./agents/nvidia/nvidia-ai-infrastructure-operations-agent/harnesses/claude-code.agent.md",
     "./agents/nvidia/nvidia-ai-networking-fabric-review-agent/harnesses/claude-code.agent.md",

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vanguard-frontier-agentic",
-  "version": "2.7.1",
+  "version": "2.9.0",
   "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
   "author": {
     "name": "Raishin",
@@ -366,6 +366,31 @@
     "./agents/marketing/marketing-pixel-data-leakage-review-agent/harnesses/cursor.agent.md",
     "./agents/marketing/martech-access-governance-review-agent/harnesses/cursor.agent.md",
     "./agents/marketing/programmatic-supply-chain-integrity-review-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-administrator-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-ai-connector-mcp-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-ai-foundations-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-application-developer-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-audit-controls-sox-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-bi-reporting-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-data-governance-privacy-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-enterprise-architecture-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-erp-consultant-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-evidence-release-drift-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-financial-foundations-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-identity-access-role-permission-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-integration-migration-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-live-org-mutation-guard-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-maestro-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-oneworld-multisubsidiary-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-sandbox-nonproduction-governance-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-saved-searches-workbook-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-sdf-devops-release-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-sso-oauth-tba-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-suitecloud-developer-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-suiteflow-automation-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-suitefoundation-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-suitescript-secure-code-review-agent/harnesses/cursor.agent.md",
+    "./agents/netsuite/netsuite-web-services-integration-agent/harnesses/cursor.agent.md",
     "./agents/nvidia/nvidia-agentic-ai-platform-review-agent/harnesses/cursor.agent.md",
     "./agents/nvidia/nvidia-ai-infrastructure-operations-agent/harnesses/cursor.agent.md",
     "./agents/nvidia/nvidia-ai-networking-fabric-review-agent/harnesses/cursor.agent.md",

package/.github/plugin/marketplace.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://raw.githubusercontent.com/github/copilot-cli/main/schemas/marketplace.schema.json",
   "name": "vanguard-frontier-agentic",
-  "description": "Curated marketplace for cloud and zero-trust AI workflows. 331 agents, 286 skills, and rules across AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud, Kubernetes, and Terraform.",
-  "version": "2.8.0",
+  "description": "Curated marketplace for cloud, zero-trust, and compliance-aware AI workflows — agents, skills, and rules spanning cloud, security, ERP, and platform providers.",
+  "version": "2.10.0",
   "owner": {
     "name": "Raishin",
     "url": "https://github.com/Raishin"
@@ -11,7 +11,7 @@
     {
       "id": "vanguard-frontier-agentic",
       "source": "./",
-      "description": "All 331 cloud, security, compliance, and platform agents in one install. Includes provider maestros (routing agents) and live-mutation guards. Requires approval-gated, target-confirmed mutations on real cloud environments."
+      "description": "All cloud, security, compliance, and platform agents in one install. Includes provider maestros (routing agents) and live-mutation guards. Requires approval-gated, target-confirmed mutations on real cloud environments."
     }
   ]
 }

package/README.md

@@ -44,7 +44,8 @@ This is the **edge of agentic intelligence** — an enterprise-grade ecosystem f
 running AI agents at scale in environments where a wrong move is a board-level
 incident. It collects reusable **skills**, **agents**, **rules**, **MCP references**,
 and supporting assets for AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud,
-Kubernetes, and Terraform — plus a **cross-functional Legal + HR agentic ecosystem**.
+Kubernetes, and Terraform — plus cross-functional **Legal, HR, Marketing, Salesforce,
+.NET, FinOps, Accounting, Finance, and Oracle NetSuite ERP** agentic ecosystems.
 
 This is **not** just cloud infrastructure tooling. It is **agentic coordination**:
 maestro routing, escalation-aware protocol, structured handoff between specialists,
@@ -57,10 +58,10 @@ operates in. Coordination, governance, and escalation are the product.
 <!-- Generated by scripts/generate-readme-counts.mjs — do not edit by hand. Run: npm run readme-counts:write -->
 | Catalog | Count |
 | --- | --- |
-| Skills | 426 |
-| Agents | 448 |
-| Providers | 34 |
-| Install roles | 22 |
+| Skills | 451 |
+| Agents | 473 |
+| Providers | 35 |
+| Install roles | 23 |
 | Rules | 1 |
 | MCP references | 3 |
 <!-- readme-counts:end -->
@@ -186,9 +187,9 @@ Or wire it into `~/.claude/settings.json` (or your project's `.claude/settings.j
 }
 ```
 
-Pin to a tag for reproducible installs: `Raishin/vanguard-frontier-agentic@v2.3.0` (or pick any [released tag](https://github.com/Raishin/vanguard-frontier-agentic/releases)).
+Pin to a tag for reproducible installs: pick any [released tag](https://github.com/Raishin/vanguard-frontier-agentic/releases) for stable versions, or use `@latest` for the current release.
 
-- **Bundled:** all <!-- count:agents -->448<!-- /count --> cloud, security, compliance, Kubernetes, Terraform agents (incl. provider maestros and live-guard agents)
+- **Bundled:** all <!-- count:agents -->473<!-- /count --> cloud, security, compliance, Kubernetes, Terraform agents (incl. provider maestros and live-guard agents)
 - **Spec:** [`.claude-plugin/marketplace.json`](.claude-plugin/marketplace.json) + [`.claude-plugin/plugin.json`](.claude-plugin/plugin.json) (canonical Claude Code plugin layout)
 - **Not bundled:** skills, rules, MCP references — use the npm path for those
 - **Docs:** [code.claude.com/docs/en/plugin-marketplaces](https://code.claude.com/docs/en/plugin-marketplaces)
@@ -218,7 +219,7 @@ Or in `.github/copilot/settings.json` for repo-wide trust:
 
 - **Marketplace manifest:** [`.github/plugin/marketplace.json`](.github/plugin/marketplace.json) declares this repo as a single-plugin marketplace
 - **Source path:** `./` (the repo root is the plugin root)
-- **Bundled:** <!-- count:agents -->448<!-- /count --> Copilot agent adapters under `agents/<provider>/<agent>/harnesses/copilot.agent.md`
+- **Bundled:** <!-- count:agents -->473<!-- /count --> Copilot agent adapters under `agents/<provider>/<agent>/harnesses/copilot.agent.md`
 - **Docs:** [github.com/github/copilot-cli](https://github.com/github/copilot-cli) (`/plugin marketplace add`)
 
 </details>
@@ -239,7 +240,7 @@ In Cursor: **Settings → Plugins → Add Plugin Directory** → pick the cloned
 vscode.cursor.plugins.registerPath("/absolute/path/to/vanguard-frontier-agentic");
 ```
 
-- **Plugin manifest:** [`.cursor-plugin/plugin.json`](.cursor-plugin/plugin.json) enumerates all **<!-- count:agents -->448<!-- /count --> Cursor agent adapters** explicitly via the `agents` field
+- **Plugin manifest:** [`.cursor-plugin/plugin.json`](.cursor-plugin/plugin.json) enumerates all **<!-- count:agents -->473<!-- /count --> Cursor agent adapters** explicitly via the `agents` field
 - **Bundled:** all agents from `agents/<provider>/<agent>/harnesses/cursor.agent.md`
 - **Rules:** existing `rules/` directory at repo root is auto-discovered by Cursor
 - **Docs:** [cursor.com/docs/plugins](https://cursor.com/docs/plugins) · [cursor.com/docs/reference/plugins](https://cursor.com/docs/reference/plugins)
@@ -247,11 +248,11 @@ vscode.cursor.plugins.registerPath("/absolute/path/to/vanguard-frontier-agentic"
 </details>
 
 <details>
-<summary><strong>🔮 Kiro (Powers + agents)</strong> &nbsp;—&nbsp; <em>14 ready-to-add Powers</em></summary>
+<summary><strong>🔮 Kiro (Powers + agents)</strong> &nbsp;—&nbsp; <em>35 ready-to-add Powers</em></summary>
 
 <br>
 
-Kiro Powers UI is per-Power directory add — there is no single-command marketplace flow. This repo ships **14 Powers** under `powers/`, one per provider, so Kiro users can add only what they need.
+Kiro Powers UI is per-Power directory add — there is no single-command marketplace flow. This repo ships **35 Powers** under `powers/`, one per provider, so Kiro users can add only what they need.
 
 ```bash
 # 1. Clone this repo
@@ -266,7 +267,7 @@ cd vanguard-frontier-agentic
 #       /absolute/path/to/vanguard-frontier-agentic/powers/vanguard-terraform
 ```
 
-- **Powers available:** `vanguard-aws`, `vanguard-azure`, `vanguard-gcp`, `vanguard-oci`, `vanguard-alibaba`, `vanguard-huawei`, `vanguard-ovhcloud`, `vanguard-scaleway`, `vanguard-hetzner`, `vanguard-contabo`, `vanguard-ionos`, `vanguard-kubernetes`, `vanguard-terraform`, `vanguard-nvidia`
+- **Powers available:** `vanguard-accounting`, `vanguard-alibaba`, `vanguard-argocd`, `vanguard-aws`, `vanguard-azure`, `vanguard-backstage`, `vanguard-cert-manager`, `vanguard-cilium`, `vanguard-contabo`, `vanguard-dotnet`, `vanguard-falco`, `vanguard-finance`, `vanguard-fluxcd`, `vanguard-gcp`, `vanguard-generic`, `vanguard-hetzner`, `vanguard-hr`, `vanguard-huawei`, `vanguard-ionos`, `vanguard-istio`, `vanguard-kubernetes`, `vanguard-kyverno`, `vanguard-legal`, `vanguard-marketing`, `vanguard-multi-cloud`, `vanguard-netsuite`, `vanguard-nvidia`, `vanguard-oci`, `vanguard-opentelemetry`, `vanguard-ovhcloud`, `vanguard-prometheus`, `vanguard-salesforce`, `vanguard-scaleway`, `vanguard-sigstore`, `vanguard-terraform`
 - **Each Power ships:** routing pattern (maestro entry), live-mutation discipline, provider invariants (account-ID/region, MLPS 2.0, EU sovereignty, etc.)
 - **Frontmatter:** strict-5 fields (`name`, `displayName`, `description`, `keywords`, `author`) per Kiro spec
 - **For Kiro agent adapter files** (`.kiro/agents/*.md`, `.kiro/agents/*.json`): use the npm-export path below
@@ -330,7 +331,7 @@ enabled = true
 - **Bundled plugins:**
   - `vanguard-frontier-agentic` — the main plugin, manifest at [`plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json`](plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json)
   - `cross-platform-agent-template` — scaffold for new cross-platform agents
-- **For agent adapter files** (`.codex/agents/*.toml`): after enabling the plugin, run `npx vfa-export-agents --platform codex --all --repo .` to write the <!-- count:agents -->448<!-- /count --> agent adapters into your repo
+- **For agent adapter files** (`.codex/agents/*.toml`): after enabling the plugin, run `npx vfa-export-agents --platform codex --all --repo .` to write the <!-- count:agents -->473<!-- /count --> agent adapters into your repo
 - **Other commands:** `codex plugin marketplace upgrade vanguard-frontier-agentic`, `codex plugin marketplace remove vanguard-frontier-agentic`
 - **Docs:** [github.com/openai/codex](https://github.com/openai/codex) · [Codex plugin spec](https://github.com/openai/codex/blob/main/codex-rs/skills/src/assets/samples/plugin-creator/references/plugin-json-spec.md)
 
@@ -372,7 +373,7 @@ npm install @raishin/vanguard-frontier-agentic@latest
 
 ## 🧠 Skills
 
-**<!-- count:skills -->426<!-- /count --> skills** across AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud, Kubernetes, CNCF ecosystem, Terraform, marketing governance, and more.
+**<!-- count:skills -->451<!-- /count --> skills** across AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud, Kubernetes, CNCF ecosystem, Terraform, marketing governance, and more.
 
 | Domain             | Count | What they cover                                                                                   |
 | ------------------ | ----: | ------------------------------------------------------------------------------------------------- |
@@ -469,7 +470,7 @@ Rule of thumb: if the asset teaches **how to do a repeatable task**, it is a ski
 
 ## 🤖 Agents
 
-**<!-- count:agents -->448<!-- /count --> agents** matching the skill catalog — agents ship harness adapters and a hardened permission model.
+**<!-- count:agents -->473<!-- /count --> agents** matching the skill catalog — agents ship harness adapters and a hardened permission model.
 
 | Provider           | Count | Specialisations                                                                     |
 | ------------------ | ----: | ----------------------------------------------------------------------------------- |
@@ -526,6 +527,7 @@ Every agent ships:
 
 ```text
 agents/
+├── accounting/       (14 agents — maestro + corporate accounting specialists: revenue recognition (ASC 606/IFRS 15), close cycle, consolidation/intercompany, fixed assets, lease accounting (ASC 842), hedge accounting, FX translation, tax provision, payroll, procure-to-pay, equity compensation, indirect tax/e-invoicing, business combinations — all advisory, no ledger writes)
 ├── alibaba/          (43 agents — advisory, live-guard operators, maestro)
 ├── argocd/           (2 agents — GitOps review, live sync guard)
 ├── aws/              (47 agents — advisory, execution, live-guard operators)
@@ -536,6 +538,7 @@ agents/
 ├── contabo/          (6 agents — advisory, live instance + storage guards, maestro)
 ├── dotnet/           (10 agents — C#/runtime, ASP.NET Core, EF Core, testing, NuGet supply chain, performance/AOT, OpenTelemetry, Aspire — maestro + 9 specialists)
 ├── falco/            (1 agent — runtime threat detection review)
+├── finance/          (8 agents — maestro + corporate finance specialists: variance analysis, FP&A forecasting, treasury/liquidity, working capital, debt/capital structure, capital allocation, transfer pricing/Pillar Two — all advisory, no ERP writes)
 ├── finops/           (4 agents — cross-cloud price advisor + experimental cost/economics agents)
 ├── fluxcd/           (1 agent — GitOps Kustomization/HelmRelease review)
 ├── gcp/              (51 agents — advisory, live-guard operators, maestro)
@@ -548,6 +551,7 @@ agents/
 ├── kyverno/          (1 agent — admission policy review)
 ├── legal/            (13 agents — contract review, employment law, privacy & data protection, regulatory compliance, IP & open source, litigation hold, ethics & investigations, vendor risk, policy governance, public disclosure, counsel review, knowledge management)
 ├── marketing/        (14 agents — 13 governance review agents + maestro router)
+├── netsuite/         (25 agents — Oracle NetSuite ERP — maestro router, live-org mutation guard, evidence/release-drift + enterprise-architecture + SOX audit governance, plus 20 domain specialists: financial foundations, SuiteScript secure code review, SDF DevOps, OneWorld multi-subsidiary, identity/RBAC, OAuth/TBA/SSO, AI Connector/MCP, data governance, integration migration, and more — all static-review tier)
 ├── nvidia/           (12 agents — GPU infrastructure, TensorRT/TensorRT-LLM, Triton serving, NeMo/NIM, agentic AI, NGC supply chain, AI networking, day-2 ops, GPU Operator on Kubernetes, model promotion gatekeeper — maestro + advisory + live-runtime gate)
 ├── oci/              (39 agents — advisory, live-guard operators)
 ├── opentelemetry/    (1 agent — collector config review)
@@ -1109,7 +1113,7 @@ In two weeks on npm: ~900 downloads. Socket.dev scores: Vulnerability 100, Quali
 
 Your sponsorship directly funds the compute, API time, and research hours that turn new cloud providers, compliance frameworks, and security patterns into production-ready agents — free for everyone.
 
-Current catalog: **<!-- count:agents -->448<!-- /count --> agents · <!-- count:skills -->426<!-- /count --> skills · <!-- count:providers -->34<!-- /count --> cloud/platform providers**
+Current catalog: **<!-- count:agents -->473<!-- /count --> agents · <!-- count:skills -->451<!-- /count --> skills · <!-- count:providers -->35<!-- /count --> cloud/platform providers**
 
 ---
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/AGENT.md

@@ -1,12 +1,12 @@
 ---
 metadata:
   author: "github: Raishin"
-  version: "0.2.0"
+  version: "0.2.2"
 ---
 
 # Azure AI Foundry Ops Governor
 
-> Agent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+> Agent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Harness Variants
 
@@ -32,20 +32,28 @@ Before answering, read and follow:
 
 Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only when the task needs that reference. Do not dump reference text into the response.
 
+## Reference Pack
+
+Use agent-local references for current grounding and output discipline:
+
+- `references/ai-foundry-ops-agent-operations.md`
+- `references/official-sources.md`
+- `references/safety-checklist.md`
+- `references/workflow-and-output.md`
+- `references/mcp-and-evidence.md`
+
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/claude-code.agent.md

@@ -1,6 +1,6 @@
 ---
 name: "Azure AI Foundry Ops Governor"
-description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 ---
 
 # Azure AI Foundry Ops Governor
@@ -17,18 +17,16 @@ Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only w
 
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/codex.toml

@@ -1,10 +1,10 @@
 name = "azure_ai_foundry_ops_governor"
-description = "Specialized subagent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description = "Specialized subagent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 model = "gpt-5.4"
 model_reasoning_effort = "high"
 sandbox_mode = "read-only"
 
-developer_instructions = "Load and follow the bound `azure-ai-foundry-ops-governor` skill first. This agent exists only for that Azure role; do not drift into generic cloud advice.\n\nToken discipline:\n- Read only SKILL.md first; load references only when the task requires them.\n- Keep answers compact: verdict, evidence level, blockers, safe next actions, open questions.\n- Do not paste long docs, raw tool inventories, or command help unless requested.\n\nRole focus: Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.\n\nSafety contract:\n- Prefer runtime-exposed Azure MCP tools as truth; do not invent namespaces or tools from documentation alone.\n- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.\n- When Azure MCP setup is in scope, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.\n- Never ask for secrets, credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, or customer identifiers unless already sanitized and required.\n- Label facts as live evidence, sanitized evidence, documentation-based, or inference.\n- Use read-only discovery first and require explicit approval before mutation or secret-bearing actions.\n"
+developer_instructions = "Load and follow the bound `azure-ai-foundry-ops-governor` skill first. This agent exists only for that Azure role; do not drift into generic cloud advice.\n\nToken discipline:\n- Read only SKILL.md first; load references only when the task requires them.\n- Keep answers compact: verdict, evidence level, blockers, safe next actions, open questions.\n- Do not paste long docs, raw tool inventories, or command help unless requested.\n\nRole focus: Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.\n\nSafety contract:\n- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.\n- Use read-only configured-environment evidence only when available and label it as sampled evidence.\n- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.\n- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.\n- State what is unknown; documentation proves service behavior, not the user's deployed state.\n- Label facts as sampled configured-environment evidence, sanitized evidence, documentation-based, or inference.\n- Use read-only discovery first and require explicit approval before mutation or secret-bearing actions.\n"
 
 [[skills.config]]
 path = "skills/azure/azure-ai-foundry-ops-governor/SKILL.md"

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/copilot.agent.md

@@ -1,5 +1,5 @@
 ---
-description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 name: "Azure AI Foundry Ops Governor"
 tools:
   - "read"
@@ -30,18 +30,16 @@ Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only w
 
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/cursor.agent.md

@@ -1,6 +1,6 @@
 ---
 name: "Azure AI Foundry Ops Governor"
-description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 model: "inherit"
 readonly: true
 ---
@@ -19,18 +19,16 @@ Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only w
 
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/gemini.agent.md

@@ -1,6 +1,6 @@
 ---
 name: "Azure AI Foundry Ops Governor"
-description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 kind: "local"
 ---
 
@@ -18,18 +18,16 @@ Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only w
 
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/kiro-cli.agent.json

@@ -1,5 +1,5 @@
 {
   "name": "Azure AI Foundry Ops Governor",
   "description": "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.",
-  "prompt": "# Azure AI Foundry Ops Governor\n\nUse this agent only for `azure-ai-foundry-ops-governor` work.\n\n## Required Skill\n\nBefore answering, read and follow:\n\n- `skills/azure/azure-ai-foundry-ops-governor/SKILL.md`\n\nLoad files under `skills/azure/azure-ai-foundry-ops-governor/references/` only when the task needs that reference. Do not dump reference text into the response.\n\n## Focus\n\nGovern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.\n\n## Operating Rules\n\n- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.\n- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.\n- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.\n- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.\n- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.\n- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.\n- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.\n- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.\n\n## Response Shape\n\n1. Verdict\n2. Evidence level\n3. Blockers / risks\n4. Safe next actions\n5. Open questions"
+  "prompt": "# Azure AI Foundry Ops Governor\n\nUse this agent only for `azure-ai-foundry-ops-governor` work.\n\n## Required Skill\n\nBefore answering, read and follow:\n\n- `skills/azure/azure-ai-foundry-ops-governor/SKILL.md`\n\nLoad files under `skills/azure/azure-ai-foundry-ops-governor/references/` only when the task needs that reference. Do not dump reference text into the response.\n\n## Focus\n\nGovern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.\n\n## Operating Rules\n\n- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.\n- Use read-only configured-environment evidence only when available and label it as sampled evidence.\n- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.\n- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.\n- State what is unknown; documentation proves service behavior, not the user's deployed state.\n- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.\n\n## Response Shape\n\n1. Verdict\n2. Evidence level\n3. Blockers / risks\n4. Safe next actions\n5. Open questions"
 }

package/agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/kiro-ide.agent.md

@@ -1,6 +1,6 @@
 ---
 name: "Azure AI Foundry Ops Governor"
-description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution."
+description: "Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution."
 ---
 
 # Azure AI Foundry Ops Governor
@@ -17,18 +17,16 @@ Load files under `skills/azure/azure-ai-foundry-ops-governor/references/` only w
 
 ## Focus
 
-Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.
+Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.
 
 ## Operating Rules
 
-- Prefer live Azure MCP capability evidence when the active client exposes it; otherwise use official Microsoft documentation and sanitized user evidence.
-- Treat the runtime-exposed Azure MCP tool inventory as truth. Do not assume a namespace or tool exists just because Microsoft documents it.
-- If Azure MCP exposure is unclear, inspect or ask for the available tool inventory before making namespace-specific claims.
-- When Azure MCP setup is part of the task, note that Microsoft recommends consolidated mode for AI agents, but adapt to the tools actually exposed in the active client.
-- Never ask for secrets, credentials, access tokens, client secrets, connection strings, tenant IDs, subscription IDs, certificates, or customer-specific identifiers unless already sanitized and required.
-- Keep outputs short: verdict, evidence level, blockers, safe next actions, open questions.
-- Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`.
-- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure namespace assumptions.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for Azure service behavior.
+- Use read-only configured-environment evidence only when available and label it as sampled evidence.
+- Never ask for credentials, tokens, tenant IDs, subscription IDs, connection strings, certificates, private keys, or customer data.
+- Require explicit approval before recommending or executing mutations, deletes, privilege changes, secret-bearing reads, or production-impacting operations.
+- State what is unknown; documentation proves service behavior, not the user's deployed state.
+- Challenge vague scope, broad privileges, destructive shortcuts, undocumented production claims, and unsupported Azure service assumptions.
 
 ## Response Shape
 

package/agents/azure/azure-ai-foundry-ops-governor-agent/metadata.json

@@ -11,24 +11,16 @@
     "gemini",
     "kiro"
   ],
-  "summary": "Agent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe MCP-backed execution.",
+  "summary": "Agent for azure-ai-foundry-ops-governor. Govern Microsoft Foundry and Azure AI Foundry operations across resource-versus-project boundaries, RBAC, quotas, network isolation, logging, and safe documentation- and API-evidence-backed execution.",
   "source_type": "adapted",
   "official_docs": [
-    "https://learn.microsoft.com/en-us/azure/foundry/concepts/architecture",
-    "https://learn.microsoft.com/en-us/azure/foundry/concepts/rbac-foundry",
-    "https://learn.microsoft.com/en-us/azure/foundry/concepts/planning",
-    "https://learn.microsoft.com/en-us/azure/foundry/mcp/security-best-practices?view=foundry",
-    "https://learn.microsoft.com/en-us/azure/foundry/how-to/configure-private-link",
-    "https://learn.microsoft.com/en-us/azure/foundry/how-to/managed-virtual-network",
-    "https://learn.microsoft.com/en-us/azure/foundry/how-to/quota",
-    "https://learn.microsoft.com/en-us/azure/foundry/foundry-models/quotas-limits",
-    "https://learn.microsoft.com/en-us/azure/foundry/foundry-models/how-to/monitor-models",
-    "https://learn.microsoft.com/en-us/azure/developer/azure-mcp-server/tools/",
-    "https://learn.microsoft.com/en-us/azure/developer/azure-mcp-server/overview",
-    "https://learn.microsoft.com/en-us/azure/developer/azure-mcp-server/concepts"
+    "https://learn.microsoft.com/azure/foundry/what-is-foundry",
+    "https://learn.microsoft.com/azure/foundry/concepts/architecture",
+    "https://learn.microsoft.com/azure/foundry/how-to/configure-private-link",
+    "https://learn.microsoft.com/azure/foundry/how-to/managed-virtual-network"
   ],
-  "security_notes": "Keep Foundry resource governance separate from project developer isolation, prefer Entra ID over key-based auth, verify quota and diagnostics before rollout, and treat MCP mutations as higher risk than read-only discovery, especially because hosted Foundry MCP security guidance documents preview and public-endpoint limitations. Prefer read-only discovery first and explicit approval before mutations or secret-bearing operations.",
-  "last_verified": "2026-04-28",
+  "security_notes": "Use official Microsoft Learn documentation for documented behavior and sampled read-only configured-environment evidence for observed state. Enforce least privilege, credential boundaries, evidence labels, and explicit approval before production-impacting or secret-bearing operations.",
+  "last_verified": "2026-06-06",
   "path": "agents/azure/azure-ai-foundry-ops-governor-agent",
   "harness_variants": {
     "codex": "agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/codex.toml",
@@ -40,5 +32,5 @@
     "kiro-cli": "agents/azure/azure-ai-foundry-ops-governor-agent/harnesses/kiro-cli.agent.json"
   },
   "author": "github: Raishin",
-  "version": "0.2.0"
+  "version": "0.2.2"
 }