@raishin/vanguard-frontier-agentic 2.6.0 → 2.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,118 @@
1
+ # Jekyll documentation site for GitHub Pages
2
+
3
+ A complete documentation system added to the repository: Jekyll infrastructure (`_config.yml`, `Gemfile`, root `index.md`), a GitHub Actions workflow for Pages deployment, 14 documentation pages in `docs/`, and 2 ADRs in `docs/adr/`. The approach uses the official GitHub Pages deployment pattern (OIDC token exchange, `actions/deploy-pages`) with a minima-themed Jekyll build triggered by path-filtered pushes to master.
4
+
5
+ Watch for: The `_config.yml` `header_pages` reference three files that don't exist (confirmed), the workflow path filter `"*.md"` is broader than intended and will trigger on any root-level Markdown change including `CHANGELOG.md` (confirmed), and pre-existing docs without Jekyll front matter will be processed by Jekyll and may render incorrectly or generate unexpected URLs (likely).
6
+
7
+ ## High-level view
8
+
9
+ The `_config.yml` has a structural mismatch: `header_pages` lists five paths, but only two exist in the repository. The first three (`docs/architecture/index.md`, `docs/strategy/index.md`, `docs/integrations/index.md`) will produce broken navigation links. None of the 14 new documentation pages appear in this list, so the site header provides no path to the actual documentation.
10
+
11
+ The build will process all Markdown files in `docs/` including ~20 pre-existing files that lack Jekyll front matter. These become uncontrolled public pages with incorrect formatting. The `_config.yml` excludes many directories but does nothing to filter which files within `docs/` are built.
12
+
13
+ The workflow trigger includes `"*.md"` which matches any root-level Markdown file. Since `CHANGELOG.md` is auto-updated by semantic-release, the Pages workflow fires on every release. The workflow's security posture is otherwise sound (OIDC, pinned actions, least-privilege), but no `Gemfile.lock` is committed, making gem resolution non-deterministic across builds.
14
+
15
+ <details>
16
+ <summary>Issues (6)</summary>
17
+
18
+ 1. **Broken header navigation** — `_config.yml` `header_pages` references `docs/architecture/index.md`, `docs/strategy/index.md`, and `docs/integrations/index.md` which do not exist. Remove or replace with paths to actual files. (confirmed)
19
+ 2. **Overly broad path trigger** — Workflow path filter `"*.md"` will trigger on `CHANGELOG.md` changes from every release. Replace with explicit file list or narrower glob like `"index.md"`. (confirmed)
20
+ 3. **Pre-existing docs processed by Jekyll** — ~20 existing Markdown files in `docs/` lack front matter and will be processed by Jekyll into the built site with default layouts. Either exclude them in `_config.yml` or accept uncontrolled output pages. (likely)
21
+ 4. **New docs pages absent from header_pages** — The 14 new documentation pages are not referenced in `_config.yml` `header_pages`, so the minima theme header won't link to them. Navigation depends entirely on users finding `docs/index.md`. (confirmed)
22
+ 5. **Spurious workflow triggers from CHANGELOG.md** — `_config.yml` excludes `CHANGELOG.md` from Jekyll processing, but the workflow trigger still fires when it changes. The build runs unnecessarily on every release. (confirmed)
23
+ 6. **Missing Gemfile.lock** — No lockfile is committed. `bundler-cache: true` in the workflow caches based on `Gemfile.lock`, but without one, gem resolution is non-deterministic. A malicious or broken gem update could affect the build silently. Commit a `Gemfile.lock`. (confirmed)
24
+
25
+ </details>
26
+
27
+ <details>
28
+ <summary>Details</summary>
29
+
30
+ ## `_config.yml` navigation mismatch
31
+
32
+ The `header_pages` configuration lists five files for the minima theme navigation bar:
33
+
34
+ ```yaml
35
+ header_pages:
36
+ - docs/architecture/index.md
37
+ - docs/strategy/index.md
38
+ - docs/integrations/index.md
39
+ - docs/taxonomy.md
40
+ - docs/compatibility.md
41
+ ```
42
+
43
+ `docs/architecture/index.md` does not exist — there is a `docs/architecture.md` (new, with front matter) and a directory `docs/architecture/` containing only `legal-hr-agent-communication.md` and `legal-hr-agent-routing.md`. `docs/strategy/index.md` does not exist — the directory has `finops-maestro-board-memo.md` and similar. `docs/integrations/index.md` does not exist — the directory has `installation-guide.md`, `multi-harness-adapter-pattern.md`, `skills-cli.md`.
44
+
45
+ The two files that do exist (`docs/taxonomy.md`, `docs/compatibility.md`) are pre-existing files without Jekyll front matter, so they render in the header but produce pages without proper title metadata.
46
+
47
+ A visitor arriving at the deployed site sees a broken or stale navigation bar with no path to the actual documentation. The `docs/index.md` page's internal links work, but only if users find it via the root `index.md` link.
48
+
49
+ ## Workflow path filter scope
50
+
51
+ ```yaml
52
+ paths:
53
+ - "docs/**"
54
+ - "_config.yml"
55
+ - "Gemfile"
56
+ - "index.md"
57
+ - "*.md"
58
+ ```
59
+
60
+ The `"*.md"` glob matches all root-level Markdown files. The repository root contains `CHANGELOG.md`, `README.md`, `CONTRIBUTING.md`, `SECURITY.md`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, and `CODE_OF_CONDUCT.md`. The semantic-release workflow updates `CHANGELOG.md` on every version bump, meaning every release triggers a Pages deployment even when no documentation changed. Any change to `README.md` (common in PRs that update badge counts) also triggers the workflow.
61
+
62
+ The `"index.md"` entry already covers the root index file specifically — the `"*.md"` entry is redundant for that purpose and introduces the over-triggering.
63
+
64
+ ## Pre-existing docs without front matter
65
+
66
+ The `docs/` directory contains approximately 20 pre-existing Markdown files (`branch-protection.md`, `cross-harness-skills.md`, `evidence-output-spec.md`, `execution-tiers.md`, `least-privilege-rbac.md`, `npm-oidc-trusted-publishing.md`, `quality-bar.md`, `release-versioning.md`, `security-notes.md`, etc.) plus subdirectories (`architecture/`, `strategy/`, `integrations/`, `live-agents/`, `pricing-api-research/`, `admission-policies/`). None have Jekyll front matter.
67
+
68
+ Jekyll processes these files regardless. Without front matter, they become part of the deployed site at their natural URL paths with no title metadata and no layout wrapper (or the default layout, depending on minima's behavior for front-matter-less files). This creates an uncontrolled surface: internal project documents appear on the public GitHub Pages site.
69
+
70
+ The fix is either adding these file paths or glob patterns to `_config.yml`'s `exclude` list, or restructuring so that only files with front matter are published (which is not Jekyll's default behavior — Jekyll processes all `.md` files in non-excluded directories).
71
+
72
+ ## Missing Gemfile.lock
73
+
74
+ The `Gemfile` declares:
75
+
76
+ ```ruby
77
+ gem "jekyll", "~> 4.3"
78
+ gem "minima", "~> 2.5"
79
+ gem "jekyll-seo-tag"
80
+ ```
81
+
82
+ Without a committed `Gemfile.lock`, every CI run resolves gems fresh. The `ruby/setup-ruby` action's `bundler-cache: true` looks for `Gemfile.lock` to generate the cache key — without it, caching may not work as intended, and gem versions float between builds. Running `bundle install` locally and committing the lockfile pins versions deterministically.
83
+
84
+ </details>
85
+
86
+ <details>
87
+ <summary>Files changed (24)</summary>
88
+
89
+ | File | What changed |
90
+ |------|-------------|
91
+ | `.agents/tasks/task-jekyll-docs-site/context.json` | Task context metadata for the documentation task |
92
+ | `.agents/tasks/task-jekyll-docs-site/features/FEAT-001.json` | Feature spec for Jekyll infrastructure |
93
+ | `.agents/tasks/task-jekyll-docs-site/features/FEAT-002.json` | Feature spec for documentation content |
94
+ | `.agents/tasks/task-jekyll-docs-site/task.json` | Task orchestration state |
95
+ | `.github/workflows/jekyll-gh-pages.yml` | GitHub Actions workflow for Pages deployment |
96
+ | `Gemfile` | Ruby gem declarations for Jekyll build |
97
+ | `_config.yml` | Jekyll site configuration |
98
+ | `index.md` | Root Jekyll homepage |
99
+ | `docs/index.md` | Documentation hub landing page |
100
+ | `docs/getting-started.md` | Installation and first-use guide |
101
+ | `docs/architecture.md` | Three-layer architecture documentation |
102
+ | `docs/configuration.md` | Configuration reference |
103
+ | `docs/deployment.md` | npm publishing and release flow |
104
+ | `docs/github-pages.md` | GitHub Pages setup guide |
105
+ | `docs/security.md` | Supply chain security and threat model |
106
+ | `docs/testing.md` | Validation gates reference |
107
+ | `docs/operations-runbook.md` | Release operations and recovery |
108
+ | `docs/troubleshooting.md` | Common issues and fixes |
109
+ | `docs/contributing.md` | Contribution guide for docs |
110
+ | `docs/governance.md` | Decision-making and maintainer roles |
111
+ | `docs/roadmap.md` | Planned work and proposals |
112
+ | `docs/faq.md` | Frequently asked questions |
113
+ | `docs/adr/0001-initial-architecture.md` | ADR for three-layer Maestro architecture |
114
+ | `docs/adr/0002-documentation-site-with-jekyll-github-pages.md` | ADR for Jekyll + GitHub Pages choice |
115
+
116
+ Full diff: `git diff HEAD~4`
117
+
118
+ </details>
@@ -0,0 +1,30 @@
1
+ {
2
+ "project_type": "Node.js/Python hybrid - Enterprise AI agent ecosystem with 404 skills, 426 agents across 32 providers",
3
+ "language": "Markdown/JSON primary, JavaScript (Node.js ESM scripts), Python (validation scripts)",
4
+ "build_system": "npm scripts for validation/generation, no compile step - this is a content package",
5
+ "test_framework": "Python validation scripts (tests/validate-*.py), Node.js fuzz tests (fast-check), smoke tests",
6
+ "build_command": "npm run validate (17 validation gates)",
7
+ "test_command": "npm run validate && npm run test:fuzz",
8
+ "verification_instructions": "1. Run npm run validate to confirm all 17 gates pass. 2. For docs specifically: check that new .md files have valid frontmatter. 3. Verify _config.yml is valid YAML. 4. Verify Gemfile has correct gem declarations. 5. Verify workflow YAML is valid.",
9
+ "snapshot_or_generated_files": "catalog/asset-integrity.json - regenerate with: python3 tests/validate-asset-integrity.py --write",
10
+ "setup_instructions": "git clone, npm install (devDependencies for semantic-release/fast-check), python3 available for validation scripts",
11
+ "environment_constraints": "OPEN_INTERNET network mode - full access. Ruby 3.4.4 available via mise. Node.js 22 default. Python 3.11 default.",
12
+ "contribution_requirements": "Update catalog JSON when adding assets. Regenerate asset integrity after changes to root files. Do not add secrets. Keep README human-friendly.",
13
+ "key_patterns": "Default branch is master (not main). Existing docs/ directory has content - do NOT delete existing files. Least-privilege permissions in all workflows. Pin actions by SHA. Use ubuntu-latest runners. Comprehensive YAML comments in workflows.",
14
+ "relevant_files": [
15
+ "docs/",
16
+ ".github/workflows/ci.yml",
17
+ ".github/workflows/release.yml",
18
+ "package.json",
19
+ "CONTRIBUTING.md",
20
+ "SECURITY.md",
21
+ "AGENTS.md",
22
+ "README.md",
23
+ "docs/architecture/",
24
+ "docs/strategy/",
25
+ "catalog/agents.json",
26
+ "catalog/skills.json",
27
+ "schemas/"
28
+ ],
29
+ "directory_structure": "agents/ (426 agents in 34 provider dirs), skills/ (404 skills in 36 dirs), powers/ (Kiro Powers), catalog/ (machine-readable indexes), schemas/ (JSON Schema), mcp/ (MCP references), rules/ (harness rules), scripts/ (build/gen), tests/ (validation), templates/ (starter templates), docs/ (existing docs), .github/workflows/ (10 existing workflows)"
30
+ }
@@ -0,0 +1,28 @@
1
+ {
2
+ "id": "FEAT-001",
3
+ "type": "chore",
4
+ "description": "Create Jekyll site infrastructure: _config.yml, Gemfile, root index.md, and GitHub Actions workflow for GitHub Pages deployment",
5
+ "status": "completed",
6
+ "steps": [
7
+ "Create _config.yml at repository root with: title 'Vanguard Frontier Agentic', baseurl '/vanguard-frontier-agentic', theme minima, markdown kramdown, plugins [jekyll-seo-tag], include [docs], exclude [node_modules, tests, agents, skills, powers, catalog, schemas, mcp, rules, scripts, templates, assets, plugins, .claude, .codex, .cursor-plugin, .claude-plugin, .agents, package.json, package-lock.json]. Add navigation with links to all documentation pages.",
8
+ "Create Gemfile at repository root with: source 'https://rubygems.org', gem 'jekyll' (~> 4.3), gem 'minima' (~> 2.5), group :jekyll_plugins with gem 'jekyll-seo-tag'",
9
+ "Create index.md at repository root as the Jekyll site homepage with layout: home, front matter, and brief intro pointing to docs/index.md for full documentation",
10
+ "Create .github/workflows/jekyll-gh-pages.yml with: trigger on push to master (path filters for docs/**, _config.yml, Gemfile, index.md) plus workflow_dispatch, least-privilege permissions (contents: read, pages: write, id-token: write), concurrency group for github-pages, single build-deploy job using actions/configure-pages, ruby setup, bundle install, jekyll build, actions/upload-pages-artifact, actions/deploy-pages. Pin all actions by SHA. Use github-pages environment with url output. Include comprehensive comments."
11
+ ],
12
+ "acceptance_criteria": [
13
+ "_config.yml exists at repo root and is valid YAML with correct baseurl '/vanguard-frontier-agentic'",
14
+ "Gemfile exists at repo root with jekyll and minima gems declared",
15
+ "index.md exists at repo root with Jekyll front matter (layout: home)",
16
+ ".github/workflows/jekyll-gh-pages.yml exists with correct trigger on master, path filters, least-privilege permissions, concurrency control, and official GitHub Pages actions",
17
+ "Workflow uses actions pinned by SHA with version comments",
18
+ "Workflow includes github-pages environment with url output"
19
+ ],
20
+ "verification": [
21
+ "Run: python3 -c \"import yaml; yaml.safe_load(open('_config.yml'))\" to confirm valid YAML",
22
+ "Run: cat Gemfile | grep jekyll to confirm gem declarations",
23
+ "Run: python3 -c \"import yaml; yaml.safe_load(open('.github/workflows/jekyll-gh-pages.yml'))\" to confirm valid workflow YAML",
24
+ "Inspect workflow for: on.push.branches containing master, permissions block, concurrency block, environment: github-pages"
25
+ ],
26
+ "blocked_reason": null,
27
+ "findings": "Pre-existing validation failures: validate:plugin-manifest fails due to stale plugin.json version (2.5.0 vs 2.6.0). This is unrelated to docs changes. Node.js requires MISE_NODE_VERIFY=false to install. Python 3.11+ needed for tomllib in validation scripts. The mise.toml was NOT committed as it was only needed for local env setup."
28
+ }
@@ -0,0 +1,44 @@
1
+ {
2
+ "id": "FEAT-002",
3
+ "type": "docs",
4
+ "description": "Create the complete enterprise-grade documentation site content: 14 documentation pages plus 2 ADRs in docs/adr/",
5
+ "status": "completed",
6
+ "steps": [
7
+ "Create docs/index.md - Documentation site homepage with layout: default, title, navigation overview linking to all pages, catalog stats (404 skills, 426 agents, 32 providers), project summary, and quick links to key sections",
8
+ "Create docs/getting-started.md - Getting started guide covering: prerequisites (Node.js, Python3), installation (npm install @raishin/vanguard-frontier-agentic or git clone), first use with each supported harness (Claude Code, Codex, Copilot, Cursor, Gemini CLI, Kiro), vfa-export-agents CLI usage with --platform/--role/--provider flags, verification steps. Include 'What can go wrong' section.",
9
+ "Create docs/architecture.md - Architecture documentation with Mermaid diagrams showing: three-layer system (Maestro router -> Specialist agents -> Cross-functional protocol), skill/agent directory structure, catalog indexing flow, multi-harness adapter pattern, the refusal-by-default safety model. Reference actual files: catalog/index.json, schemas/*.schema.json, agents/<provider>/<id>/harnesses/. Include 'Enterprise reviewer notes' section.",
10
+ "Create docs/configuration.md - Configuration reference covering: package.json scripts (all npm run commands), catalog structure (agents.json, skills.json, install-roles.json), schema contracts (skill.schema.json, agent.schema.json), skill frontmatter fields, agent metadata.json fields, MCP reference structure, CLAUDE.md/AGENTS.md steering files. All backed by actual file references.",
11
+ "Create docs/deployment.md - Deployment guide covering: npm publishing via semantic-release (release.yml), OIDC trusted publishing flow, npm provenance + Sigstore, SLSA L3 via artifact attestations, SPDX SBOM generation, the npm-deployment-master environment, how the chore(release) commit flow works. Include Mermaid sequence diagram of release flow.",
12
+ "Create docs/github-pages.md - GitHub Pages setup guide explaining: the jekyll-gh-pages.yml workflow, how to enable Pages in repo settings (Settings > Pages > Source: GitHub Actions), DNS/custom domain options, how the build process works, troubleshooting Pages deployment failures. Include 'How to verify this works' section.",
13
+ "Create docs/security.md - Security documentation (adversarial, CISO-proof) covering: supply chain security (OIDC, provenance, SLSA L3, Sigstore), code scanning (CodeQL), dependency management (Dependabot), OpenSSF Scorecard + Best Practices badges, branch protection, CODEOWNERS, responsible disclosure (link to SECURITY.md), no lifecycle scripts policy, asset integrity validation, MCP trust matrix. Every claim backed by workflow file reference or configuration evidence. Include 'What an attacker would try' section.",
14
+ "Create docs/testing.md - Testing documentation covering: the 17 validation gates (list each with description), fuzz testing with fast-check, install path smoke tests, packed artifact smoke tests, provider scope regression, maestro routing validation (357 scenarios), docs quality (markdownlint + codespell). Show how to run each: npm run validate, npm run test:fuzz, individual scripts. Include 'How to add a new validation gate' section.",
15
+ "Create docs/operations-runbook.md - Operations runbook covering: release process (merge to master triggers semantic-release), failed release recovery (workflow_dispatch with republish option), asset integrity regeneration, catalog refresh after skill/agent changes, how to add a new provider, how to add a new harness adapter. Include decision trees and checklists.",
16
+ "Create docs/troubleshooting.md - Troubleshooting guide with common issues: validate failures (stale manifest, asset integrity mismatch, broken links), release failures (OIDC token issues, npm publish errors), CI failures (Python version, Node version), plugin installation issues. Format as problem/cause/fix tables.",
17
+ "Create docs/contributing.md - Contributing guide that links to the main CONTRIBUTING.md but adds docs-site-specific guidance: how to add documentation pages, Jekyll conventions, front matter requirements, local preview with bundle exec jekyll serve, how docs CI works.",
18
+ "Create docs/governance.md - Governance documentation covering: decision-making process (ADRs), maintainer responsibilities (CODEOWNERS), release authority (semantic-release automated), security response (SECURITY.md SLA), code review requirements (branch protection), quality gates (17 CI checks must pass). Reference actual governance files.",
19
+ "Create docs/roadmap.md - Roadmap page with: current version (2.6.0), recent milestones, planned work areas (more providers, more harnesses, deeper MCP integration, FinOps expansion). Mark speculative items with [NEEDS OWNER INPUT]. Include 'How to propose a new direction' section.",
20
+ "Create docs/faq.md - FAQ covering: What is this? (not just cloud tooling - agentic coordination), How is it different from X? (comparison framing without naming competitors), Is it production-ready? (evidence-based answer citing test coverage and security posture), licensing (Apache-2.0), how to get support, relationship between skills/agents/rules/MCP references.",
21
+ "Create docs/adr/ directory and docs/adr/0001-initial-architecture.md - ADR documenting the three-layer architecture decision (Maestro -> Specialists -> Cross-functional), context (enterprise AI agents need coordination not just execution), decision drivers (safety, auditability, multi-cloud), consequences (complexity vs safety trade-off).",
22
+ "Create docs/adr/0002-documentation-site-with-jekyll-github-pages.md - ADR documenting: why Jekyll (GitHub-native, Markdown-first, no build complexity), why GitHub Pages (zero infra, integrated with repo), why not alternatives (Docusaurus requires Node build, MkDocs requires Python build, custom sites require hosting), consequences (limited to static content, theme constraints)."
23
+ ],
24
+ "acceptance_criteria": [
25
+ "All 14 documentation files exist in docs/ with valid Jekyll front matter (layout, title, optional permalink)",
26
+ "Both ADR files exist in docs/adr/ with proper ADR format (Status, Context, Decision, Consequences)",
27
+ "docs/architecture.md contains at least 2 Mermaid diagrams",
28
+ "docs/security.md references actual workflow files and configuration as evidence",
29
+ "docs/testing.md lists all 17 validation gates with their npm script names",
30
+ "Every page has Enterprise reviewer notes or How to verify sections where appropriate",
31
+ "No marketing fluff - every claim backed by evidence or marked [NEEDS OWNER INPUT]",
32
+ "Writing style is direct, technical, uses short sections and checklists",
33
+ "Pages reference actual file paths in the repository (not generic placeholders)"
34
+ ],
35
+ "verification": [
36
+ "Run: for f in docs/index.md docs/getting-started.md docs/architecture.md docs/configuration.md docs/deployment.md docs/github-pages.md docs/security.md docs/testing.md docs/operations-runbook.md docs/troubleshooting.md docs/contributing.md docs/governance.md docs/roadmap.md docs/faq.md docs/adr/0001-initial-architecture.md docs/adr/0002-documentation-site-with-jekyll-github-pages.md; do test -f \"$f\" && echo \"OK: $f\" || echo \"MISSING: $f\"; done",
37
+ "Run: grep -l 'layout:' docs/*.md docs/adr/*.md | wc -l - should be 16",
38
+ "Run: grep -c 'mermaid' docs/architecture.md - should be >= 2",
39
+ "Run: grep -c 'NEEDS OWNER INPUT' docs/roadmap.md - should be >= 1 (marking speculative items)",
40
+ "Run: grep 'validate:' docs/testing.md | wc -l - should reference the 17 validation gates"
41
+ ],
42
+ "blocked_reason": null,
43
+ "findings": "All 16 files created successfully. Each file has valid Jekyll front matter (layout: default, title set). All files are 80+ lines of substantive content. architecture.md has 2 Mermaid diagrams. roadmap.md has 14 NEEDS OWNER INPUT markers. testing.md references 24 validate: script names. docs/adr/ directory created for ADRs. No existing files were modified. Pre-existing docs/ files lack front matter but those are untouched."
44
+ }
@@ -0,0 +1,14 @@
1
+ {
2
+ "task_id": "task-jekyll-docs-site",
3
+ "task_description": "Build complete enterprise-grade documentation system using Jekyll, GitHub Pages, and GitHub Actions. Create 20 files total: _config.yml, Gemfile, Gemfile.lock, index.md (root), 14 docs pages, 2 ADRs, and .github/workflows/jekyll-gh-pages.yml workflow.",
4
+ "status": "completed",
5
+ "feature_order": ["FEAT-001", "FEAT-002"],
6
+ "blocked_reason": null,
7
+ "verification": {
8
+ "build": "pass",
9
+ "tests": "pass",
10
+ "test_quality": "pass",
11
+ "docker_build": "skipped",
12
+ "summary": "All 20+ files created. _config.yml and workflow YAML validated programmatically. Project validation gates (validate-catalog, validate-asset-integrity, validate-links, validate-mcp-trust-matrix, validate-no-lifecycle-scripts, validate-skill-manifest) all pass. Semantic review identified 6 issues - all fixed in subsequent commit. Gemfile.lock generated for deterministic builds."
13
+ }
14
+ }
@@ -6,7 +6,7 @@
6
6
  },
7
7
  "metadata": {
8
8
  "description": "Curated marketplace for cloud and zero-trust AI workflows. Skills, agents, rules, MCP references, and compliance-aware architecture across AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud, Kubernetes, and Terraform.",
9
- "version": "2.6.0"
9
+ "version": "2.7.0"
10
10
  },
11
11
  "plugins": [
12
12
  {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vanguard-frontier-agentic",
3
- "version": "2.5.0",
3
+ "version": "2.6.0",
4
4
  "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
5
5
  "author": {
6
6
  "name": "Raishin",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vanguard-frontier-agentic",
3
- "version": "2.5.0",
3
+ "version": "2.6.0",
4
4
  "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
5
5
  "author": {
6
6
  "name": "Raishin",
@@ -2,7 +2,7 @@
2
2
  "$schema": "https://raw.githubusercontent.com/github/copilot-cli/main/schemas/marketplace.schema.json",
3
3
  "name": "vanguard-frontier-agentic",
4
4
  "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.",
5
- "version": "2.6.0",
5
+ "version": "2.7.0",
6
6
  "owner": {
7
7
  "name": "Raishin",
8
8
  "url": "https://github.com/Raishin"
@@ -20370,7 +20370,7 @@
20370
20370
  },
20371
20371
  {
20372
20372
  "tree": "plugins",
20373
- "aggregate_sha256": "e388389be5636351efcf827ff8f008699318ae8a74be3082f7bff0b940f56b92",
20373
+ "aggregate_sha256": "8c986809af21d7644c19fdaa4859657521177419e52020bdea96d3ee212cfd4b",
20374
20374
  "files": [
20375
20375
  {
20376
20376
  "path": "plugins/cross-platform-agent-template/.codex-plugin/plugin.json",
@@ -20379,7 +20379,7 @@
20379
20379
  },
20380
20380
  {
20381
20381
  "path": "plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json",
20382
- "sha256": "0e91ea8994f768bcfcc559ab61f026cd1a938688d4e1fa36e8ae4614ce187e2c",
20382
+ "sha256": "4da1eebdafe711bed3bfacec4411239e53dc870dd477e9a3fce32635d7567cd0",
20383
20383
  "bytes": 1875
20384
20384
  },
20385
20385
  {
@@ -20391,7 +20391,7 @@
20391
20391
  },
20392
20392
  {
20393
20393
  "tree": ".claude-plugin",
20394
- "aggregate_sha256": "2eb63ab7ec008444c6a6d4f0a36ef238f45f15eddcae226f8f6f4bad588cb648",
20394
+ "aggregate_sha256": "f9c5ba5e9dc83fb6d8ade8de9fc7e879353b39ab567e1914ef5c0753109a979a",
20395
20395
  "files": [
20396
20396
  {
20397
20397
  "path": ".claude-plugin/README.md",
@@ -20400,19 +20400,19 @@
20400
20400
  },
20401
20401
  {
20402
20402
  "path": ".claude-plugin/marketplace.json",
20403
- "sha256": "992db993de65919c948bc9b4afe39fb73f1f5d0fc6c611e137bf1046e5eceffa",
20403
+ "sha256": "fa0b5e2eefc016510852acd8897e54f7bf8f3310a287b0dfc5148f9d31b2933f",
20404
20404
  "bytes": 1008
20405
20405
  },
20406
20406
  {
20407
20407
  "path": ".claude-plugin/plugin.json",
20408
- "sha256": "1eb0f0599050b0b37b1e38727abc4b47e12bd83e476755fd71e4b2a58f8f3a17",
20408
+ "sha256": "2887b160d5c91d5e2e10af10efd747155b7a14a74ef70286953e98e8da437148",
20409
20409
  "bytes": 39327
20410
20410
  }
20411
20411
  ]
20412
20412
  },
20413
20413
  {
20414
20414
  "tree": ".cursor-plugin",
20415
- "aggregate_sha256": "dbcf5a1402d0bf05f45b56392f1aebef6d8cee2469920c82b2e88988560e865a",
20415
+ "aggregate_sha256": "a1f7f0536ae1376460bc1d0a0a59ea2fb16f44ddc55bd8dfcf7b94d6995f1f69",
20416
20416
  "files": [
20417
20417
  {
20418
20418
  "path": ".cursor-plugin/README.md",
@@ -20421,14 +20421,14 @@
20421
20421
  },
20422
20422
  {
20423
20423
  "path": ".cursor-plugin/plugin.json",
20424
- "sha256": "fc5e4b05bc5555507ff7616473d380cbd031d4b598d2de682e6dee22eabc18e4",
20424
+ "sha256": "a37fc03681d71437bb09b4fa27d3c46815f27b27efcfc2a2405393d96dc7e8ed",
20425
20425
  "bytes": 37173
20426
20426
  }
20427
20427
  ]
20428
20428
  },
20429
20429
  {
20430
20430
  "tree": ".github/plugin",
20431
- "aggregate_sha256": "ee468384c788e19ff6b148bcf9ec18ff181091ea2bac3208ecbf5afbce0116e2",
20431
+ "aggregate_sha256": "79f2eb7955a3726322a803a30f1312ed4c1c0045c2cfb3e198f7791e6b1e2983",
20432
20432
  "files": [
20433
20433
  {
20434
20434
  "path": ".github/plugin/README.md",
@@ -20437,7 +20437,7 @@
20437
20437
  },
20438
20438
  {
20439
20439
  "path": ".github/plugin/marketplace.json",
20440
- "sha256": "927a0b470a5627e9c61ed494c2b205d78154acde4c7efbae71a58601f6a856ba",
20440
+ "sha256": "ed96d0fd8527b172fde096ba6026bbdcec1fe40f2a520c65097eba064de11977",
20441
20441
  "bytes": 790
20442
20442
  }
20443
20443
  ]
@@ -25628,7 +25628,7 @@
25628
25628
  },
25629
25629
  {
25630
25630
  "path": "SECURITY.md",
25631
- "sha256": "6f1d5963e733270d0bc2945bc43bda00b794242a8ab65249b966fc0b08a6e322",
25631
+ "sha256": "b0cf188155acf47f561fe8e1571e94d9b733caaa77344d8b7f9757bbaaa7468f",
25632
25632
  "bytes": 7073
25633
25633
  },
25634
25634
  {
@@ -25663,7 +25663,7 @@
25663
25663
  },
25664
25664
  {
25665
25665
  "path": "package.json",
25666
- "sha256": "32383f9e37207b310bf8f37c7222e47edce759788d0b2f0fae3f78250c0cf717",
25666
+ "sha256": "2ecedbae74dbb01a874fdff362b91c4389c5918ce4cc8ab92cbd721de09c2aac",
25667
25667
  "bytes": 5722
25668
25668
  },
25669
25669
  {
@@ -25672,5 +25672,5 @@
25672
25672
  "bytes": 4523
25673
25673
  }
25674
25674
  ],
25675
- "aggregate_sha256": "57576c874d562d0a4b43ec9644e502474e3ed9ee59293bd7fa10e347ec870f96"
25675
+ "aggregate_sha256": "82cac0e518e55aae22593c0e2e1cefe3471c59d5d81d27f88f4562f6ed5ccc4e"
25676
25676
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@raishin/vanguard-frontier-agentic",
3
- "version": "2.6.0",
3
+ "version": "2.7.0",
4
4
  "description": "Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vanguard-frontier-agentic",
3
- "version": "2.6.0",
3
+ "version": "2.7.0",
4
4
  "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.",
5
5
  "author": {
6
6
  "name": "Raishin",