docs: move extension API reference into documentation (#5174)

* docs: move extension API reference into documentation

Assisted-by: GitHub Copilot (model: GPT-6.1 Sol, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* fix: bump bundled extensions for documentation updates

Assisted-by: GitHub Copilot (model: GPT-6.1 Sol, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* fix: align bugfix bundle with updated bug extension

Assisted-by: GitHub Copilot (model: GPT-6.1 Sol, autonomous)
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: mnriem

bundles/bugfix/bundle.yml

@@ -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"

bundles/catalog.json

@@ -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",

extensions/EXTENSION-API-REFERENCE.md docs/extensions/api.mdextensions/EXTENSION-API-REFERENCE.md renamed to docs/extensions/api.md

@@ -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
 

docs/toc.yml

@@ -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.

extensions/bug/README.md

@@ -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

extensions/bug/extension.yml

@@ -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",

extensions/catalog.json

@@ -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

extensions/github/README.md

@@ -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

extensions/github/extension.yml

@@ -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)