mnriem · Oct 29, 2026 · Oct 29, 2026 · Oct 29, 2026 · Oct 29, 2026
@@ -3,7 +3,7 @@ schema_version: "1.0"
 bundle:
   id: "bugfix"
   name: "Guided Bug Fix"
-  version: "1.0.1"
+  version: "1.0.2"
   role: "developer"
   description: "Orchestrated bug triage: assess a bug report, review the assessment behind a human gate, apply the fix, and verify it with tests."
   author: "GitHub"
@@ -17,7 +17,7 @@ requires:
 provides:
   extensions:
     - id: "bug"
-      version: "1.0.1"
+      version: "1.0.2"
   workflows:
     - id: "bugfix"
       version: "1.0.0"

@@ -6,7 +6,7 @@
     "bugfix": {
       "id": "bugfix",
       "name": "Guided Bug Fix",
-      "version": "1.0.1",
+      "version": "1.0.2",
       "role": "developer",
       "description": "Orchestrated bug triage: assess a bug report, review behind a human gate, apply the fix, and verify with tests.",
       "author": "GitHub",

@@ -143,6 +143,8 @@
       href: extensions/overview.md
     - name: Developing
       href: extensions/developing.md
+    - name: API Reference
+      href: extensions/api.md
     - name: Publishing
       href: extensions/publishing.md
 

@@ -99,4 +99,4 @@ hooks:
       description: Collect evidence in the resolved bug directory
 ```
 
-Mandatory hooks are invoked and awaited; optional hooks are presented for the user to run. Disabled hooks and hooks with non-empty conditions are skipped by the command templates. With no registered hooks, the workflow proceeds as before. See the [Extension API Reference](../EXTENSION-API-REFERENCE.md#hook-events) for the shared hook contract.
+Mandatory hooks are invoked and awaited; optional hooks are presented for the user to run. Disabled hooks and hooks with non-empty conditions are skipped by the command templates. With no registered hooks, the workflow proceeds as before. See the [Extension API Reference](https://github.github.io/spec-kit/extensions/api.html#hook-events) for the shared hook contract.
@@ -3,7 +3,7 @@ schema_version: "1.0"
 extension:
   id: bug
   name: "Bug Triage Workflow"
-  version: "1.0.1"
+  version: "1.0.2"
   description: "Assess, fix, and validate bug reports against the codebase with per-bug reports stored under .specify/bugs/<slug>/"
   author: spec-kit-core
   repository: https://github.com/github/spec-kit

@@ -36,7 +36,7 @@
     "bug": {
       "name": "Bug Triage Workflow",
       "id": "bug",
-      "version": "1.0.1",
+      "version": "1.0.2",
       "description": "Assess, fix, and validate bug reports against the codebase with per-bug reports stored under .specify/bugs/<slug>/",
       "author": "spec-kit-core",
       "repository": "https://github.com/github/spec-kit",
@@ -66,7 +66,7 @@
     "github": {
       "name": "GitHub Integration",
       "id": "github",
-      "version": "1.0.3",
+      "version": "1.0.4",
       "description": "GitHub platform integration for Spec Kit - create GitHub issues from a feature's task list",
       "author": "spec-kit-core",
       "repository": "https://github.com/github/spec-kit",

@@ -130,7 +130,7 @@ If an extension proposal or external dependency declaration uses
 `speckit.github.taskstoissues`. `requires.commands` is not an enforced dependency
 field in the current extension manifest API, so do not rely on that declaration
 to install or check the GitHub extension. Follow the supported requirements in
-the [extension API reference](../EXTENSION-API-REFERENCE.md#extension-manifest).
+the [extension API reference](https://github.github.io/spec-kit/extensions/api.html#extension-manifest).
 
 Preset command overrides are separate from command references: an override of
 `speckit.taskstoissues` does not automatically customize the namespaced GitHub

@@ -3,7 +3,7 @@ schema_version: "1.0"
 extension:
   id: github
   name: "GitHub Integration"
-  version: "1.0.3"
+  version: "1.0.4"
   description: "GitHub platform integration for Spec Kit - create GitHub issues from a feature's task list"
   author: spec-kit-core
   repository: https://github.com/github/spec-kit

@@ -68,7 +68,7 @@ Starter template for creating a Spec Kit extension.
 ## Need Help?
 
 - **Development Guide**: See [Extension Development Guide](https://github.github.io/spec-kit/extensions/developing.html)
-- **API Reference**: See EXTENSION-API-REFERENCE.md
+- **API Reference**: See the [Extension API Reference](https://github.github.io/spec-kit/extensions/api.html)
 - **Publishing Guide**: See the [Extension Publishing Guide](https://github.github.com/spec-kit/extensions/publishing.html)
 - **User Guide**: See the [Extension User Guide](https://github.github.io/spec-kit/extensions/overview.html)
 

@@ -81,7 +81,7 @@ def test_assess_ensures_bug_directory_before_hook_checks():
 
 
 @pytest.mark.parametrize("path", [
-    ROOT / "extensions/EXTENSION-API-REFERENCE.md",
+    ROOT / "docs/extensions/api.md",
     ROOT / "docs/extensions/developing.md",
     ROOT / "docs/extensions/overview.md",
     EXT_DIR / "README.md",

@@ -158,7 +158,7 @@ def test_manifest_validates(self):
 
         m = ExtensionManifest(EXT_DIR / "extension.yml")
         assert m.id == "github"
-        assert m.version == "1.0.3"
+        assert m.version == "1.0.4"
         assert [c["name"] for c in m.commands] == [COMMAND_NAME]
 
     def test_manifest_command_files_exist(self):

@@ -8777,7 +8777,7 @@ def test_hook_condition_returns_false_without_raising(self, tmp_path):
 class TestConfigManagerTopLevelManifestDefaults:
     """A top-level `defaults:` in extension.yml must be loaded (#5084).
 
-    The extension template and EXTENSION-API-REFERENCE.md put defaults under a
+    The extension template and docs/extensions/api.md put defaults under a
     top-level ``defaults:`` key, but ``_get_extension_defaults`` only read
     ``config.defaults``, so an extension built from the template silently had
     no defaults at runtime.