Repository navigation
[Bundle]: Add Agentstandards Multi-Vendor Architecture #4722
Description
Activity
- addedtriage-can-waitVerdict: valid and in-scope but deprioritized; held behind the evidence gateVerdict: valid and in-scope but deprioritized; held behind the evidence gatebundle-submissionCommunity bundle catalog submissionCommunity bundle catalog submissiontriage-must-haveVerdict: high-value, important work for Spec Kit — do firstVerdict: high-value, important work for Spec Kit — do firstand removedtriage-can-waitVerdict: valid and in-scope but deprioritized; held behind the evidence gateVerdict: valid and in-scope but deprioritized; held behind the evidence gate
on Sep 24, 2026 github-actions commented
on Sep 24, 2026 on Sep 24, 2026 – with GitHub ActionsContributorMore actionscc @github/spec-kit-maintainers — new catalog submission for review.
github-actions commented
on Sep 24, 2026 on Sep 24, 2026 – with GitHub ActionsContributorMore actionsValidation failed for this submission. The artifact download itself completed with HTTP 200, and the downloaded archive digest was
f15baa79a01467d2fef9b5fac1971cf73c9e34d0b114d0054a714c0e7dce8542.Failed checks:
- Manifest metadata mismatch:
bundles/agentstandards/bundle.ymldescribes the bundle as “Install the Agentstandards council, task gate, and Spec Kit architecture workflow together.”, which does not match the submitted Description (“Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.”). Update the submission or manifest so they match exactly. - Integration target not represented in the manifest: the submission specifies
codex, butbundle.ymldoes not declare or otherwise match that integration target. Add the target to the manifest if supported, or correct the submission. - Documentation URL is incomplete:
bundles/agentstandards/README.mdidentifies the components and required catalogs but does not provide the installation commands/steps; it points readers to the repository root README instead. Make the submitted documentation URL self-contained, including the required catalog setup and bundle installation steps.
The release tag and exact ZIP asset were present, the repository contained
bundle.yml,README.md, andLICENSE, and the proposed catalog entry had valid counts, tags, andverified: false. Please correct the failed items and submit again.Workflow run: https://github.com/github/spec-kit/actions/runs/36000313833
Generated by 📦 Add Community Bundle from Issue Submission for #4722 · copilot · gpt52codex · 2.36 AIC · ⌖ 6.81 AIC · ⊞ 24K · ◷
- Manifest metadata mismatch:
Based on the Copilot reviewer’s findings, please align the submitted description with
bundle.yml, declare or remove thecodexintegration target, and make the bundle README self-contained with the required catalog setup and installation steps. Maintainers will review the updated revision.- added a commit that references this issue
on Sep 24, 2026 Published and verified v0.1.1, then updated the submission body with the corrected manifest metadata, documentation URL, download URL, component versions, installation example, and SHA-256.
The revision addresses every reported item:
-
bundle.yml, the companion catalog, and the submitted Description now use the same exact text. -
bundle.ymldeclares the supported top-level integration target asintegration.id: codex. -
The bundle-scoped README is self-contained and includes all three required component catalog commands, bundle-catalog installation, direct artifact installation, prerequisites, and post-install usage.
-
A clean Spec Kit 1.0.10 catalog-backed install resolved and installed the bundle and all three v0.1.1 components.
-
Release: https://github.com/bbjwz/agentstandards/releases/tag/v0.1.1
-
Corrective PR: Address Spec Kit catalog review feedback bbjwz/agentstandards#11
-
Bundle README: https://github.com/bbjwz/agentstandards/blob/v0.1.1/bundles/agentstandards/README.md
Ready for maintainer re-review.
-
- addedbundle-submissionCommunity bundle catalog submissionCommunity bundle catalog submissionand removedbundle-submissionCommunity bundle catalog submissionCommunity bundle catalog submissionauthor-awaitingWaiting on author responseWaiting on author response
on Sep 25, 2026 - added a commit that references this issue
on Sep 25, 2026 github-actions commented
on Sep 25, 2026 on Sep 25, 2026 – with GitHub ActionsContributorMore actionsPull request created: #4751
Generated by Add Community Bundle from Issue Submission · copilot · gpt52codex · 2.75 AIC · ⌖ 14.1 AIC · ⊞ 24K
- added a commit that references this issue
on Sep 25, 2026
Bundle ID
agentstandards
Bundle Name
Agentstandards Multi-Vendor Architecture
Version
0.1.1
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.1/agentstandards-bundle-0.1.1.zip
Documentation URL
https://github.com/bbjwz/agentstandards/blob/v0.1.1/bundles/agentstandards/README.md
License
MIT
Required Spec Kit Version
Integration Target (optional)
codex
Components Provided
agentstandards@0.1.1agentstandards-gate@0.1.1agentstandards-architecture@0.1.1Required Component Catalogs
Tags
architecture, governance, multi-vendor, codex
Key Features
Testing Checklist
specify bundle validate --path <bundle-directory>specify bundle build --path <bundle-directory>and produces the submitted artifactSubmission Requirements
bundle.ymlmanifest includedTesting Details
Tested on:
Test projects: Clean Spec Kit Codex projects created specifically for release verification.
Test scenarios:
bundles/agentstandardswith the official Spec Kit bundle validator.specify bundle build --path bundles/agentstandards.install-allowedpolicy and installedagentstandardsby bundle ID in another clean Spec Kit 1.0.10 project.The monorepo release builder uses a distinct
agentstandards-bundle-0.1.1.zipfilename 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
Proposed Catalog Entry
{ "agentstandards": { "name": "Agentstandards Multi-Vendor Architecture", "id": "agentstandards", "version": "0.1.1", "role": "architecture-governance", "description": "Installs a Codex-orchestrated, multi-vendor architecture council, its hard task gate, and the supporting Spec Kit workflow.", "author": "bbjwz", "license": "MIT", "download_url": "https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-bundle-0.1.1.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.1 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.
SHA-256
0306cdc780f4107e6702cd25680afede8acea866dfbb0ba81f9ea9c8f960a9dc