Skip to content

Latest commit

 

History

History
86 lines (67 loc) · 3.87 KB

CHANGELOG.md

File metadata and controls

86 lines (67 loc) · 3.87 KB

Changelog

All notable changes to the Superpowers Bridge extension will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.0.2] - 2026-08-07

Fixed

  • v1.0.1 could not be installed via specify extension add superspec. The catalog downloads GitHub's generated tag ZIP, and spec-kit validates it before extracting (_download_security.py: 10 MiB per member, 50 MiB total, 512 entries). assets/workflow-overview-en.png is ~12 MiB, so the install aborted with ZIP member ... exceeds maximum size of 10485760 bytes (issue #6). The archive now ships only the runtime payload: 0.04 MiB downloaded, 25 entries, largest member 0.02 MiB.

Changed

  • .gitattributes marks documentation media (assets/), samples (examples/), development tooling (scripts/) and CI (.github/) as export-ignore, so git archive — and therefore GitHub's tag ZIP — omits them. The repository, the rendered README images and --dev installs are unchanged; nothing was deleted or recompressed.
  • Documentation now uses spec-kit's real specs/NNN-*/ feature layout instead of .specify/specs/.

CI / Tooling

  • scripts/validate-release-archive.py rebuilds the published archive and fails CI when it approaches any spec-kit install limit, loses a file extension.yml declares, or regains an export-ignored path.
  • Structural and AI-driven end-to-end tests (scripts/e2e-smoke.sh, scripts/e2e-agent-claude.sh) verify a real spec-kit install.

[1.0.1] - 2026-05-30

Changed

  • Catalog namespace alignment (BREAKING for command names):
    • extension.id renamed from superpowers to superspec (matches repository name and the catalog id required by spec-kit's registry validator).
    • All command names migrated: /speckit.superpowers.{status,brainstorm,tasks,execute,review} → /speckit.superspec.{status,brainstorm,tasks,execute,review}.
    • All three lifecycle hooks (after_tasks, before_implement, after_implement) now point to the new speckit.superspec.* commands.
    • README catalog install command updated to specify extension add superspec.

Fixed

  • v1.0.0 could not be installed via specify extension add superpowers-bridge due to a mismatch between the catalog id and the command namespace (Validation Error: Command 'speckit.superpowers.status' must use extension namespace 'superpowers-bridge'). v1.0.1 fixes this by aligning the namespace with the (renamed) catalog id.

CI / Tooling

  • scripts/validate-extension-metadata.py rewritten to derive the expected namespace dynamically from extension.yml's id, so future namespace/slug drift fails CI before reaching the catalog. New checks:
    • every commands[].name and every hooks[].command must start with speckit.<extension.id>.;
    • the README catalog install command's slug must equal extension.id;
    • docs must not retain legacy speckit.superpowers.* references.

[1.0.0] - 2026-04-22

Added

  • Extension manifest (extension.yml) for spec-kit extension registry
  • 5 superpowers-bridge commands: status, brainstorm, tasks, execute, review
  • 3 lifecycle hooks: after-tasks, before-execute, after-execute
  • 5 enhanced templates: constitution, spec, plan, tasks, checklist
  • Session resumability via progress.yml and superpowers.yml
  • Superpowers detection with graceful fallback when skills not installed
  • Built-in brainstorming protocol (5 categories) as fallback for superpowers
  • Built-in code review checklist as fallback for requesting-code-review
  • TDD/REVIEW/SUBAGENT execution markers in task templates
  • Bilingual documentation (English + Chinese)
  • Architecture diagrams for both EN and CN
  • Reference documentation: workflow guide and superpowers bridge
  • End-to-end sample workflow example