@raishin/vanguard-frontier-agentic 3.3.0 → 3.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raishin/vanguard-frontier-agentic",
-  "version": "3.3.0",
+  "version": "3.5.0",
   "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
   "license": "Apache-2.0",
   "repository": {
@@ -95,7 +95,7 @@
     "@semantic-release/release-notes-generator": "14.1.1",
     "conventional-changelog-conventionalcommits": "10.2.1",
     "fast-check": "^4.7.0",
-    "semantic-release": "25.0.5"
+    "semantic-release": "25.0.7"
   },
   "publishConfig": {
     "access": "public",

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

@@ -1,6 +1,6 @@
 {
   "name": "vanguard-frontier-agentic",
-  "version": "3.3.0",
+  "version": "3.5.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 **41 Kiro Powers** for `vanguard-frontier-agentic`, one
+This directory holds **43 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.
 
@@ -30,6 +30,8 @@ powers/
 ├── vanguard-huawei/POWER.md
 ├── vanguard-ionos/POWER.md
 ├── vanguard-istio/POWER.md
+├── vanguard-java/POWER.md
+├── vanguard-kotlin/POWER.md
 ├── vanguard-kubernetes/POWER.md
 ├── vanguard-kyverno/POWER.md
 ├── vanguard-legal/POWER.md
@@ -85,7 +87,7 @@ cd vanguard-frontier-agentic
 ## How to update
 
 ```bash
-# Regenerate the 41 Powers from catalog/agents.json + per-provider config:
+# Regenerate the 43 Powers from catalog/agents.json + per-provider config:
 npm run kiro-powers:write
 
 # Then verify everything is in sync:

package/powers/vanguard-java/POWER.md

@@ -0,0 +1,40 @@
+---
+name: "vanguard-java"
+displayName: "Vanguard Frontier — Java"
+description: "Curated Java agents for java application server exit, java concurrency and virtual thread, java container and kubernetes readiness, java database migration safety. Routes via java-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
+keywords: ["java", "static-review", "configuration-audit", "best-practices"]
+author: "Raishin"
+---
+# Vanguard Frontier — Java
+
+Curated Java agents for java application server exit, java concurrency and virtual thread, java container and kubernetes readiness, java database migration safety. Routes via java-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 Java services, resources, or operations. Do not activate on unrelated requests — narrow keyword matching is required to avoid false activations (Kiro Powers convention).
+
+## Routing pattern
+
+- **`java-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)
+
+- *(none — this provider has no live-mutation guards in the catalog)*
+
+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
+
+- Route all tasks through java-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/java/` in that repository. All 15 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 java --repo .`

package/powers/vanguard-kotlin/POWER.md

@@ -0,0 +1,40 @@
+---
+name: "vanguard-kotlin"
+displayName: "Vanguard Frontier — Kotlin"
+description: "Curated Kotlin agents for kotlin android architecture, kotlin android performance reliability, kotlin android security privacy, kotlin backend production readiness. Routes via kotlin-maestro-agent to specialist agents based on task scope. Static review only; no live mutations."
+keywords: ["kotlin", "static-review", "configuration-audit", "best-practices"]
+author: "Raishin"
+---
+# Vanguard Frontier — Kotlin
+
+Curated Kotlin agents for kotlin android architecture, kotlin android performance reliability, kotlin android security privacy, kotlin backend production readiness. Routes via kotlin-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 Kotlin services, resources, or operations. Do not activate on unrelated requests — narrow keyword matching is required to avoid false activations (Kiro Powers convention).
+
+## Routing pattern
+
+- **`kotlin-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)
+
+- *(none — this provider has no live-mutation guards in the catalog)*
+
+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
+
+- Route all tasks through kotlin-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/kotlin/` in that repository. All 16 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 kotlin --repo .`

package/schemas/agent.schema.json

@@ -52,6 +52,8 @@
         "generic",
         "frontend",
         "dotnet",
+        "java",
+        "kotlin",
         "hr",
         "legal",
         "salesforce",
@@ -62,7 +64,22 @@
         "microsoft",
         "databricks",
         "snowflake",
-        "php"
+        "php",
+        "kyverno",
+        "istio",
+        "argocd",
+        "cilium",
+        "opentelemetry",
+        "prometheus",
+        "falco",
+        "sigstore",
+        "cert-manager",
+        "fluxcd",
+        "backstage",
+        "velero",
+        "nvidia",
+        "claude",
+        "marketing"
       ]
     },
     "harnesses": {

package/schemas/skill.schema.json

@@ -45,6 +45,8 @@
         "generic",
         "frontend",
         "dotnet",
+        "java",
+        "kotlin",
         "hr",
         "legal",
         "salesforce",
@@ -53,7 +55,31 @@
         "microsoft",
         "databricks",
         "snowflake",
-        "php"
+        "php",
+        "kyverno",
+        "istio",
+        "argocd",
+        "cilium",
+        "opentelemetry",
+        "prometheus",
+        "falco",
+        "sigstore",
+        "cert-manager",
+        "fluxcd",
+        "backstage",
+        "velero",
+        "alibaba",
+        "huawei",
+        "ovhcloud",
+        "ionos",
+        "scaleway",
+        "hetzner",
+        "contabo",
+        "nvidia",
+        "claude",
+        "marketing",
+        "accounting",
+        "finance"
       ]
     },
     "harnesses": {