[Preset]: Update Intake Authoring Governance to v0.3.4
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Bereich
- backend-api-design, tooling
Rechercherichtung
The issue is to update an existing preset in the spec-kit catalog from version 0.3.1 to 0.3.4. Start by examining the preset catalog structure in the repository, likely under a directory like 'presets' or 'catalog'. Look for the existing entry for 'intake-authoring-governance'. The update involves validating the new version's features, such as archive placement and lifecycle checks, and ensuring the preset.yml manifest and templates are correctly integrated. Test by installing the preset via specify preset add and verifying template resolution. The work requires understanding the spec-kit preset system and possibly the preset's own repository structure.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Preset ID
intake-authoring-governance
Preset Name
Intake Authoring Governance
Version
0.3.4
Description
Governs traceable intake CRUD, language-aware requirements collections, bounded public HTTPS sources, and explicitly approved single or series authoring.
Author
Thorsten Hindermann
Repository URL
https://github.com/hindermath/spec-kit-preset-intake-authoring-governance
Download URL
Documentation URL
https://github.com/hindermath/spec-kit-preset-intake-authoring-governance/blob/v0.3.4/README.md
License
MIT
Required Spec Kit Version
=0.8.3
Required Extensions (optional)
None
Templates Provided
- intake-authoring-governance-model-routing — agent-neutral command-to-role contract.
- intake-governance-config-template — language, naming, roles and collections.
- intake-governance-migration-journal-template — hash-bound migration and rollback evidence.
- intake-authoring-policy-template — target paths, profiles and overwrite protection.
- intake-authoring-receipt-template — lifecycle receipt.
- intake-authoring-series-template — approved coverage, ordering, DAG and lineage.
- intake-authoring-operation-template — transactional approval and publication journal.
- intake-authoring-tombstone-template — logical deletion and archive evidence.
- intake-authoring-intake-template — portable intake core.
- intake-authoring-profile-template — repository-owned profile extension.
- intake-authoring-runbook-template — create, update, status and handoff workflow.
- intake-authoring-agent-guidance-addendum-template — agent-neutral guidance.
- intake-authoring-field-validation-summary — validation summary.
Commands Provided
- speckit.intake-create
- speckit.intake-read
- speckit.intake-update
- speckit.intake-delete
- speckit.intake-create-status
Number of Scripts (optional)
9
Tags
intake, authoring, governance, requirements, migration
Key Features
- Update the existing intake-authoring-governance entry from 0.3.1 to 0.3.4; preserve its ID.
- Validate completed-series archive placement, separate physical active-file counts from series counts, and support absent empty active directories in SeriesManifest mode without weakening DirectoryStrict.
- Validate unique hash-bound archive successors for historical receipt targets and repository-file sources without rewriting historical evidence.
- Reject physical collection aliases, unknown lifecycle states and repository path escapes before reading receipt targets or sources.
- Restore valid shipped receipt JSON templates and consistent generator version metadata. Native CI now parses every shipped JSON template.
- Preserve traceable intake CRUD, bounded public HTTPS sources, explicit write authority, language-aware collections and provider-neutral model routing.
- Creating an intake starts no review, implementation, campaign, commit, push or merge. Recommended composition priority remains 64.
Testing Checklist
- Preset installs successfully via
specify preset add - Template resolution works correctly after installation
- Documentation is complete and accurate
- Tested on at least one real project
Submission Requirements
- Valid
preset.ymlmanifest included - Linked README (Documentation URL) explains how to use this preset and includes a valid
specify preset add ...command (preferablyspecify preset add --from <download-url>using the exact download URL) - LICENSE file included
- GitHub release created with version tag
- Preset ID follows naming conventions (lowercase-with-hyphens)
Update and validation evidence
This updates the existing catalog entry, previously submitted through #4118, rather than adding a second preset ID.
- Stable v0.3.4 release.
- Merged source PR #8: native lifecycle checks succeeded on macOS, Linux and Windows.
- Fresh macOS verification on 2026-09-23: installation directly from the submitted tag URL with priority 64; preset info and receipt-template resolution succeeded; all five agent command surfaces were generated. Installed package contents match the independently downloaded tag ZIP.
- Download URL SHA-256:
b08c1128756f7fc56de8deb98f9e1cb859b5f76063b39843e395aaed2b440214. This identifies the submitted GitHub tag archive, not the separately packaged release asset. - Fresh template-integrity test: all seven shipped JSON templates parse and bind release 0.3.4 (exit 0).
- Real-project integration includes TinyPl0 PR #98 and the completed six-repository rollout, which retain the installed Authoring v0.3.4 within the composed governance profile.
- Completed-series lifecycle documentation and boundary hardening.
Counts: 13 template entries, 5 commands, and 9 production script files (6 Bash/PowerShell wrappers and 3 Python implementation/resolution helpers); tests are excluded from the script count. Python 3 is required for configuration and archive-resolution paths, including the corresponding PowerShell wrapper paths.
- Vorherrschende Sprache
- Python
- Sterne
- 138k
- Forks
- 12.4k
- Ø Merge
- 3 T. 2 Std.
- Gemergte PRs (30 T.)
- 169
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus github/spec-kit
-
enhancement needs-triage triage-can-wait
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
-
preset-submission triage-must-have validation-passed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
extension-submission triage-must-have validation-passed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
-
extension-submission triage-can-wait validation-passed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
-
[Feature]: 给 slug 添加默认值 Offenenhancement needs-triage triage-can-wait
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Alle Issues in github/spec-kit
Ähnliche Issues
-
agent-ready documentation needs-triage
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100
-
documentation
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 92/100
-
instance instance add
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 72/100
searxng/searx-instances#939 · 1 Kommentar ·
-
area-deployment area-integrations triage:bot-seen
Schwierigkeit 2/5 Ein halber Tag Anfängerfreundlichkeit 86/100