[Bundle]: Add Agentstandards Multi-Vendor Architecture

The issue is a bundle submission for the Spec Kit project. Start by reading the bundle.yml manifest and README in the linked repository to understand the multi-vendor architecture components. Test the bundle validation and installation using the provided CLI commands in a clean Spec Kit project. 'Done' means the bundle is successfully integrated and the proposed catalog entry is added.

Bundle ID

agentstandards

Bundle Name

Agentstandards Multi-Vendor Architecture

Version

0.1.0

Role or Team

architecture-governance

Description

Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.

Author

bbjwz

Repository URL

https://github.com/bbjwz/agentstandards

Download URL

https://github.com/bbjwz/agentstandards/releases/download/v0.1.0/agentstandards-bundle-0.1.0.zip

Documentation URL

https://github.com/bbjwz/agentstandards/blob/v0.1.0/bundles/agentstandards/README.md

License

MIT

Required Spec Kit Version

=1.0.8,<2.0.0

Integration Target (optional)

codex

Components Provided

• extensions: agentstandards@0.1.0
• presets: agentstandards-gate@0.1.0
• workflows: agentstandards-architecture@0.1.0
• steps: None

Required Component Catalogs

• Extensions: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/extensions.json
• Presets: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/presets.json
• Workflows: https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/workflows.json

Tags

architecture, governance, multi-vendor, codex

Key Features

• Installs the complete Agentstandards extension, task-gate preset, and architecture workflow as one pinned stack.
• Runs 13 architecture roles across Codex, Anthropic, and all enabled optional vendors.
• Uses fresh model instances for every gate and labels peer work for disclosed review passes.
• Pauses for human decisions and records their rationale before final validation.
• Keeps task generation blocked until the aggregate architecture gate is READY.

Testing Checklist

• Validation succeeds with specify bundle validate --path <bundle-directory>
• Build succeeds with specify bundle build --path <bundle-directory> and produces the submitted artifact
• Bundle installs successfully from the built artifact
• The submitted distribution path was tested end to end, including bundle-ID installation from an install-allowed catalog when a catalog entry is proposed
• Installation was tested in a clean Spec Kit project
• Required component catalogs are documented and were included in testing, or no extra catalogs are required
• Documentation is complete and accurate

Submission Requirements

• Valid bundle.yml manifest included
• README.md explains the bundle's intended role, installed components, and installation steps
• LICENSE file included
• GitHub release created with version tag
• Bundle ID matches the manifest and follows naming conventions
• Every extension, preset, workflow, and step reference is pinned where the manifest requires a version

Testing Details

Tested on:

• macOS with Spec Kit 1.0.8 and 1.0.10
• GitHub Actions on Python 3.11 and 3.14

Test project: Clean Spec Kit 1.0.10 Codex projects created specifically for release verification.

Test scenarios:

1. Validated bundles/agentstandards with the official Spec Kit bundle validator.
2. Built it with specify bundle build --path bundles/agentstandards.
3. Downloaded the submitted v0.1.0 bundle asset and installed it in a clean project after registering the three required component catalogs.
4. Registered the public bundle catalog with install-allowed policy and installed agentstandards by bundle ID in another clean project.
5. Verified Spec Kit reports the bundle at v0.1.0 with all three components and reports the extension with five commands and two hooks.
6. Ran 30 automated tests, Ruff, release metadata checks, and full-history Gitleaks scanning.

The monorepo release builder uses a distinct agentstandards-bundle-0.1.0.zip filename to avoid colliding with the extension archive in the same GitHub release. Its bundle payload is the validated manifest and README plus the required top-level MIT LICENSE. Both the official CLI-built archive and the submitted release archive installed successfully.

Example Usage

specify extension catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/extensions.json \
  --name agentstandards --install-allowed

specify preset catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/presets.json \
  --name agentstandards --install-allowed

specify workflow catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/workflows.json \
  --name agentstandards

specify bundle catalog add \
  https://raw.githubusercontent.com/bbjwz/agentstandards/v0.1.0/catalogs/bundles.json \
  --id agentstandards --policy install-allowed

specify bundle install agentstandards

Proposed Catalog Entry

{
  "agentstandards": {
    "name": "Agentstandards Multi-Vendor Architecture",
    "id": "agentstandards",
    "version": "0.1.0",
    "role": "architecture-governance",
    "description": "Installs the council extension, hard task gate, and Codex architecture workflow.",
    "author": "bbjwz",
    "license": "MIT",
    "download_url": "https://github.com/bbjwz/agentstandards/releases/download/v0.1.0/agentstandards-bundle-0.1.0.zip",
    "repository": "https://github.com/bbjwz/agentstandards",
    "requires": {
      "speckit_version": ">=1.0.8,<2.0.0"
    },
    "provides": {
      "extensions": 1,
      "presets": 1,
      "steps": 0,
      "workflows": 1
    },
    "tags": ["architecture", "governance", "multi-vendor", "codex"],
    "verified": false
  }
}

Additional Context

Release v0.1.0 publishes SHA-256 checksums and GitHub build-provenance attestations for every artifact. Live provider calls are explicit only; normal CI and bundle installation are offline from model providers.