@raishin/vanguard-frontier-agentic 2.9.0 → 2.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raishin/vanguard-frontier-agentic",
-  "version": "2.9.0",
+  "version": "2.10.0",
   "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
   "license": "Apache-2.0",
   "repository": {

package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vanguard-frontier-agentic",
-  "version": "2.9.0",
+  "version": "2.10.0",
   "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.",
   "author": {
     "name": "Raishin",

package/powers/README.md

@@ -1,6 +1,6 @@
 # `powers/` — Kiro Powers
 
-This directory holds **34 Kiro Powers** for `vanguard-frontier-agentic`, one
+This directory holds **35 Kiro Powers** for `vanguard-frontier-agentic`, one
 per cloud/platform/IaC provider. Each Power is a directory containing a
 `POWER.md` file with strict-5 frontmatter and steering content.
 
@@ -33,6 +33,7 @@ powers/
 ├── vanguard-legal/POWER.md
 ├── vanguard-marketing/POWER.md
 ├── vanguard-multi-cloud/POWER.md
+├── vanguard-netsuite/POWER.md
 ├── vanguard-nvidia/POWER.md
 ├── vanguard-oci/POWER.md
 ├── vanguard-opentelemetry/POWER.md
@@ -78,7 +79,7 @@ cd vanguard-frontier-agentic
 ## How to update
 
 ```bash
-# Regenerate the 34 Powers from catalog/agents.json + per-provider config:
+# Regenerate the 35 Powers from catalog/agents.json + per-provider config:
 npm run kiro-powers:write
 
 # Then verify everything is in sync:

package/powers/vanguard-accounting/POWER.md

@@ -1,13 +1,13 @@
 ---
 name: "vanguard-accounting"
 displayName: "Vanguard Frontier — Accounting"
-description: "Curated Accounting agents for accounting revenue recognition advisor, accounting close cycle advisor, accounting tax provision advisor, accounting lease accounting advisor. Routes via accounting-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
+description: "Curated Accounting agents for accounting business combinations advisor, accounting close cycle advisor, accounting consolidation intercompany advisor, accounting equity compensation advisor. Routes via accounting-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
 keywords: ["accounting", "static-review", "configuration-audit", "best-practices"]
 author: "Raishin"
 ---
 # Vanguard Frontier — Accounting
 
-Curated Accounting agents for accounting revenue recognition advisor, accounting close cycle advisor, accounting tax provision advisor, accounting lease accounting advisor. Routes via accounting-maestro-agent to specialist agents based on task scope. Static review only; no live mutations.
+Curated Accounting agents for accounting business combinations advisor, accounting close cycle advisor, accounting consolidation intercompany advisor, accounting equity compensation advisor. Routes via accounting-maestro-agent to specialist agents based on task scope. Static review only; no live mutations.
 
 ## When to engage this Power
 

package/powers/vanguard-finance/POWER.md

@@ -1,13 +1,13 @@
 ---
 name: "vanguard-finance"
 displayName: "Vanguard Frontier — Finance"
-description: "Curated Finance agents for finance variance analysis advisor, finance treasury liquidity advisor, finance capital allocation advisor, finance transfer pricing pillar two advisor. Routes via finance-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
+description: "Curated Finance agents for finance capital allocation advisor, finance debt capital structure advisor, finance fpa forecasting advisor, finance transfer pricing pillar two advisor. Routes via finance-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
 keywords: ["finance", "static-review", "configuration-audit", "best-practices"]
 author: "Raishin"
 ---
 # Vanguard Frontier — Finance
 
-Curated Finance agents for finance variance analysis advisor, finance treasury liquidity advisor, finance capital allocation advisor, finance transfer pricing pillar two advisor. Routes via finance-maestro-agent to specialist agents based on task scope. Static review only; no live mutations.
+Curated Finance agents for finance capital allocation advisor, finance debt capital structure advisor, finance fpa forecasting advisor, finance transfer pricing pillar two advisor. Routes via finance-maestro-agent to specialist agents based on task scope. Static review only; no live mutations.
 
 ## When to engage this Power
 

package/powers/vanguard-netsuite/POWER.md

@@ -0,0 +1,41 @@
+---
+name: "vanguard-netsuite"
+displayName: "Vanguard Frontier — Netsuite"
+description: "Curated Netsuite agents for netsuite administrator, netsuite ai connector mcp, netsuite ai foundations, netsuite application developer. Routes via netsuite-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
+keywords: ["netsuite", "static-review", "configuration-audit", "best-practices"]
+author: "Raishin"
+---
+# Vanguard Frontier — Netsuite
+
+Curated Netsuite agents for netsuite administrator, netsuite ai connector mcp, netsuite ai foundations, netsuite application developer. Routes via netsuite-maestro-agent to specialist agents based on task scope. Static review only; no live mutations.
+
+## When to engage this Power
+
+Activate when the task references Netsuite services, resources, or operations. Do not activate on unrelated requests — narrow keyword matching is required to avoid false activations (Kiro Powers convention).
+
+## Routing pattern
+
+- **`netsuite-maestro-agent`** — classifies and routes the task to the right specialist
+
+Use the maestro as the entry point: classify the task, then dispatch to one specialist or a parallel team of specialists. Never have the maestro itself execute a live mutation.
+
+## Live-guard agents (gate_mode only)
+
+- `netsuite-live-org-mutation-guard-agent` — never auto-dispatched; gate_mode only
+
+Live-guard agents enforce approval, target confirmation, evidence capture, and rollback plans before executing a mutation. They are never auto-dispatched — the maestro must place them in `live-guard-gate` or `runtime-evidence-gate` mode.
+
+## Invariants
+
+- Live-guard agents (netsuite-live-*) must never be auto-dispatched; require explicit approval and rollback plan.
+- Route all tasks through netsuite-maestro-agent for proper classification and dispatch.
+- Static review only -- agents analyze configuration and provide findings without mutating live systems.
+
+## Where the agents live
+
+Agent specs and adapters are part of the [Vanguard Frontier Agentic](https://github.com/Raishin/vanguard-frontier-agentic) marketplace. For this provider, see `agents/netsuite/` in that repository. All 25 agents in this provider ship a Kiro adapter (`harnesses/kiro-ide.agent.md`, `kiro-cli.agent.json`).
+
+## Companion install paths
+
+- **Claude Code:** `/plugin marketplace add Raishin/vanguard-frontier-agentic` then `/plugin install vanguard-frontier-agentic@vanguard-frontier-agentic`
+- **Codex / Copilot / Cursor / Gemini CLI / Kiro (file export):** `npx vfa-export-agents --platform <harness> --provider netsuite --repo .`

package/schemas/agent.schema.json

@@ -54,6 +54,7 @@
         "hr",
         "legal",
         "salesforce",
+        "netsuite",
         "accounting",
         "finance"
       ]

package/schemas/skill.schema.json

@@ -46,7 +46,8 @@
         "dotnet",
         "hr",
         "legal",
-        "salesforce"
+        "salesforce",
+        "netsuite"
       ]
     },
     "harnesses": {