Spec Kit 0.14 Packages Agent Workflows as Reproducible Bundles and Tightens Remote Catalog Download Boundaries

GitHub released Spec Kit 0.14.0 on July 23 and advanced it to 0.14.2 the following day. The notable change is not a new set of prompts, but further packaging of how specification-driven development components are distributed. A Bundle can use `bundle.yml` to combine extensions, presets, workflows, and steps into a single, versioned ZIP artifact. During installation, it expands pinned versions, checks for integration conflicts, and records the source of each component to support subsequent updates or removal.

Version 0.14.0 also formally introduces the `py` script type, migrating some previously separate Shell and PowerShell workflows to Python. Bundle builds sort members using standard POSIX paths, reducing the likelihood that identical inputs will produce different hashes on different machines. For teams that need to audit agent configurations, run workflows in CI, or maintain consistent specifications across multiple coding agents, reproducible artifacts are easier to sign, cache, and compare for changes than directly copied prompt files.

Security is likewise a central theme of this release cycle. Version 0.14.0 uses size-limited HTTP reads for remote catalogs and validates every redirect to prevent a trusted URL from leading to an unexpected host. Version 0.14.2 goes further by removing the `shell` parameter from `run_command()` and adding failure handling for cases such as malformed hosts and workflow inputs that are not mappings. These fixes do not mean that Bundles have become a complete sandbox. The documentation explicitly states that recovery after failure is best-effort, and partial state may remain on disk. Version pinning is also reapplied only during the initial installation or an explicit update; an existing component with the same name will not have its version compared merely by running `install`.

Engineering teams should next verify that clean and upgraded environments produce identical file trees, and treat community catalogs as part of the software supply chain rather than as ordinary lists of prompts. If a Bundle executes shell commands or agent tools, teams should still enforce containers, network restrictions, and human approval at an outer layer.