[Bundle]: Add SpecAssay (update to 0.5.2)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 65/100
Línea de trabajo
Esta es una solicitud para actualizar una entrada existente del catálogo de bundles para SpecAssay de la versión 0.4.12 a la 0.5.2. El trabajo implica actualizar el archivo JSON del catálogo con los nuevos detalles de la versión, el hash SHA256 y cualquier metadato modificado. Comience localizando el archivo del catálogo de bundles (probablemente en un directorio como catalogs/). Verifique la entrada existente para 'specassay' y actualice la versión, download_url, sha256 y cualquier otro campo modificado según el bloque JSON proporcionado. Pruebe ejecutando los comandos de validación de bundles mencionados en el issue para asegurarse de que la entrada del catálogo sea correcta.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bundle ID
specassay
Bundle Name
SpecAssay
Version
0.5.2
Role or Team
developer
Description
Durable-ID promotion for stock Spec Kit: templates, Gate 2 refusal, and trace-manifest emission.
Author
Rik Dryfoos
Repository URL
https://github.com/rdryfoos/specassay
Download URL
https://github.com/rdryfoos/specassay/releases/download/v0.5.2/specassay-0.5.2.zip
Documentation URL
https://github.com/rdryfoos/specassay/blob/main/README.md
License
MIT
Required Spec Kit Version
=0.14.0,<2.0.0
Integration Target (optional)
No response
Components Provided
- extensions: specassay-check@0.5.2
- presets: specassay@0.5.2
- workflows: none
- steps: none
Required Component Catalogs
The three SpecAssay catalogs, added as install-allowed, because the community
catalog is discovery-only and cannot install:
specify preset catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/presets.json --name specassay --install-allowed
specify extension catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/extensions.json --name specassay --install-allowed
specify bundle catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/bundles.json --id specassay --policy install-allowed
Both components can alternatively be installed directly with
specify extension add ... --from <url> and specify preset add ... --from <url>.
Tags
traceability, governance, durable-ids, gate, sdd
Key Features
- One install provisions the whole thread: templates that mint durable IDs, and the Gate that refuses a silent gap
- Registry, specs and tasks must agree as an exact set; drift fails rather than passing quietly
- Emits a trace-manifest any viewer can read, so proof is a file rather than a claim
- Components are pinned to matching versions, so a partial upgrade cannot leave the bundle half-resolved
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.ymlmanifest included - README.md explains the bundle's intended role, installed components, and installation steps
- LICENSE file included
- GitHub release created with a 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
This updates the existing catalog entry from 0.4.12 to 0.5.2, superseding
issue #4255 (merged as catalog PR #4257). Neither v0.4.13 nor v0.5.0 was ever
filed, so this carries three releases of change.
Tested on: Linux, Spec Kit 1.0.5, Python 3.11.15, on 2026-09-23, against the
published v0.5.2 assets in a clean project.
sha256 of the submitted artifact, computed from the published v0.5.2 assets on 2026-09-23:
$ curl -fsSL -O https://github.com/rdryfoos/specassay/releases/download/v0.5.2/specassay-0.5.2.zip
$ sha256sum specassay-0.5.2.zip
a9acd0848132bee975be7ca6759a531ff02b736c99a98b1bc4e7d8da90da7c82 specassay-0.5.2.zip
Component digests, same run:
f481c6794d0cffc6d532721c1acc378287ba291b3e74dbe1e54eef083d1e7a20 specassay-check-0.5.2.zip
9920daf8b7ebe2d5e0d5e723409719afeaaa7c59788a6f3ecda67e2f7543d0b9 specassay-preset-0.5.2.zip
Test scenarios, clean project:
$ specify init . --here --force --non-interactive --integration claude
$
$ specify bundle install specassay
Installed 'specassay' (2 added, 0 already present).
$ specify bundle list
specassay v0.5.2 (2 components, installed 2026-09-23T17:41:00Z)
$ specify preset list
SpecAssay (specassay) v0.5.2 - enabled - priority 10
$ specify extension list
SpecAssay Check (v0.5.2)
All three resolve 0.5.2 on the first try. A thread was then driven from an
empty registry through mint, the Gate's honest refusal, and a clear to green as
tracked debt.
Example Usage
# Add the three SpecAssay catalogs as install-allowed (community is discovery-only)
specify preset catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/presets.json --name specassay --install-allowed
specify extension catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/extensions.json --name specassay --install-allowed
specify bundle catalog add https://raw.githubusercontent.com/rdryfoos/specassay/main/catalogs/bundles.json --id specassay --policy install-allowed
# Install the bundle
specify bundle install specassay
# Mint an ID at intent, then let the Gate refuse anything unproven
/speckit.specassay-check.mint AC LOGIN "Given a wrong password, when the user signs in, then the form shows an error."
/speckit.specassay-check.gate
Proposed Catalog Entry
{
"specassay": {
"name": "SpecAssay",
"id": "specassay",
"version": "0.5.2",
"role": "developer",
"description": "Durable-ID promotion for stock Spec Kit: templates, Gate 2 refusal, and trace-manifest emission.",
"author": "Rik Dryfoos",
"license": "MIT",
"download_url": "https://github.com/rdryfoos/specassay/releases/download/v0.5.2/specassay-0.5.2.zip",
"sha256": "a9acd0848132bee975be7ca6759a531ff02b736c99a98b1bc4e7d8da90da7c82",
"repository": "https://github.com/rdryfoos/specassay",
"requires": {
"speckit_version": ">=0.14.0,<2.0.0"
},
"provides": {
"extensions": 1,
"presets": 1,
"steps": 0,
"workflows": 0
},
"tags": ["traceability", "governance", "durable-ids", "gate", "sdd"],
"verified": false
}
}
Additional Context
Update to an existing entry.
Replaces #4692 which was filed at 0.5.1 before v0.5.2 shipped.
Companion issues: the extension and the preset filed just before this one; the bundle pins both component versions, so all three land together:
https://github.com/github/spec-kit/issues/4713
https://github.com/github/spec-kit/issues/4711
- Lenguaje dominante
- Python
- Estrellas
- 138k
- Forks
- 12.4k
- Merge medio
- 3 d 4 h
- PR fusionados (30 d)
- 154
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
preset-submission triage-must-have validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
extension-submission triage-must-have validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
extension-submission triage-can-wait validation-passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
[Feature]: 给 slug 添加默认值 Abiertoenhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
extension-submission triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Todos los issues de github/spec-kit
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#30750 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100