chore: bump version to 0.14.1

2026-08-15 14:02:04 +02:00 · 2026-07-23 20:17:39 +00:00
189 changed files with 1872 additions and 37703 deletions
@@ -8,7 +8,7 @@ body:
      value: |
        Thanks for requesting a new agent! Before submitting, please check if the agent is already supported.

-        **Currently supported agents**: Alquimia AI, Amp, Antigravity, Auggie CLI, Claude Code, Cline, CodeBuddy, Codex CLI, Cursor, Devin for Terminal, Factory Droid, Firebender, Forge, Gemini CLI, GitHub Copilot, Goose, Grok Build, Hermes Agent, IBM Bob, Junie, Kilo Code, Kimi Code, Kiro CLI, Lingma, Mistral Vibe, Oh My Pi, opencode, Pi Coding Agent, Qoder CLI, Qwen Code, RovoDev ACLI, SHAI, Tabnine CLI, Trae, ZCode, Zed
+        **Currently supported agents**: Amp, Antigravity, Auggie CLI, Claude Code, Cline, CodeBuddy, Codex CLI, Cursor, Devin for Terminal, Factory Droid, Firebender, Forge, Gemini CLI, GitHub Copilot, Goose, Grok Build, Hermes Agent, IBM Bob, Junie, Kilo Code, Kimi Code, Kiro CLI, Lingma, Mistral Vibe, Oh My Pi, opencode, Pi Coding Agent, Qoder CLI, Qwen Code, RovoDev ACLI, SHAI, Tabnine CLI, Trae, ZCode, Zed

  - type: input
    id: agent-name
@@ -62,7 +62,6 @@ body:
      label: AI Agent
      description: Which AI agent are you using?
      options:
-        - Alquimia AI
        - Amp
        - Antigravity
        - Auggie CLI
@@ -56,7 +56,6 @@ body:
      description: Does this feature relate to a specific AI agent?
      options:
        - All agents
-        - Alquimia AI
        - Amp
        - Antigravity
        - Auggie CLI
@@ -29,20 +29,12 @@ def _dependency_diff_refs() -> tuple[str, str]:
 def _dependency_inputs_changed() -> bool:
    base_ref, head_ref = _dependency_diff_refs()
    try:
-        merge_base = subprocess.run(
-            ["git", "merge-base", base_ref, head_ref],
-            check=True,
-            cwd=REPO_ROOT,
-            stderr=subprocess.PIPE,
-            stdout=subprocess.PIPE,
-            text=True,
-        ).stdout.strip()
        result = subprocess.run(
            [
                "git",
                "diff",
                "--name-only",
-                merge_base,
+                base_ref,
                head_ref,
                "--",
                *DEPENDENCY_INPUTS,
@@ -85,7 +77,6 @@ def main() -> int:

    generated_requirements = Path(generated_requirements_env)
    generated_requirements.parent.mkdir(parents=True, exist_ok=True)
-    generated_requirements.write_bytes(COMMITTED_REQUIREMENTS.read_bytes())

    subprocess.run(
        [
@@ -96,6 +87,7 @@ def main() -> int:
            "--extra",
            "test",
            "--universal",
+            "--upgrade",
            "--generate-hashes",
            "--quiet",
            "--no-header",
@@ -1,6 +1,6 @@
-annotated-doc==0.0.5 \
-    --hash=sha256:117bac03a25ede5df5440e855b32d556049ca169ead221505badf432fed4b101 \
-    --hash=sha256:c7e58ce09192557605d8bbd92836d7e1d520ac9580096042c0bfd197efacf1bb
+annotated-doc==0.0.4 \
+    --hash=sha256:571ac1dc6991c450b25a9c2d84a3705e2ae7a53467b5d111c24fa8baabbed320 \
+    --hash=sha256:fbcda96e87e9c92ad167c2e53839e57503ecfda18804ea28102353485033faa4
    # via typer
 click==8.4.2 \
    --hash=sha256:9a6cea6e60b17ebe0a44c5cc636d94f09bd66142c1cd7d8b4cd731c4917a15f6 \
@@ -33,10 +33,10 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
-#   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+#   - actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
 #   - actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
 #   - github/gh-aw-actions/setup@c0338fef4749d08c21f8f975fb0e37efa17dda47 # v0.79.8
 #
@@ -162,7 +162,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -434,7 +434,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1352,7 +1352,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -1419,7 +1419,7 @@ jobs:
          mkdir -p /tmp/gh-aw/threat-detection
          touch /tmp/gh-aw/threat-detection/detection.log
      - name: Setup Node.js
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
        with:
          node-version: '24'
          package-manager-cache: false
@@ -1678,7 +1678,7 @@ jobs:
            await main();
      - name: Checkout repository (trusted default branch for comment events)
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment')
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
        with:
          ref: ${{ github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -1686,7 +1686,7 @@ jobs:
          fetch-depth: 0
      - name: Checkout repository
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && github.event_name != 'issue_comment' && github.event_name != 'pull_request_review_comment'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
        with:
          ref: ${{ steps.extract-base-branch.outputs.base-branch || github.base_ref || github.event.pull_request.base.ref || github.ref_name || github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -33,7 +33,7 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
 #   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
@@ -162,7 +162,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -434,7 +434,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1332,7 +1332,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -1658,7 +1658,7 @@ jobs:
            await main();
      - name: Checkout repository (trusted default branch for comment events)
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment')
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -1666,7 +1666,7 @@ jobs:
          fetch-depth: 0
      - name: Checkout repository
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && github.event_name != 'issue_comment' && github.event_name != 'pull_request_review_comment'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ steps.extract-base-branch.outputs.base-branch || github.base_ref || github.event.pull_request.base.ref || github.ref_name || github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -33,7 +33,7 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
 #   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
@@ -162,7 +162,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -434,7 +434,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1332,7 +1332,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -1658,7 +1658,7 @@ jobs:
            await main();
      - name: Checkout repository (trusted default branch for comment events)
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment')
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -1666,7 +1666,7 @@ jobs:
          fetch-depth: 0
      - name: Checkout repository
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && github.event_name != 'issue_comment' && github.event_name != 'pull_request_review_comment'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ steps.extract-base-branch.outputs.base-branch || github.base_ref || github.event.pull_request.base.ref || github.ref_name || github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -32,7 +32,7 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
 #   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
@@ -161,7 +161,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -430,7 +430,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1277,7 +1277,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -33,7 +33,7 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
 #   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
@@ -162,7 +162,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -434,7 +434,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1338,7 +1338,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -1664,7 +1664,7 @@ jobs:
            await main();
      - name: Checkout repository (trusted default branch for comment events)
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment')
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -1672,7 +1672,7 @@ jobs:
          fetch-depth: 0
      - name: Checkout repository
        if: (!cancelled()) && needs.agent.result != 'skipped' && contains(needs.agent.outputs.output_types, 'create_pull_request') && github.event_name != 'issue_comment' && github.event_name != 'pull_request_review_comment'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: ${{ steps.extract-base-branch.outputs.base-branch || github.base_ref || github.event.pull_request.base.ref || github.ref_name || github.event.repository.default_branch }}
          token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
@@ -32,7 +32,7 @@
 #   - GITHUB_TOKEN
 #
 # Custom actions used:
-#   - actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+#   - actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 #   - actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
 #   - actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
 #   - actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
@@ -161,7 +161,7 @@ jobs:
        env:
          COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      - name: Checkout .github and .agents folders
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          sparse-checkout: |
@@ -431,7 +431,7 @@ jobs:
            echo "GH_AW_SAFE_OUTPUTS_TOOLS_PATH=${RUNNER_TEMP}/gh-aw/safeoutputs/tools.json"
          } >> "$GITHUB_OUTPUT"
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
          fetch-depth: 0
@@ -1299,7 +1299,7 @@ jobs:
          echo "GH_AW_AGENT_OUTPUT=/tmp/gh-aw/agent_output.json" >> "$GITHUB_OUTPUT"
      - name: Checkout repository for patch context
        if: needs.agent.outputs.has_patch == 'true'
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          persist-credentials: false
      # --- Threat Detection ---
@@ -19,14 +19,14 @@ jobs:
        language: [ 'actions', 'python' ]
    steps:
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

      - name: Initialize CodeQL
-        uses: github/codeql-action/init@d1ba80a13dd99fba24a470575428917156a28b43 # v4
+        uses: github/codeql-action/init@7188fc363630916deb702c7fdcf4e481b751f97a # v4
        with:
          languages: ${{ matrix.language }}

      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@d1ba80a13dd99fba24a470575428917156a28b43 # v4
+        uses: github/codeql-action/analyze@7188fc363630916deb702c7fdcf4e481b751f97a # v4
        with:
          category: "/language:${{ matrix.language }}"
@@ -30,7 +30,7 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          fetch-depth: 0 # Fetch all history for git info

@@ -12,7 +12,7 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          fetch-depth: 1

@@ -37,7 +37,7 @@ jobs:
          fi

      - name: Run markdownlint-cli2
-        uses: DavidAnson/markdownlint-cli2-action@21c1be1b93ad9ed58fa840aacc3f279cde2a72ff # v24.2.0
+        uses: DavidAnson/markdownlint-cli2-action@8de2aa07cae85fd17c0b35642db70cf5495f1d25 # v24.0.0
        with:
          globs: |
            '**/*.md'
@@ -47,7 +47,7 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

      # shellcheck is preinstalled on ubuntu-latest runners.
      # Start at --severity=error to block real bugs without flagging style
@@ -27,15 +27,15 @@ jobs:
          fi

      - name: Checkout release tag
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          ref: refs/tags/${{ inputs.tag }}

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Set up Python
-        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
        with:
          python-version: "3.13"

@@ -74,7 +74,7 @@ jobs:
          path: dist/

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Publish to PyPI
        run: uv publish
@@ -16,7 +16,7 @@ jobs:
      pull-requests: write
    steps:
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          fetch-depth: 0
          token: ${{ secrets.RELEASE_PAT }}
@@ -12,7 +12,7 @@ jobs:
      contents: write
    steps:
      - name: Checkout repository
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          fetch-depth: 0
          token: ${{ secrets.GITHUB_TOKEN }}
@@ -19,22 +19,22 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
        with:
          fetch-depth: 0

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Set up Python
-        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
        with:
          python-version: "3.14"

      - name: Check committed audit requirements are current
        env:
          DEPENDENCY_DIFF_BASE: ${{ github.event.pull_request.base.sha || github.event.before || '' }}
-          DEPENDENCY_DIFF_HEAD: ${{ github.event.pull_request.head.sha || github.sha }}
+          DEPENDENCY_DIFF_HEAD: ${{ github.sha }}
          GENERATED_REQUIREMENTS: ${{ runner.temp }}/security-audit-requirements.txt
        run: python .github/scripts/check_security_requirements.py

@@ -52,13 +52,13 @@ jobs:
        python-version: ["3.11", "3.12", "3.13", "3.14"]
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
        with:
          python-version: ${{ matrix.python-version }}

@@ -14,7 +14,7 @@ jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
+      - uses: actions/stale@1e223db275d687790206a7acac4d1a11bd6fe629 # v10
        with:
          # Days of inactivity before an issue or PR becomes stale
          days-before-stale: 150
@@ -13,13 +13,13 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Set up Python
-        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
        with:
          python-version: "3.14"

@@ -34,13 +34,13 @@ jobs:
        python-version: ["3.13", "3.14"]
    steps:
      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

      - name: Install uv
-        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        uses: astral-sh/setup-uv@11f9893b081a58869d3b5fccaea48c9e9e46f990 # v8.3.2

      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6
        with:
          python-version: ${{ matrix.python-version }}

@@ -10,20 +10,6 @@ The toolkit supports multiple AI coding assistants, allowing teams to use their

 ---

-## Quickstart — Add a New Integration in 5 Steps
-
-If you are new to the codebase and want to add support for a new AI agent, here is the shortest path from zero to a working integration:
-
-1. **Choose a base class** — most agents only need `MarkdownIntegration`. See [Choose a base class](#1-choose-a-base-class).
-2. **Create a subpackage** — add `src/specify_cli/integrations/<package_dir>/__init__.py` with the required `key`, `config`, and `registrar_config` fields.
-3. **Register it** — add one import and one `_register()` call in `src/specify_cli/integrations/__init__.py` (both alphabetical).
-4. **Write a test file** — create `tests/integrations/test_integration_<key>.py` (hyphens in the key become underscores in the filename).
-5. **Run and verify** — use `specify init --integration <key>` to exercise the full install/uninstall cycle.
-
-Each step is expanded under [Adding a New Integration](#adding-a-new-integration). Note that agent **context files** (`CLAUDE.md`, `AGENTS.md`, …) are **not** handled by the integration — that is owned by the opt-in `agent-context` extension; see [Context file behavior](#4-context-file-behavior).
-
---
-
 ## Integration Architecture

 Each AI agent is a self-contained **integration subpackage** under `src/specify_cli/integrations/<key>/`. The subpackage exposes a single class that declares all metadata and inherits setup/teardown logic from a base class. Built-in integrations are then instantiated and added to the global `INTEGRATION_REGISTRY` by `src/specify_cli/integrations/__init__.py` via `_register_builtins()`.
@@ -48,30 +34,6 @@ The registry is the **single source of truth for Python integration metadata**.

 ---

-## IntegrationManifest — File Tracking
-
-`manifest.py` provides the `IntegrationManifest` class, which records every file an integration installs. This record is what makes uninstall reliable and safe.
-
-### How it works
-
-`setup()` receives an `IntegrationManifest` and writes files through it rather than touching the filesystem directly:
-
-```python
-# Produce a new file and record its hash for later verification.
-manifest.record_file("commands/speckit.plan.md", processed_content)
-
-# Adopt a pre-existing file the integration is now responsible for.
-manifest.record_existing(".vscode/settings.json")
-```
-
-The manifest is persisted at `.specify/integrations/<key>.manifest.json` (one per integration, keyed by `key`) and stores a SHA-256 hash per file. When the user runs `specify integration uninstall <key>`, `teardown()` delegates to `manifest.uninstall()`, which removes only files whose current hash still matches the recorded value — so files the user later edited by hand are skipped, not clobbered (use `specify integration uninstall <key> --force` to remove modified tracked files anyway).
-
-### Why this matters
-
-Without hash-tracked manifests, uninstall would either remove files it should not (destructive) or leave orphans behind (messy). If you write a custom `setup()`, route **every** file you create through `manifest.record_file(...)` (or `record_existing(...)` for files you adopt) so uninstall can reason about them.
-
---
-
 ## Adding a New Integration

 ### 1. Choose a base class
@@ -102,14 +64,13 @@ class KilocodeIntegration(MarkdownIntegration):
    key = "kilocode"
    config = {
        "name": "Kilo Code",
-        "folder": ".kilo/",
-        "commands_subdir": "commands",
+        "folder": ".kilocode/",
+        "commands_subdir": "workflows",
        "install_url": None,
        "requires_cli": False,
    }
    registrar_config = {
-        "dir": ".kilo/commands",
-        "legacy_dir": ".kilocode/workflows",
+        "dir": ".kilocode/workflows",
        "format": "markdown",
        "args": "$ARGUMENTS",
        "extension": ".md",
@@ -240,8 +201,8 @@ Only add custom setup logic when the agent needs non-standard behavior. Integrat
 specify init my-project --integration <key>

 # Verify files were created in the commands directory configured by
-# config["folder"] + config["commands_subdir"] (for example, .kilo/commands/)
-ls -R my-project/.kilo/commands/
+# config["folder"] + config["commands_subdir"] (for example, .kilocode/workflows/)
+ls -R my-project/.kilocode/workflows/

 # Uninstall cleanly
 cd my-project && specify integration uninstall <key>
@@ -260,13 +221,13 @@ The base classes handle most work automatically. Override only when the agent de
 | Override | When to use | Example |
 |---|---|---|
 | `command_filename(template_name)` | Custom file naming or extension | Copilot → `speckit.{name}.agent.md` |
-| `options()` | Integration-specific CLI flags via `--integration-options` | Codex → `--skills` flag, Copilot → `--commands` flag |
-| `setup()` | Custom install logic (companion files, settings merge) | Copilot → `speckit-<name>/SKILL.md` (default) or `.agent.md` + `.prompt.md` + `.vscode/settings.json` (`--commands`) |
+| `options()` | Integration-specific CLI flags via `--integration-options` | Codex → `--skills` flag, Copilot → `--skills` flag |
+| `setup()` | Custom install logic (companion files, settings merge) | Copilot → `.agent.md` + `.prompt.md` + `.vscode/settings.json` (default) or `speckit-<name>/SKILL.md` (skills mode) |
 | `teardown()` | Custom uninstall logic | Rarely needed; base handles manifest-tracked files |

 **Example — Copilot (fully custom `setup`):**

-Copilot extends `IntegrationBase` directly because it supports two layouts. It scaffolds `speckit-<name>/SKILL.md` under `.github/skills/` by default using composition with an internal `_CopilotSkillsHelper`. Its `--commands` mode creates `.agent.md` commands, companion `.prompt.md` files, and merges `.vscode/settings.json`. See `src/specify_cli/integrations/copilot/__init__.py` for the full implementation.
+Copilot extends `IntegrationBase` directly because it creates `.agent.md` commands, companion `.prompt.md` files, and merges `.vscode/settings.json`. It also supports a `--skills` mode that scaffolds `speckit-<name>/SKILL.md` under `.github/skills/` using composition with an internal `_CopilotSkillsHelper`. See `src/specify_cli/integrations/copilot/__init__.py` for the full implementation.

 ### 7. Update Devcontainer files (Optional)

@@ -415,28 +376,36 @@ Some agents require custom processing beyond the standard template transformatio

 ### Copilot Integration

-GitHub Copilot uses skills by default, scaffolded as
-`speckit-<name>/SKILL.md` under `.github/skills/`.
+GitHub Copilot has unique requirements:

-**Commands mode (`--commands`):** Copilot also supports a commands-based layout
-via `--integration-options="--commands"`. When enabled:
-
- Commands use `.agent.md` extension under `.github/agents/`
+- Commands use `.agent.md` extension (not `.md`)
 - Each command gets a companion `.prompt.md` file in `.github/prompts/`
- `.vscode/settings.json` is merged with prompt file recommendations
- `build_command_invocation()` returns bare args for `--agent` dispatch
+- Installs `.vscode/settings.json` with prompt file recommendations
+- Context file lives at `.github/copilot-instructions.md`

-In the default skills mode, no companion prompts or VS Code settings merge are
-created, and `build_command_invocation()` returns `/speckit-<stem>`.
+Implementation: Extends `IntegrationBase` with custom `setup()` method that:
+
+1. Processes templates with `process_template()`
+2. Generates companion `.prompt.md` files
+3. Merges VS Code settings
+
+**Skills mode (`--skills`):** Copilot also supports an alternative skills-based layout
+via `--integration-options="--skills"`. When enabled:
+
+- Commands are scaffolded as `speckit-<name>/SKILL.md` under `.github/skills/`
+- No companion `.prompt.md` files are generated
+- No `.vscode/settings.json` merge
+- `post_process_skill_content()` injects a `mode: speckit.<stem>` frontmatter field
+- `build_command_invocation()` returns `/speckit-<stem>` instead of bare args

 The two modes are mutually exclusive — a project uses one or the other:

 ```bash
-# Default skills mode: speckit-<name>/SKILL.md under .github/skills/
+# Default mode: .agent.md agents + .prompt.md companions + settings merge
 specify init my-project --integration copilot

-# Commands mode: .agent.md agents + .prompt.md companions + settings merge
-specify init my-project --integration copilot --integration-options="--commands"
+# Skills mode: speckit-<name>/SKILL.md under .github/skills/
+specify init my-project --integration copilot --integration-options="--skills"
 ```

 ### Forge Integration
@@ -501,11 +470,6 @@ When an issue exists, include its number immediately after the prefix — this i

 Disclosure is **continuous**, not a one-time event. A single AI-disclosure paragraph in the PR body does **not** cover the commits and replies you add during review rounds. Each of the following must independently attest to agent authorship.

-### Opening pull requests
-
- Before opening a pull request, check whether the account that will file it already has three open pull requests in this repository.
- If so, alert the user that additional submissions may receive lower review priority and ask for explicit permission to proceed. Do not assume consent.
-
 ### Commits

 - **Every commit you author must carry an `Assisted-by:` trailer** identifying the agent and whether it acted autonomously or under direct human supervision, for example:
@@ -546,54 +510,4 @@ Disclosure is **continuous**, not a one-time event. A single AI-disclosure parag

 ---

-## Error Handling and Debugging
-
-### Common Errors and Fixes
-
-| Symptom | Likely Cause | Fix |
-|---|---|---|
-| `Integration '<key>' not found` | Missing `_register()` call | Add `_register(<Name>Integration())` inside `_register_builtins()` |
-| `NameError: name '<Name>Integration' is not defined` at startup | Missing import | Add `from .<package_dir> import <Name>Integration` inside `_register_builtins()` |
-| CLI check fails for a `requires_cli: True` agent | `key` does not match the executable name | Set `key` to the exact name `shutil.which(key)` must resolve (e.g. `"cursor-agent"`, not `"cursor"`) |
-| Command files have the wrong argument syntax | Wrong `args` value in `registrar_config` | Use `$ARGUMENTS` for Markdown agents, `{{args}}` for TOML/YAML agents, or the agent's custom placeholder |
-| `ModuleNotFoundError` on a brand-new subpackage under pytest only | Ambient interpreter with a stale editable `.pth` | Run inside this tree's own venv (see Common Pitfall 6) |
-| Uninstall leaves files behind, or skips files you expected removed | Files not recorded via the manifest, or their hash changed after install | Route every created file through `manifest.record_file(...)`; user-edited files are intentionally skipped unless `force=True` |
-| Context file (`CLAUDE.md`, etc.) not updated | Expecting the CLI to manage it | Context files are owned by the opt-in `agent-context` extension, not the integration — see [Context file behavior](#4-context-file-behavior) |
-
-### Debugging Tips
-
-**Inspect the manifest** to see what an installed integration tracks:
-
-```bash
-cat .specify/integrations/<key>.manifest.json
-```
-
-**Verify a CLI tool is detected** before debugging a `requires_cli` agent:
-
-```bash
-which <key>        # Should print the executable path if installed
-```
-
-**Verify the installed output structure** after `specify init`:
-
-```bash
-find my-project/<folder> -type f
-```
-
---
-
-## Contribution Checklist
-
-Before opening or merging an integration PR, confirm the following:
-
- [ ] Added the integration subpackage under `src/specify_cli/integrations/<package_dir>/`.
- [ ] Registered it (import **and** `_register()`) in `src/specify_cli/integrations/__init__.py`, both alphabetical.
- [ ] Added or updated tests in `tests/integrations/test_integration_<key>.py`.
- [ ] Verified the install/uninstall flow with `specify init --integration <key>`.
- [ ] Did **not** add `context_file` handling to the CLI (that belongs to the `agent-context` extension).
- [ ] Updated devcontainer files if the agent needs a VS Code extension or CLI install step.
- [ ] Updated this guide or other relevant docs if the integration has special setup or limitations.
-
---
-
 *This documentation should be updated whenever new integrations are added to maintain accuracy and completeness.*
@@ -2,225 +2,6 @@

 <!-- insert new changelog below this comment -->

-## [0.16.1] - 2026-08-07
-
-### Changed
-
- fix(integrations): wrap a non-UTF-8 catalog response (#4011)
- fix(events): skip an unreadable command template (#3956)
- fix(bundle): wrap malformed YAML in a local .zip bundle manifest (#4013)
- chore(deps): bump github/codeql-action/analyze from 4.37.3 to 4.37.5 (#4005)
- chore(deps): bump DavidAnson/markdownlint-cli2-action (#4006)
- fix(agent-context): recurse for nested plans in Python mtime fallback (#3757)
- fix: add utf-8 encoding to extension and preset registry file I/O (#3834)
- fix(init): escape user-supplied values in `specify init` output (#3787)
- fix: bound response read in integration catalog fetch (#3812)
- fix: use missing_ok for temp file cleanup to avoid masking errors (#3803)
- fix(workflows): handle an unreadable run state in `workflow status` (#3999)
- feat(init): scaffold managed .specify/.gitignore (#4000)
- fix(scripts): stop check-prerequisites text mode crashing on a legacy stdout code page (#3890)
- fix(presets): return None for an unreadable layer in resolve_content (#3959)
- fix(extensions): start fresh on a non-UTF-8 extension registry (#3998)
- Fix init-force-preset-desync: reapply presets/extensions on init --here --force (#3995)
- fix(skills): apply the line-anchored delimiter scan to hermes and kimi (#3739)
- fix(archives): wrap the bare EOFError a truncated tar.gz raises (#3938)
- test(integrations): guard multiline/control-char SKILL.md frontmatter escaping (#3392)
- fix(scripts): stop setup-tasks text mode crashing on a legacy code page (#3892)
- chore: release 0.16.0, begin 0.16.1.dev0 development (#3992)
-
-## [0.16.0] - 2026-08-05
-
-### Changed
-
- fix: keep long frontmatter values on a single line (#3989)
- fix: skip corrupted run state files in list_runs (#3817)
- fix: skip corrupted run state files in list_runs (#3814)
- Add July 2026 newsletter (#3987)
- fix(presets): start fresh on a non-UTF-8 preset registry (#3955)
- docs: clarify agent PR review prioritization (#3985)
- fix(events): preserve a non-UTF-8 config.toml on hook install/teardown (#3963)
- fix(extensions): treat an unreadable staged backup as a conflict (#3962)
- fix(manifests): reject non-string requires.speckit_version (#3980)
- fix(extensions): reject reinstall when a kept config cannot be read (#3960)
- [extension] Update Charter extension to v0.5.1 (#3983)
- fix(events): return None for an unparseable script command (#3957)
- feat(events): context injection for opencode and JSON-envelope agent hooks (#3934)
- Add TDD Extension to community catalog (#3982)
- Update Archive Extension to v1.1.0 (#3981)
- feat(copilot): default integration to skills (#3976)
- fix(events): ignore non-UTF-8 event overrides (#3897)
- fix: cap stdin read at 1 MiB to prevent DoS (#3857)
- fix(workflows): reject mismatched run state IDs (#3899)
- chore: release 0.15.2, begin 0.15.3.dev0 development (#3953)
-
-## [0.15.2] - 2026-08-03
-
-### Changed
-
- fix(presets): restore core skills instead of deleting them on preset remove (#3929)
- fix(manifests): reject non-string metadata instead of crashing on it (#3943)
- fix: narrow bare except Exception in invoke separator resolution (#3856)
- fix(workflows): keep the init step's documented ignore_agent_tools default on an explicit null (#3889)
- fix(kimi): preserve non-UTF-8 user skills (#3895)
- fix(presets): tolerate non-UTF-8 legacy commands (#3896)
- feat: allow overriding default init integration via SPECKIT_INTEGRATION_DEFAULT (#3952)
- Add adrkit extension to community catalog (#3947)
- feat(extensions): scaffold config templates on extension add/enable (#2000)
- fix(events): skip non-UTF-8 extension manifests (#3900)
- fix(workflows): fail a gate whose on_reject is not abort/skip/retry (#3888)
- fix(presets): validate required manifest mappings (#3898)
- fix: eliminate TOCTOU race in zip packaging (#3855)
- fix(workflows): fail a fan-in step whose output is not a mapping (#3887)
- fix(workflows): refetch non-UTF-8 catalog caches (#3901)
- fix(bundler): wrap local catalog decode failures (#3902)
- Add `--extension` flag to `specify init` for opting into extensions at init time (#3914)
- fix: bound response reads in extension catalog and download (#3775)
- fix(workflows): reject a retry gate whose verdict enum forbids the reset value (#3912)
- chore: release 0.15.1, begin 0.15.2.dev0 development (#3913)
-
-## [0.15.1] - 2026-07-31
-
-### Changed
-
- fix: escape Rich markup in `workflow resolve` output (#3879)
- chore(deps): bump actions/stale from 10.4.0 to 11.0.0 (#3877)
- chore(deps): bump actions/setup-python from 6.3.0 to 7.0.0 (#3876)
- feat: support tar archives for installs (#3874)
- fix: eliminate TOCTOU race in file unlink calls (#3819)
- fix(scripts): tolerate an unusable integration.json in the Python helper (#3785)
- fix(catalogs): validate the port in the shared catalog-URL validator, like its mirrors do (#3804)
- feat(presets): add opt-in constitution-sync preset (#3873)
- fix: reject non-object workflow caches (#3860)
- Harden extension URL download cache against symlink and junction races (#3869)
- fix: escape workflow step metadata (#3863)
- [bug-fix] Fix bundle-update-force-mislead: add refresh() to DefaultPrimitiveInstaller (#3452)
- fix: use chunked read for extension manifest hash (#3841)
- fix: preserve unreadable event config files (#3861)
- fix(scripts): use a .NET Framework-safe trim in the PowerShell init-dir resolver (#3872)
- Add ContextForge MCP extension to community catalog (#3487)
- fix: normalize non-UTF-8 integration manifests (#3862)
- feat: bind gate verdict to workflow input via verdict_input (#3725)
- docs: use absolute image URLs in README for PyPI rendering (#3867)
- chore: release 0.15.0, begin 0.15.1.dev0 development (#3871)
-
-## [0.15.0] - 2026-07-30
-
-### Changed
-
- Add yolo to community workflow catalog (#3864)
- fix(workflows): guard the shell step's timeout check against OverflowError (#3865)
- Add Intent Reconciliation extension to community catalog (#3858)
- fix(workflows): validate prompt step 'timeout' like the shell step (#3847)
- fix: add utf-8 encoding to registry file open calls (#3816)
- fix: eliminate TOCTOU race in file unlink calls (#3815)
- test(workflows): name the condition-rejection tests for the real boundary (#3808)
- fix: eliminate TOCTOU race in file unlink calls (#3811)
- fix(presets): escape user-supplied catalog name/URL in add/remove output (#3806)
- fix: add missing utf-8 encoding to registry file open calls (#3810)
- [bug-fix] Fix upgrade-overwrites-copilot-skills: pass force=True to extension skill re-registration after upgrade (#3853)
- fix(integrations): don't abort uninstall when the manifest can't be deleted (#3805)
- test(extensions): update stale manifest validation message assertion (#3859)
- fix(agents): coerce a non-string description in TOML command rendering (#3799)
- fix(workflows): make security requirements sync deterministic (#3832)
- fix(cli): render the literal [suffix] in --tag help and rejection message (#3800)
- fix(integrations): preserve non-UTF-8 VS Code settings (#3833)
- fix(bundler): treat an explicit-null manifest field as missing, not the text "None" (#3798)
- feat: first-class agent-native runtime hooks for integrations (#3704)
- fix(extensions): guard the required manifest sections so one bad extension cannot break `extension list` (#3797)
- fix(presets): escape installed preset metadata in Rich output (#3826)
- fix(workflows): dispatch prompt steps via the resolved executable (#3793)
- chore: release 0.14.4, begin 0.14.5.dev0 development (#3850)
-
-## [0.14.4] - 2026-07-29
-
-### Changed
-
- fix(bundler): degrade non-UTF-8 config reads into BundlerError (#3784)
- fix(workflows): escape the step-progress line so step ids render (and `/` stops failing the run) (#3783)
- Update Agent Parity Governance preset to v0.4.1 (#3830)
- fix(integrations): reject empty --commands-dir in generic raw_options (#3714)
- fix(presets): guard non-list/non-mapping provides.templates in PresetManifest (#3712)
- fix(auth): resolve az via shutil.which so azure-cli token works on Windows (#3709)
- fix(workflows): reject falsy non-mapping workflow-catalogs.yml top level (#3707)
- fix(integrations): render hyphenated /speckit-<name> for Droid (always-slash agent) (#3688)
- [preset] Update A11Y Governance preset to v0.4.2 (#3828)
- [preset] Update Parallel Autonomous Run Governance to v0.2.4 (#3825)
- fix: correct Optional type annotation for _resolved_dir parameter (#3801)
- fix: add timeout to prompt step subprocess execution (#3768)
- fix: handle tags containing / in GitHub release asset URL resolution (#3767)
- fix(presets): escape catalog metadata in discovery output (#3773)
- Update Autonomous Run Governance preset to v0.3.3 (#3823)
- fix: use bounded read for integration catalog HTTP responses (#3763)
- docs: add Simplified Chinese translation of README (#3740)
- Update Intake Sequencing Governance preset to v0.2.2 (#3809)
- fix(workflows): reject non-string/non-boolean 'condition' in if/while/do-while steps (#3706)
- fix(bundle): escape catalog metadata in discovery output (#3774)
- fix(workflows,extensions): tolerate non-list catalog tags in search/info display (#3770)
- fix: correct nullable resolved directory annotation (#3771)
- fix(presets): tolerate non-string and non-list catalog fields in preset search/info (#3769)
- fix(integrations): escape catalog metadata in discovery output (#3772)
- Update Verify Review Ship extension to v0.4.2 (#3792)
- fix(integrations): preserve native skill invocation prefixes (#3663)
- Update Intake Review Governance preset to v0.2.0 (#3796)
- fix(constitution): stop propagating guidance into templates (#3737) (#3790)
- chore: release 0.14.3, begin 0.14.4.dev0 development (#3795)
-
-## [0.14.3] - 2026-07-28
-
-### Changed
-
- Update Intake Authoring Governance preset to v0.3.0 (#3788)
- fix(copilot): honor preset command template overrides (#3592)
- clarify: require real interrogatives, ban topic-label questions (#3745)
- feat: Add Alquimia AI integration (#2734)
- harden: secure extension and preset archive downloads (#3141)
- fix: correct Optional type annotation for context_note parameter (#3765)
- Update AGENTS.md (#2626)
- fix(extensions): tolerate non-string catalog name in display-name lookup (#3747)
- fix(presets): coerce non-string catalog tags before joining (#3743)
- fix: register extensions for the active integration only (#3459)
- fix(extensions): tolerate non-string tags in catalog search (#3746)
- fix(extensions): hyphenate command names in 'extension info' listing (#3744)
- fix(workflows): escape remaining untrusted fields in `workflow info` (#3731)
- fix(extensions): guard non-numeric catalog downloads in search/info rendering (#3710)
- fix(agent-context): apply default markers when config markers are blank (bash) (#3736)
- fix: escape Rich markup in catalog list output (#3738)
- fix(workflows): guard non-mapping 'workflow:' block in WorkflowDefinition (#3694)
- fix(bundler): reject unsupported schema_version in _merge_config (align readers) (#3711)
- Update Linear Weave extension to v1.0.1 (#3762)
- Add Intake Sequencing Governance preset to community catalog (#3761)
- Update Quality Gates (Enforcement Layer) extension to v0.3.3 (#3760)
- Update Verify Review Ship extension to v0.4.1 (#3759)
- fix(agent-context): discover nested plans in Python port mtime fallback (#3734)
- fix(extensions): make shipped scripts executable after install (#3723)
- docs(assess): clarify the pipeline works on an empty project (#3732)
- chore: release 0.14.2, begin 0.14.3.dev0 development (#3730)
-
-## [0.14.2] - 2026-07-24
-
-### Changed
-
- Update Intake Review Governance preset to v0.1.1 (#3729)
- Update Verify Review Ship extension to v0.3.0 (#3728)
- Update Architecture Guard extension to v1.13.1 (#3724)
- docs(upgrade): Claude Code files live in .claude/skills, not .claude/commands (#3708)
- fix(kilocode): install commands under .kilo/commands (#3672)
- fix(auth): normalize whitespace in auth-config env-var/id references at store time (#3691)
- fix(workflows): guard non-mapping 'inputs:' block in engine._resolve_inputs (#3696)
- Update Intake Authoring Governance preset to v0.2.0 (#3721)
- docs: clarify shell-step interpolation safety (#3719)
- [extension] Add Blueprint Index — Living Architecture Map extension to community catalog (#3718)
- fix(github-http): return None on malformed host in resolve_github_release_asset_api_url (#3715)
- fix(integrations): declare PiIntegration multi_install_safe (#3652)
- harden: remove shell parameter from run_command() (#3716)
- chore(deps): bump github/codeql-action/init from 4.37.1 to 4.37.3 (#3699)
- fix: auto-correct conflicting feature prefixes (#1829)
- chore(deps): bump actions/checkout from 6.0.3 to 7.0.1 (#3703)
- chore(deps): bump DavidAnson/markdownlint-cli2-action (#3702)
- chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#3701)
- chore(deps): bump astral-sh/setup-uv from 8.3.2 to 9.0.0 (#3700)
- chore: release 0.14.1, begin 0.14.2.dev0 development (#3698)
-
 ## [0.14.1] - 2026-07-23

 ### Changed
@@ -55,8 +55,6 @@ Here are a few things you can do that will increase the likelihood of your pull
 - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 - Test your changes with the Spec-Driven Development workflow to ensure compatibility.

-Accounts with three open pull requests may continue submitting changes, but additional submissions may be placed behind contributions from other authors in the review queue. Coding agents should disclose this possibility and obtain the filer's confirmation before opening another pull request.
-
 ### Branch naming

 We recommend naming branches as `<type>/<number>-<short-slug>`, where `<number>` is the issue or PR number (whichever comes first) and `<type>` is one of:
@@ -1,5 +1,5 @@
 <div align="center">
-    <img src="https://raw.githubusercontent.com/github/spec-kit/main/media/logo_large.webp" alt="Spec Kit Logo" width="200" height="200"/>
+    <img src="./media/logo_large.webp" alt="Spec Kit Logo" width="200" height="200"/>
    <h1>🌱 Spec Kit</h1>
    <h3><em>Define what to build before building it — with any AI coding agent.</em></h3>
 </div>
@@ -15,11 +15,6 @@
    <a href="https://github.github.io/spec-kit/"><img src="https://img.shields.io/badge/docs-GitHub_Pages-blue" alt="Documentation"/></a>
 </p>

-<p align="center">
-    <strong>English</strong> ·
-    <a href="./README.zh-CN.md">简体中文</a>
-</p>
-
 ---

 ## Table of Contents
@@ -136,7 +131,7 @@ For detailed step-by-step instructions, see our [comprehensive guide](./spec-dri

 Want to see Spec Kit in action? Watch our [video overview](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)!

-[![Spec Kit video header](https://raw.githubusercontent.com/github/spec-kit/main/media/spec-kit-video-header.jpg)](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)
+[![Spec Kit video header](/media/spec-kit-video-header.jpg)](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)

 ## 🌍 Community

@@ -1,361 +0,0 @@
-<div align="center">
-    <img src="./media/logo_large.webp" alt="Spec Kit Logo" width="200" height="200"/>
-    <h1>🌱 Spec Kit</h1>
-    <h3><em>在动手编码之前，先定义要构建什么 —— 适配任意 AI 编码助手。</em></h3>
-</div>
-
-<p align="center">
-    <strong>一个开源工具套件，帮助你借助任意 AI 编码助手构建高质量软件 —— 内置开箱即用的规范驱动流程（也可自带流程），可无限扩展、由社区驱动，并为整个组织的协作而设计。</strong>
-</p>
-
-<p align="center">
-    <a href="https://github.com/github/spec-kit/releases/latest"><img src="https://img.shields.io/github/v/release/github/spec-kit" alt="Latest Release"/></a>
-    <a href="https://github.com/github/spec-kit/stargazers"><img src="https://img.shields.io/github/stars/github/spec-kit?style=social" alt="GitHub stars"/></a>
-    <a href="https://github.com/github/spec-kit/blob/main/LICENSE"><img src="https://img.shields.io/github/license/github/spec-kit" alt="License"/></a>
-    <a href="https://github.github.io/spec-kit/"><img src="https://img.shields.io/badge/docs-GitHub_Pages-blue" alt="Documentation"/></a>
-</p>
-
-<p align="center">
-    <a href="./README.md">English</a> ·
-    <strong>简体中文</strong>
-</p>
-
---
-
-## 目录
-
- [🤔 什么是规范驱动开发？](#-什么是规范驱动开发)
- [⚡ 快速开始](#-快速开始)
- [📽️ 视频概览](#️-视频概览)
- [🌍 社区](#-社区)
- [🤖 支持的 AI 编码助手集成](#-支持的-ai-编码助手集成)
- [🔧 Specify CLI 参考](#-specify-cli-参考)
- [🧩 打造你自己的 Spec Kit：扩展与预设](#-打造你自己的-spec-kit扩展与预设)
- [📦 捆绑包：面向角色的一键配置](#-捆绑包面向角色的一键配置)
- [📚 核心理念](#-核心理念)
- [🌟 开发阶段](#-开发阶段)
- [🎯 实验目标](#-实验目标)
- [🔧 环境要求](#-环境要求)
- [📖 深入了解](#-深入了解)
- [💬 支持](#-支持)
- [🙏 致谢](#-致谢)
- [📄 许可证](#-许可证)
-
-## 🤔 什么是规范驱动开发？
-
-规范驱动开发（Spec-Driven Development）**颠覆了**传统软件开发的思路。几十年来，代码一直是核心 —— 规范只是编码这项"正事"开始前搭起、随后就被丢弃的脚手架。规范驱动开发改变了这一点：**规范本身变得可执行**，它不再只是引导实现，而是直接生成可运行的实现。
-
-## ⚡ 快速开始
-
-### 1. 安装 Specify CLI
-
-需要 **[uv](https://docs.astral.sh/uv/)**（[安装 uv](./docs/install/uv.md)）。将 `vX.Y.Z` 替换为 [Releases](https://github.com/github/spec-kit/releases) 中最新的发布标签 —— 记得保留开头的 `v`（例如 `v0.12.11`，而不是 `0.12.11`）：
-
-```bash
-uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@vX.Y.Z
-```
-
-更倾向从 PyPI 安装？`specify-cli` 包同样发布在那里：
-
-```bash
-uv tool install specify-cli
-```
-
-其他安装方式、安装校验、升级以及故障排查，请参阅[安装指南](./docs/installation.md)。
-
-### 2. 初始化项目
-
-```bash
-specify init my-project --integration copilot
-cd my-project
-```
-
-要检查更新或升级已安装的 CLI，可使用自管理命令。更详细的场景和自定义选项请参阅[升级指南](./docs/upgrade.md)。
-
-```bash
-# 检查是否有更新版本可用（只读操作 —— 不会修改任何内容）
-specify self check
-
-# 预览升级将执行的操作，但不实际升级
-specify self upgrade --dry-run
-
-# 就地升级到最新稳定版（自动识别 uv tool 与 pipx 安装方式）
-specify self upgrade
-
-# 或锁定到指定的发布标签（将 vX.Y.Z[suffix] 替换为你想要的标签）
-specify self upgrade --tag vX.Y.Z[suffix]
-```
-
-直接运行 `specify self upgrade` 会立即执行，与 `pip install -U`、`npm update` 等命令一样无需额外确认。对于 `uv tool` 安装的情况，它在底层会执行 `uv tool install specify-cli --force --from <git ref>`，因此锁定的发布标签同样有效，包括 dev、alpha/beta/rc 或带构建元数据的后缀。`uvx`（临时运行）和源码检出会被自动识别，此时会给出针对具体路径的操作建议，而不会执行安装程序。可通过设置 `SPECIFY_UPGRADE_TIMEOUT_SECS` 来限制安装子进程的最长运行时间（默认无超时限制 —— 必要时用 `Ctrl+C` 中断）。
-
-### 3. 确立项目准则
-
-在项目目录下启动你的编码助手。大多数助手将 spec-kit 暴露为 `/speckit.*` 斜杠命令；处于技能（skills）模式的 Codex CLI 则使用 `$speckit-*`；GitHub Copilot CLI 使用 `/agents` 来选择助手，或直接在提示词中指定它。
-
-使用 **`/speckit.constitution`** 命令来创建项目的治理准则和开发指南，它们将指导后续所有开发工作。
-
-```bash
-/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements
-```
-
-### 4. 编写规范
-
-使用 **`/speckit.specify`** 命令描述你想构建什么。聚焦于**做什么**和**为什么做**，而不是技术栈。
-
-```bash
-/speckit.specify Build an application that can help me organize my photos in separate photo albums. Albums are grouped by date and can be re-organized by dragging and dropping on the main page. Albums are never in other nested albums. Within each album, photos are previewed in a tile-like interface.
-```
-
-### 5. 制定技术实现方案
-
-使用 **`/speckit.plan`** 命令提供你的技术栈和架构选择。
-
-```bash
-/speckit.plan The application uses Vite with minimal number of libraries. Use vanilla HTML, CSS, and JavaScript as much as possible. Images are not uploaded anywhere and metadata is stored in a local SQLite database.
-```
-
-### 6. 拆解为任务
-
-使用 **`/speckit.tasks`** 从实现方案生成一份可执行的任务清单。
-
-```bash
-/speckit.tasks
-```
-
-### 7. 执行实现
-
-使用 **`/speckit.implement`** 执行所有任务，按方案构建你的功能。
-
-```bash
-/speckit.implement
-```
-
-详细的分步说明，请参阅我们的[完整指南](./spec-driven.md)。
-
-## 📽️ 视频概览
-
-想看看 Spec Kit 的实际效果？观看我们的[视频概览](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)！
-
-[![Spec Kit video header](/media/spec-kit-video-header.jpg)](https://www.youtube.com/watch?v=a9eR1xsfvHg&pp=0gcJCckJAYcqIYzv)
-
-## 🌍 社区
-
-在 [Spec Kit 文档站点](https://github.github.io/spec-kit/)上探索由社区贡献的资源：
-
- [扩展（Extensions）](https://github.github.io/spec-kit/community/extensions.html) —— 命令、钩子与各类能力
- [预设（Presets）](https://github.github.io/spec-kit/community/presets.html) —— 模板与术语覆盖
- [捆绑包（Bundles）](https://github.github.io/spec-kit/community/bundles.html) —— 由现有组件组合而成的角色与团队技术栈
- [实战演练（Walkthroughs）](https://github.github.io/spec-kit/community/walkthroughs.html) —— 端到端的 SDD 场景
- [伙伴项目（Friends）](https://github.github.io/spec-kit/community/friends.html) —— 扩展 Spec Kit 或基于它构建的项目
-
-> [!NOTE]
-> 社区贡献由各自的作者独立创建和维护。请在安装前审阅源代码，并自行斟酌使用。
-
-想要参与贡献？请参阅[扩展发布指南](extensions/EXTENSION-PUBLISHING-GUIDE.md)、[预设发布指南](presets/PUBLISHING.md)或[社区捆绑包指南](docs/community/bundles.md)。
-
-## 🤖 支持的 AI 编码助手集成
-
-Spec Kit 可与 30 多个 AI 编码助手协作 —— 既包括 CLI 工具，也包括基于 IDE 的助手。完整列表以及相关说明和使用细节，请参阅[支持的 AI 编码助手集成](https://github.github.io/spec-kit/reference/integrations.html)指南。
-
-运行 `specify integration list` 可查看当前安装版本中所有可用的集成。
-
-## 可用的斜杠命令
-
-运行 `specify init` 后，你的 AI 编码助手就能使用这些斜杠命令来进行结构化开发。对于支持技能模式的集成，传入 `--integration <agent> --integration-options="--skills"` 会安装助手技能，而不是斜杠命令的提示词文件。
-
-### 核心命令
-
-规范驱动开发工作流中必不可少的命令：
-
-| 命令                     | 助手技能               | 说明                                                       |
-| ------------------------ | ---------------------- | ---------------------------------------------------------- |
-| `/speckit.constitution`  | `speckit-constitution` | 创建或更新项目的治理准则和开发指南                         |
-| `/speckit.specify`       | `speckit-specify`      | 定义你想构建什么（需求与用户故事）                         |
-| `/speckit.plan`          | `speckit-plan`         | 结合所选技术栈制定技术实现方案                             |
-| `/speckit.tasks`         | `speckit-tasks`        | 生成可执行的实现任务清单                                   |
-| `/speckit.taskstoissues` | `speckit-taskstoissues`| 将生成的任务清单转换为 GitHub issue，便于跟踪与执行        |
-| `/speckit.implement`     | `speckit-implement`    | 执行所有任务，按方案构建功能                               |
-| `/speckit.converge`      | `speckit-converge`     | 对照规范/方案/任务评估代码库，并将剩余工作追加为新任务     |
-
-### 可选命令
-
-用于提升质量与做校验的额外命令：
-
-| 命令                 | 助手技能               | 说明                                                                                              |
-| -------------------- | ---------------------- | ------------------------------------------------------------------------------------------------- |
-| `/speckit.clarify`   | `speckit-clarify`      | 澄清描述不充分的部分（建议在 `/speckit.plan` 之前使用；旧称 `/quizme`）                            |
-| `/speckit.analyze`   | `speckit-analyze`      | 跨制品的一致性与覆盖度分析（在 `/speckit.tasks` 之后、`/speckit.implement` 之前运行）              |
-| `/speckit.checklist` | `speckit-checklist`    | 生成自定义质量清单，校验需求的完整性、清晰度与一致性（好比"为自然语言写单元测试"）                 |
-
-## 🔧 Specify CLI 参考
-
-完整的命令详情、选项与示例，请参阅 [CLI 参考文档](https://github.github.io/spec-kit/reference/overview.html)。
-
-## 🧩 打造你自己的 Spec Kit：扩展与预设
-
-Spec Kit 可通过两套互补的机制进行深度定制 —— **扩展（extensions）** 和 **预设（presets）** —— 以及面向单个项目的本地覆盖，用于临时性调整：
-
-| 优先级 | 组件类型                           | 位置                             |
-| -----: | ---------------------------------- | -------------------------------- |
-|   ⬆ 1 | 项目本地覆盖                       | `.specify/templates/overrides/`  |
-|      2 | 预设 —— 定制核心与扩展             | `.specify/presets/templates/`    |
-|      3 | 扩展 —— 新增能力                   | `.specify/extensions/templates/` |
-|   ⬇ 4 | Spec Kit 核心 —— 内置 SDD 命令与模板 | `.specify/templates/`            |
-
- **模板**在**运行时**解析 —— Spec Kit 从高到低遍历优先级栈，使用第一个匹配项。
- 项目本地覆盖（`.specify/templates/overrides/`）允许对单个项目做一次性调整，无需创建完整的预设。
- **扩展/预设命令**在**安装时**生效 —— 当你运行 `specify extension add` 或 `specify preset add` 时，命令文件会被写入助手目录（如 `.claude/commands/`）。
- 若多个预设或扩展提供了同一命令，优先级最高的版本生效。移除时，次优先级的版本会自动恢复。
- 若不存在任何覆盖或自定义，Spec Kit 使用核心默认配置。
-
-### 扩展 —— 新增能力
-
-当你需要 Spec Kit 核心之外的功能时，使用**扩展**。扩展可引入新命令和模板 —— 例如添加核心 SDD 命令未覆盖的领域特定工作流、集成外部工具，或新增全新的开发阶段。它们扩展了 *Spec Kit 能做什么*。
-
-```bash
-# 搜索可用扩展
-specify extension search
-
-# 安装扩展
-specify extension add <extension-name>
-```
-
-举例来说，扩展可以添加 Jira 集成、实现后代码审查、V 模型测试追溯性，或项目健康诊断等功能。
-
-完整命令指南请参阅[扩展参考文档](https://github.github.io/spec-kit/reference/extensions.html)。浏览[社区扩展](https://github.github.io/spec-kit/community/extensions.html)了解现有资源。
-
-### 预设 —— 定制现有工作流
-
-当你想改变 Spec Kit 的*工作方式*而不是新增能力时，使用**预设**。预设会覆盖核心及已安装扩展中附带的模板和命令 —— 例如强制使用面向合规的规范格式、采用领域特定术语，或对方案和任务应用组织规范。预设定制的是 Spec Kit 及其扩展生成的制品与指令。
-
-```bash
-# 搜索可用预设
-specify preset search
-
-# 安装预设
-specify preset add <preset-name>
-```
-
-举例来说，预设可以重构规范模板以要求监管追溯性，将工作流适配为你所用的方法论（如敏捷、看板、瀑布、用户任务驱动或领域驱动设计），在方案中添加强制安全审查关卡，强制要求测试优先的任务排序，或将整个工作流本地化为其他语言。[海盗语演示](https://github.com/mnriem/spec-kit-pirate-speak-preset-demo)充分展示了定制的深度。多个预设可按优先级叠加使用。
-
-完整命令指南以及解析顺序和优先级叠加说明，请参阅[预设参考文档](https://github.github.io/spec-kit/reference/presets.html)。
-
-## 📦 捆绑包：面向角色的一键配置
-
-扩展和预设是独立的构建模块。而**捆绑包（bundle）**将一组精选的扩展、预设、步骤和工作流打包成一个带版本、面向角色的配置，从而可以用一条命令为整个团队角色（产品经理、业务分析师、安全研究员、开发者……）完成配置。
-
-捆绑包由一份手写的 `bundle.yml` 清单描述。它将每个组件锁定到具体版本，并可选择性地面向特定集成；未指定 `integration` 的捆绑包是**中立的**，会沿用项目当前已使用的集成。
-
-```bash
-# 在当前激活的目录栈中发现捆绑包
-specify bundle search [<query>]
-
-# 查看捆绑包将添加的确切组件集合（与实际安装的内容一致）
-specify bundle info <bundle-id>
-
-# 一步安装捆绑包的完整组件集合
-specify bundle install <bundle-id>
-
-# 查看已安装内容，然后以非破坏性方式更新或移除
-specify bundle list
-specify bundle update <bundle-id>     # 或 --all
-specify bundle remove <bundle-id>     # 仅移除此捆绑包的组件
-```
-
-捆绑包从一个**按优先级排序的目录栈**（项目 > 用户 > 内置）中解析。每个来源都带有安装策略：`install-allowed` 来源可用于安装，而 `discovery-only` 来源在 `search`/`info` 中可见但拒绝安装。可通过 `specify bundle catalog list|add|remove` 管理目录栈。
-
-作者在本地校验并打包捆绑包。分发方式是托管构建产物并添加一个目录来源；社区捆绑包投稿请使用 [Bundle Submission](https://github.com/github/spec-kit/issues/new?template=bundle_submission.yml) issue 模板，以便对所需的组件目录和安装证据进行审阅：
-
-```bash
-specify bundle validate --path ./my-bundle      # 结构与引用检查
-specify bundle build --path ./my-bundle         # 生成带版本的 .zip 产物
-```
-
-[`examples/bundles/`](examples/bundles/) 目录下有四份可直接阅读的示例清单（产品经理、业务分析师、安全研究员、开发者）。
-
-关键保证：`info` 展示的内容与 `install` 添加的内容完全一致（透明性）；安装是幂等的，且限定在项目根目录内；`remove` 绝不会触碰其他已安装捆绑包仍需要的组件；所有消费/创作命令都能针对本地或锁定的来源**离线**工作。
-
-### 何时用哪个
-
-| 目标 | 使用 |
-| --- | --- |
-| 添加全新的命令或工作流 | 扩展 |
-| 定制规范、方案或任务的格式 | 预设 |
-| 集成外部工具或服务 | 扩展 |
-| 强制执行组织或监管规范 | 预设 |
-| 交付可复用的领域特定模板 | 均可 —— 预设用于模板覆盖，扩展用于随新命令一起打包的模板 |
-| 用一条命令完成完整的角色配置 | 捆绑包 |
-
-## 📚 核心理念
-
-规范驱动开发是一套结构化流程，它强调：
-
- **意图驱动开发** —— 让规范先定义"*做什么*"，再谈"*怎么做*"
- **丰富的规范撰写** —— 借助护栏与组织准则来编写规范
- **多步精炼** —— 而非从提示词一次性生成代码
- **充分依赖**先进 AI 模型对规范的解读能力
-
-## 🌟 开发阶段
-
-| 阶段                                      | 侧重点             | 关键活动                                                                                                                                             |
-| ----------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **从 0 到 1 开发**（"绿地/Greenfield"）   | 从零生成           | <ul><li>从高层需求出发</li><li>生成规范</li><li>规划实现步骤</li><li>构建生产就绪的应用</li></ul>                                                    |
-| **创意探索**                              | 并行实现           | <ul><li>探索多样化的解决方案</li><li>支持多种技术栈与架构</li><li>试验不同的用户体验模式</li></ul>                                                   |
-| **迭代增强**（"棕地/Brownfield"）         | 存量系统现代化     | <ul><li>迭代式添加功能</li><li>现代化改造遗留系统</li><li>调整流程</li></ul>                                                                         |
-
-对于已有项目，请将 Spec Kit 工具本身的更新与功能制品的演进分开处理：升级时刷新受管理的项目文件，而在预期行为发生变化时更新 `specs/` 制品。[规范演进指南](./docs/guides/evolving-specs.md)介绍了推荐的棕地迭代循环。
-
-## 🎯 实验目标
-
-我们的研究与实验聚焦于：
-
-### 技术无关性
-
- 使用多样化的技术栈构建应用
- 验证这一假设：规范驱动开发是一套流程，不与特定技术、编程语言或框架绑定
-
-### 企业级约束
-
- 展示关键业务应用的开发
- 纳入组织层面的约束（云服务商、技术栈、工程实践）
- 支持企业设计系统与合规要求
-
-### 以用户为中心的开发
-
- 为不同的用户群体和偏好构建应用
- 支持多种开发方式（从"氛围编码"到 AI 原生开发）
-
-### 创意与迭代流程
-
- 验证并行实现探索的理念
- 提供稳健的迭代式功能开发工作流
- 将流程扩展到升级与现代化改造任务
-
-## 🔧 环境要求
-
- **Linux/macOS/Windows**
- [受支持的](#-支持的-ai-编码助手集成) AI 编码助手。
- [uv](https://docs.astral.sh/uv/) 用于包管理（推荐），或 [pipx](https://pipx.pypa.io/) 用于持久化安装
- [Python 3.11+](https://www.python.org/downloads/)
- [Git](https://git-scm.com/downloads)
-
-如果你在使用某个助手时遇到问题，欢迎提交 issue，以便我们完善相应集成。
-
-## 📖 深入了解
-
- **[完整的规范驱动开发方法论](./spec-driven.md)** —— 深入了解整个流程
- **[快速上手指南](https://github.github.io/spec-kit/quickstart.html)** —— 分步实现演练
-
---
-
-## 💬 支持
-
-如需帮助，请提交 [GitHub issue](https://github.com/github/spec-kit/issues/new)。我们欢迎缺陷报告、功能建议，以及关于使用规范驱动开发的各类问题。
-
-## 🙏 致谢
-
-本项目深受 [John Lam](https://github.com/jflam) 的工作与研究的影响，并在其基础上构建。
-
-## 📄 许可证
-
-本项目基于 MIT 开源许可证的条款授权。完整条款请参阅 [LICENSE](./LICENSE) 文件。
@@ -25,7 +25,6 @@ The following community-contributed extensions are available in [`catalog.commun

 | Extension | Purpose | Category | Effect | URL |
 |-----------|---------|----------|--------|-----|
-| adrkit — decision memory for spec-driven development | Pulls the decisions governing this work into agent context, checks produced plans against them, and drafts an ADR from a plan artifact | `process` | Read+Write | [adrkit](https://github.com/mbeacom/adrkit) |
 | Agent Assign | Assign specialized Claude Code agents to spec-kit tasks for targeted execution | `process` | Read+Write | [spec-kit-agent-assign](https://github.com/xymelon/spec-kit-agent-assign) |
 | Agent Governance | Generate agent-platform repository governance files from Spec Kit metadata | `process` | Read+Write | [spec-kit-agent-governance](https://github.com/bigsmartben/spec-kit-agent-governance) |
 | AI-Driven Engineering (AIDE) | A structured 7-step workflow for building new projects from scratch with AI assistants — from vision through implementation | `process` | Read+Write | [aide](https://github.com/mnriem/spec-kit-extensions/tree/main/aide) |
@@ -37,7 +36,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Archive Extension | Archive merged features into main project memory. | `docs` | Read+Write | [spec-kit-archive](https://github.com/stn1slv/spec-kit-archive) |
 | Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | `integration` | Read+Write | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) |
 | Blueprint | Stay code-literate in AI-driven development: review a complete code blueprint for every task from spec artifacts before /speckit.implement runs | `docs` | Read+Write | [spec-kit-blueprint](https://github.com/chordpli/spec-kit-blueprint) |
-| Blueprint Index — Living Architecture Map | A living architecture map for spec-driven projects, kept honest by a deterministic, low-friction, machine-first CI gate (JSON, self-healable) that blocks only when the map contradicts the specs or code. Brownfield or greenfield. | `process` | Read+Write | [spec-kit-blueprint](https://github.com/ogil109/spec-kit-blueprint) |
 | Branch Convention | Configurable branch and folder naming conventions for /specify with presets and custom patterns | `process` | Read+Write | [spec-kit-branch-convention](https://github.com/Quratulain-bilal/spec-kit-branch-convention) |
 | Brownfield Bootstrap | Bootstrap spec-kit for existing codebases — auto-discover architecture and adopt SDD incrementally | `process` | Read+Write | [spec-kit-brownfield](https://github.com/Quratulain-bilal/spec-kit-brownfield) |
 | BrownKit | Evidence-driven capability discovery, security and QA risk assessment for existing codebases | `process` | Read+Write | [BrownKit](https://github.com/MaksimShevtsov/BrownKit) |
@@ -51,7 +49,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Coding Standards Drift Control | Generate coding-standards drift reports and remediation tasks for active Spec Kit features | `code` | Read+Write | [spec-kit-coding-standards-drift-control](https://github.com/benizzio/spec-kit-coding-standards-drift-control) |
 | Conduct Extension | Orchestrates spec-kit phases via sub-agent delegation to reduce context pollution. | `process` | Read+Write | [spec-kit-conduct-ext](https://github.com/twbrandon7/spec-kit-conduct-ext) |
 | Confluence Extension | Create a doc in Confluence summarizing the specifications and planning files | `integration` | Read+Write | [spec-kit-confluence](https://github.com/aaronrsun/spec-kit-confluence) |
-| ContextForge MCP | Integrates codebase-memory-mcp + headroom into Spec Kit — graph-based code intelligence and context compression for the implement phase | `code` | Read+Write | [contextforge-mcp](https://github.com/capatinore/contextforge-mcp) |
 | Cost Tracker | Track real LLM dollar cost across SDD workflows — per-feature budgets, per-integration comparison, and finance-ready exports | `visibility` | Read+Write | [spec-kit-cost](https://github.com/Quratulain-bilal/spec-kit-cost) |
 | Data Model Diagram | Generates Mermaid ER diagrams from Spec Kit data models after planning | `docs` | Read+Write | [spec-kit-data-model-diagram](https://github.com/benizzio/spec-kit-data-model-diagram) |
 | DocGuard — CDD Enforcement | The only doc-integrity engine with an MCP server, SARIF/JUnit output, and a deterministic zero-LLM core. Validates, scores, and traces documentation against code — 27 validators, stable finding codes, adoption baseline for legacy repos, compliance-evidence reports, GitHub Action with PR annotations, spec-kit hooks. Pure Node.js, one pinned dep. | `docs` | Read+Write | [spec-kit-docguard](https://github.com/raccioly/docguard) |
@@ -68,7 +65,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Improve Extension | Audits any codebase as a senior advisor and writes prioritized, self-contained spec prompts under specs/ that the spec-kit lifecycle can process | `process` | Read+Write | [spec-kit-improve](https://github.com/d0whc3r/spec-kit-improve) |
 | Intake | Normalize PRD, design, HTML SSOT, and test-case evidence into SDD-ready intake artifacts. | `docs` | Read+Write | [spec-kit-intake](https://github.com/bigsmartben/spec-kit-intake) |
 | Intelligent Agent Orchestrator | Cross-catalog agent discovery and intelligent prompt-to-command routing | `process` | Read+Write | [spec-kit-orchestrator](https://github.com/pragya247/spec-kit-orchestrator) |
-| Intent Reconciliation | Reconcile implementation-discovered decisions against approved feature intent | `process` | Read+Write | [spec-kit-reconcile](https://github.com/SuhaibAslam/spec-kit-reconcile) |
 | Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | `docs` | Read+Write | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) |
 | Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | `integration` | Read+Write | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) |
 | Jira Integration (Sync Engine) | Idempotent, drift-aware, fail-closed reconcile engine mirroring spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase) | `integration` | Read+Write | [spec-kit-jira-sync](https://github.com/ashbrener/spec-kit-jira-sync) |
@@ -153,7 +149,6 @@ The following community-contributed extensions are available in [`catalog.commun
 | Superpowers Implementation Bridge | Thin orchestrator between Spec Kit (design) and Superpowers (implementation). Cross-agent. | `process` | Read+Write | [speckit-superpowers-bridge](https://github.com/lihan3238/speckit-superpowers-bridge) |
 | Superspec | Bridges spec-kit with obra/superpowers (brainstorming, TDD, subagent, code-review) into a unified, resumable workflow with graceful degradation and session progress tracking | `process` | Read+Write | [superspec](https://github.com/WangX0111/superspec) |
 | Tasks to GitHub Project | Publish and synchronize Spec Kit tasks as cards on a GitHub Project (v2) kanban board, with priority and status sync between spec.md/tasks.md and the board. | `integration` | Read+Write | [spec-kit-tasks-to-project](https://github.com/mancioshell/spec-kit-tasks-to-project) |
-| TDD Extension | Drives spec-kit implementation with tests: a language-agnostic red-green-refactor loop with a per-feature test list, recorded red and green evidence, and mutation-checked test strength. | `process` | Read+Write | [spec-kit-tdd](https://github.com/d0whc3r/spec-kit-tdd) |
 | Team Assign | Assign tasks.md items to human engineers, split into subtasks, and generate a per-engineer workboard | `process` | Read+Write | [spec-kit-team-assign](https://github.com/tarunkumarbhati/spec-kit-team-assign) |
 | Test Coverage Drift Control | Generate incremental coverage drift reports and planned remediation tasks after implementation | `code` | Read+Write | [spec-kit-test-coverage-drift-control](https://github.com/benizzio/spec-kit-test-coverage-drift-control) |
 | Time Machine | Retroactively apply the full SDD workflow to existing codebases — analyse, spec, and ship feature-by-feature | `process` | Read+Write | [spec-kit-time-machine](https://github.com/teeyo/spec-kit-time-machine) |
@@ -163,7 +158,7 @@ The following community-contributed extensions are available in [`catalog.commun
 | Token Economy | Token routing, measured savings, and context audit workflows | `process` | Read+Write | [spec-kit-token-economy](https://github.com/formin/spec-kit-token-economy) |
 | V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability | `docs` | Read+Write | [spec-kit-v-model](https://github.com/leocamello/spec-kit-v-model) |
 | Verify Extension | Post-implementation quality gate that validates implemented code against specification artifacts | `code` | Read-only | [spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify) |
-| Verify Review Ship | Post-convergence operational verification, technical review, learning governance, and transactional delivery. | `process` | Read+Write | [spec-kit-verify-review-ship](https://github.com/cadugevaerd/spec-kit-verify-review-ship) |
+| Verify Review Ship | Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows | `process` | Read-only | [spec-kit-verify-review-ship](https://github.com/cadugevaerd/spec-kit-verify-review-ship) |
 | Verify Tasks Extension | Detect phantom completions: tasks marked [X] in tasks.md with no real implementation | `code` | Read-only | [spec-kit-verify-tasks](https://github.com/datastone-inc/spec-kit-verify-tasks) |
 | Version Guard | Verify tech stack versions against live npm registries before planning and implementation | `process` | Read-only | [spec-kit-version-guard](https://github.com/KevinBrown5280/spec-kit-version-guard) |
 | What-if Analysis | Preview the downstream impact (complexity, effort, tasks, risks) of requirement changes before committing to them | `visibility` | Read-only | [spec-kit-whatif](https://github.com/DevAbdullah90/spec-kit-whatif) |
@@ -7,11 +7,11 @@ The following community-contributed presets customize how Spec Kit behaves — o

 | Preset | Purpose | Provides | Requires | URL |
 |--------|---------|----------|----------|-----|
-| A11Y Governance | Adds accessibility (WCAG 2.2 AA), accessible text and JSON status parity, bilingual DE/EN delivery, CEFR-B2 readability, inclusive-content governance, didactic inline-code-comment review, and audit-ready Spec-Kit run evidence to Spec Kit | 10 templates, 3 commands | — | [spec-kit-preset-a11y-governance](https://github.com/hindermath/spec-kit-preset-a11y-governance) |
-| Agent Parity Governance | Adds shared-guidance and generated-command parity, repository-fleet completion evidence, secret-free runner/status metadata, audit-ready Spec-Kit run evidence, and agent-neutral model-routing guidance across declared AI-agent surfaces. | 6 templates, 3 commands | — | [spec-kit-preset-agent-parity-governance](https://github.com/hindermath/spec-kit-preset-agent-parity-governance) |
+| A11Y Governance | Adds WCAG 2.2 AA governance, accessible text/JSON status parity, bilingual DE/EN delivery, CEFR-B2 readability, inclusive content, didactic-comment review, and audit-ready evidence | 10 templates, 3 commands | — | [spec-kit-preset-a11y-governance](https://github.com/hindermath/spec-kit-preset-a11y-governance) |
+| Agent Parity Governance | Adds shared-guidance and generated-command parity, fleet-completion evidence, secret-free runner/status metadata, audit-ready evidence, and agent-neutral model routing. | 6 templates, 3 commands | — | [spec-kit-preset-agent-parity-governance](https://github.com/hindermath/spec-kit-preset-agent-parity-governance) |
 | AIDE In-Place Migration | Adapts the AIDE extension workflow for in-place technology migrations (X → Y pattern) — adds migration objectives, verification gates, knowledge documents, and behavioral equivalence criteria | 2 templates, 8 commands | AIDE extension | [spec-kit-presets](https://github.com/mnriem/spec-kit-presets) |
 | Architecture Governance | Adds secure software architecture, resumable remote-transaction boundaries, STRIDE+CAPEC threat modeling, arc42 security cross-cutting concepts, S-ADRs, Zero Trust applicability, OWASP SAMM governance, BSI C3A cloud autonomy, BSI C5 cloud compliance assurance, and audit-ready Spec Kit run evidence | 13 templates, 3 commands | — | [spec-kit-preset-architecture-governance](https://github.com/hindermath/spec-kit-preset-architecture-governance) |
-| Autonomous Run Governance | Adds permission-bounded autonomous delivery, an optional intake-review gate, and preservation of the project's learner and accessibility contract. | 13 templates, 5 commands, 4 scripts | — | [spec-kit-preset-autonomous-run-governance](https://github.com/hindermath/spec-kit-preset-autonomous-run-governance) |
+| Autonomous Run Governance | Adds permission-bounded, evidence-first governance for complete autonomous Spec Kit delivery, including validated status, stop, explicit resume, exact-head proof, post-merge closeout, retrospective learning, and an optional policy-driven intake-review gate before feature creation. | 13 templates, 5 commands, 4 scripts | — | [spec-kit-preset-autonomous-run-governance](https://github.com/hindermath/spec-kit-preset-autonomous-run-governance) |
 | Canon Core | Adapts original Spec Kit workflow to work together with Canon extension | 2 templates, 8 commands | — | [spec-kit-canon](https://github.com/maximiliamus/spec-kit-canon) |
 | Claude AskUserQuestion | Upgrades `/speckit.clarify` and `/speckit.checklist` on Claude Code from Markdown-table prompts to the native AskUserQuestion picker, with a recommended option and reasoning on every question | 2 commands | — | [spec-kit-preset-claude-ask-questions](https://github.com/0xrafasec/spec-kit-preset-claude-ask-questions) |
 | Command Density | Compacts the nine core Spec Kit command prompts while preserving scripts, handoffs, placeholders, hook output blocks, and rule structure | 9 commands | — | [spec-kit-preset-command-density](https://github.com/Xopoko/spec-kit-preset-command-density) |
@@ -19,14 +19,13 @@ The following community-contributed presets customize how Spec Kit behaves — o
 | Explicit Task Dependencies | Adds explicit `(depends on T###)` dependency declarations and an Execution Wave DAG to tasks.md for parallel scheduling | 1 template, 1 command | — | [spec-kit-preset-explicit-task-dependencies](https://github.com/Quratulain-bilal/spec-kit-preset-explicit-task-dependencies) |
 | Fiction Book Writing | It adapts the Spec-Driven Development workflow for storytelling to create books or audiobooks (with annotations) in 12 languages: features become story elements, specs become story briefs, plans become story structures, and tasks become scene-by-scene writing tasks. Supports single and multi-POV, all major plot structure frameworks, and two style modes: an author voice sample or humanized AI prose principles. Supports interactive elements like brainstorming, interview, roleplay, and extras like statistics, cover builder, illustration builder, and bio command. Export with templates for KDP, D2D, etc. | 26 templates, 34 commands, 2 scripts | — | [speckit-preset-fiction-book-writing](https://github.com/adaumann/speckit-preset-fiction-book-writing) |
 | Game Narrative Writing | Preset for game narrative design and interactive storytelling. It adapts the Spec-Driven Development workflow for game narratives: features become story mechanics, specs become narrative briefs, plans become story maps, and tasks become dialogue and scene-writing tasks. Supports branching narratives, player agency systems, state machines, and interactive dialogue trees. | 37 templates, 34 commands, 5 scripts | — | [speckit-preset-game-narrative-writing](https://github.com/adaumann/speckit-preset-game-narrative-writing) |
-| Intake Authoring Governance | Governs traceable intake CRUD and language-aware requirements collections with atomic migrations, rollback evidence, and safe series authoring. | 12 templates, 5 commands, 7 scripts | — | [spec-kit-preset-intake-authoring-governance](https://github.com/hindermath/spec-kit-preset-intake-authoring-governance) |
-| Intake Review Governance | Reviews single, series, campaign, and language-aware requirements collections before Spec Kit execution. | 8 templates, 3 commands, 4 scripts | — | [spec-kit-preset-intake-review-governance](https://github.com/hindermath/spec-kit-preset-intake-review-governance) |
-| Intake Sequencing Governance | Manages language-aware intake-series order, typed dependencies, lifecycle, and authority-neutral next-candidate selection. | 11 templates, 6 commands, 8 scripts | — | [spec-kit-preset-intake-sequencing-governance](https://github.com/hindermath/spec-kit-preset-intake-sequencing-governance) |
+| Intake Authoring Governance | Creates traceable Spec Kit intakes from ordered text sources and now truthfully adopts legacy intakes without inventing predecessor receipts. | 7 templates, 2 commands, 2 scripts | — | [spec-kit-preset-intake-authoring-governance](https://github.com/hindermath/spec-kit-preset-intake-authoring-governance) |
+| Intake Review Governance | Adds hash-bound review, repair, and status gates for single, series, and campaign intake files before interactive, autonomous, or parallel Spec Kit execution. | 8 templates, 3 commands, 2 scripts | — | [spec-kit-preset-intake-review-governance](https://github.com/hindermath/spec-kit-preset-intake-review-governance) |
 | iSAQB Architecture Governance | Adds iSAQB/CPSA-F and arc42 architecture governance with audit-ready evidence for goals, views, resumability, partial-failure scenarios, ADRs, risks, and technical debt. | 13 templates, 3 commands | — | [spec-kit-preset-isaqb-architecture-governance](https://github.com/hindermath/spec-kit-preset-isaqb-architecture-governance) |
 | Jira Issue Tracking | Overrides `speckit.taskstoissues` to create Jira epics, stories, and tasks instead of GitHub Issues via Atlassian MCP tools | 1 command | — | [spec-kit-preset-jira](https://github.com/luno/spec-kit-preset-jira) |
 | Model Driven Engineering | Focuses on streamlined commands, app repository support, cross-spec support, and capability-aware project memory for model-driven engineering workflows | 6 templates, 11 commands | MDE extension | [spec-kit-preset-mde](https://github.com/AI-MDE/spec-kit-preset-mde) |
 | Multi-Repo Branching | Coordinates feature branch creation across multiple git repositories (independent repos and submodules) during plan and tasks phases | 2 commands | — | [spec-kit-preset-multi-repo-branching](https://github.com/sakitA/spec-kit-preset-multi-repo-branching) |
-| Parallel Autonomous Run Governance | Coordinates permission-bounded autonomous campaigns while preserving the project's learner and accessibility contract across workers and consolidation. | 9 templates, 5 commands, 2 scripts | autonomous-run-governance >=0.2.2; optional: intake-review-governance >=0.1.0 | [spec-kit-preset-parallel-autonomous-run-governance](https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance) |
+| Parallel Autonomous Run Governance | Coordinates isolated autonomous Spec Kit campaigns with bounded concurrency, mixed agents, resumable consolidation, governed post-merge closeout, schema 1.2, and an optional current intake-review gate before worker scheduling. | 9 templates, 5 commands, 2 scripts | autonomous-run-governance >=0.3.2; optional: intake-review-governance >=0.1.0 | [spec-kit-preset-parallel-autonomous-run-governance](https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance) |
 | Pirate Speak (Full) | Transforms all Spec Kit output into pirate speak — specs become "Voyage Manifests", plans become "Battle Plans", tasks become "Crew Assignments" | 6 templates, 9 commands | — | [spec-kit-presets](https://github.com/mnriem/spec-kit-presets) |
 | Screenwriting | Spec-Driven Development for screenwriting/scriptwriting/tutorials: feature films, television (pilot, episode, limited series), and stage plays. Adapts the Spec Kit workflow to screenplay craft — slug lines, action lines, act breaks, beat sheets, and industry-standard pitch documents. Supports three-act, Save the Cat, TV pilot, network episode, cable/streaming episode, and stage-play structural frameworks. Export to Fountain, FTX, PDF | 26 templates, 32 commands, 1 script | — | [speckit-preset-screenwriting](https://github.com/adaumann/speckit-preset-screenwriting) |
 | Security Governance | Adds memory-safe-language and secure-coding governance, exact-head and security-gate evidence, provider-failure classification, ASVS, supply-chain transparency, and EU regulatory screening. | 14 templates, 3 commands | — | [spec-kit-preset-security-governance](https://github.com/hindermath/spec-kit-preset-security-governance) |
@@ -25,7 +25,7 @@ Creates a new Spec Kit project with the necessary directory structure, templates

 Use `<project_name>` to create a new directory, or `--here` (or `.`) to initialize in the current directory. If the directory already has files, use `--force` to merge without confirmation.

-When `--integration` is omitted, interactive terminals prompt you to choose an integration. Non-interactive sessions, such as CI or piped runs, default to GitHub Copilot; pass `--integration <key>` to choose a different integration explicitly, or set `SPECKIT_INTEGRATION_DEFAULT` to change the fallback (see [Environment Variables](#environment-variables)).
+When `--integration` is omitted, interactive terminals prompt you to choose an integration. Non-interactive sessions, such as CI or piped runs, default to GitHub Copilot; pass `--integration <key>` to choose a different integration explicitly.

 ### Examples

@@ -50,15 +50,12 @@ specify init my-project --integration copilot --preset compliance

 | Variable          | Description                                                              |
 | ----------------- | ------------------------------------------------------------------------ |
-| `SPECKIT_INTEGRATION_DEFAULT` | Override the fallback integration used by `specify init` when `--integration` is omitted (interactive prompt default and non-interactive fallback). Set it to any registered integration key (e.g. `gemini`, `claude`). An unrecognized value is ignored with a warning and the built-in default (`copilot`) is used. An explicit `--integration <key>` always takes precedence. |
 | `SPECIFY_INIT_DIR` | Target a member project from outside its directory (e.g. a monorepo root) without `cd`, for non-interactive / CI use. Set it to the **project root** — the directory *containing* `.specify/` (relative paths resolve against the current directory). The path must exist and contain `.specify/`, otherwise the command errors and does **not** fall back to the current directory. Resolved once in the core root helper (`get_repo_root` in Bash, `Get-RepoRoot` in PowerShell), so it is honored by the core feature scripts (`/speckit.plan`, `/speckit.tasks`, …) and the Git extension's feature-branch creation, which inherit it. The `specify` CLI applies the **same** validation rules to every project-scoped subcommand (`specify integration …`, `specify extension …`, `specify workflow …`, `specify preset …`, and the rest that operate on a `.specify/` project), so those can target a member project too. When unset, Bash/PowerShell helpers keep their existing upward search; the `specify` CLI keeps its project-scoped resolver cwd-only unless a command explicitly defines broader detection (for example, bundle commands). |
 | `SPECIFY_FEATURE_DIRECTORY` | Override the active feature directory *within* the resolved project (takes precedence over `.specify/feature.json`). Relative paths resolve under the project root. Combine with `SPECIFY_INIT_DIR` to pick both the project and the feature non-interactively. |
 | `SPECIFY_FEATURE` | Override feature detection for non-Git repositories. Set to the feature directory name (e.g., `001-photo-albums`) to work on a specific feature when not using Git branches. Must be set in the context of the agent prior to using `/speckit.plan` or follow-up commands. |

 > **Two resolution axes.** `SPECIFY_INIT_DIR` selects the **project** (which directory contains `.specify/`); `SPECIFY_FEATURE_DIRECTORY` / `.specify/feature.json` select the **feature** within that project. They are independent — project first, then feature.

-> **Version control.** `specify init` scaffolds a managed `.specify/.gitignore` that excludes machine-local state — `feature.json` (the current-feature pointer, rewritten on every feature switch) and per-machine extension `extensions/*/local-config.yml` overrides — while leaving everything else under `.specify/` (constitution, templates, scripts, extension config) shareable so teams stay aligned. Like the rest of `.specify/`'s shared scripts and templates, the file is tracked in the shared-infrastructure manifest: your edits are preserved on re-init and `specify init --here --force` restores the managed content. It is intentionally left in place by `specify integration uninstall`, which only removes the uninstalled agent's own files.
-
 > **Symlinked project roots.** `SPECIFY_INIT_DIR` relocates *where* the project is, not *how* a command treats symlinks: each command keeps its existing cwd-path stance. Commands that traverse and write project files through broad input paths (`bundle`, `workflow run <file>`) refuse a symlinked `.specify/` to preserve write confinement. Other project-scoped commands keep their existing behavior when `SPECIFY_INIT_DIR` points at a project root, which may include following a symlinked `.specify/`.

 ## Check Installed Tools
@@ -6,7 +6,6 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify

 | Agent                                                                                | Key              | Notes                                                                                                                                     |
 | ------------------------------------------------------------------------------------ | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| [Alquimia AI](https://docs.alquimia.ai)                                              | `alquimia`       | Skills-based integration; installs skills into `.alquimia/skills` and invokes them as `/speckit-<command>`                                |
 | [Amp](https://ampcode.com/)                                                          | `amp`            |                                                                                                                                           |
 | [Antigravity (agy)](https://antigravity.google/)                                     | `agy`            | Skills-based integration; skills are installed automatically                                                                               |
 | [Auggie CLI](https://docs.augmentcode.com/cli/overview)                              | `auggie`         |                                                                                                                                           |
@@ -20,13 +19,13 @@ The Specify CLI supports a wide range of AI coding agents. When you run `specify
 | [Firebender](https://firebender.com/)                                                | `firebender`     | IDE-based agent for Android Studio / IntelliJ                                                                                             |
 | [Forge](https://forgecode.dev/)                                                      | `forge`          |                                                                                                                                           |
 | [Gemini CLI](https://github.com/google-gemini/gemini-cli)                            | `gemini`         |                                                                                                                                           |
-| [GitHub Copilot](https://code.visualstudio.com/)                                     | `copilot`        | Skills-based by default; installs `speckit-<command>/SKILL.md` under `.github/skills/`. Pass `--integration-options="--commands"` to use the supported commands layout: `.agent.md` files under `.github/agents/`, companion `.prompt.md` files under `.github/prompts/`, and a `.vscode/settings.json` merge. |
+| [GitHub Copilot](https://code.visualstudio.com/)                                     | `copilot`        | Defaults to legacy markdown mode: `.agent.md` command files under `.github/agents/`, companion `.prompt.md` files under `.github/prompts/`, and a `.vscode/settings.json` merge. Pass `--integration-options="--skills"` to scaffold skills as `speckit-<command>/SKILL.md` under `.github/skills/` instead. Legacy markdown mode is deprecated and will stop being the default in a future release. |
 | [Goose](https://goose-docs.ai/)                                                      | `goose`          | Uses YAML recipe format in `.goose/recipes/`                                                                                              |
 | [Grok Build](https://docs.x.ai/build/overview)                                       | `grok`           | Skills-based integration; installs skills into `.grok/skills` and invokes them as `/speckit-<command>`                                    |
 | [Hermes](https://github.com/NousResearch/hermes-agent)                               | `hermes`         | Skills-based integration; installs skills globally into `~/.hermes/skills/`                                                                |
 | [IBM Bob](https://www.ibm.com/products/bob)                                          | `bob`            | Skills-based integration by default; installs skills as `speckit-<command>/SKILL.md` under `.bob/skills/` and invokes them as `/speckit-<command>`. Pass `--integration-options="--legacy-commands"` to scaffold the deprecated Bob 1.x layout (`.bob/commands/*.md`) instead; that flag will be removed in a future release. Existing legacy installs can migrate with `specify integration upgrade bob --integration-options="--skills"`, which converts them to the skills layout and removes the old command files. If preset overrides are installed, the migration is rejected with an actionable error (preset artifacts cannot yet be reconciled across a layout change) — remove the preset(s), migrate, then reinstall them. |
 | [Junie](https://junie.jetbrains.com/)                                                | `junie`          |                                                                                                                                           |
-| [Kilo Code](https://github.com/Kilo-Org/kilocode)                                    | `kilocode`       | Installs commands into `.kilo/commands`; legacy `.kilocode/workflows` installs remain supported as a registration fallback                 |
+| [Kilo Code](https://github.com/Kilo-Org/kilocode)                                    | `kilocode`       |                                                                                                                                           |
 | [Kimi Code](https://code.kimi.com/)                                                  | `kimi`           | Skills-based integration; installs into `.kimi-code/skills/`. `--migrate-legacy` moves old `.kimi/skills/` installs to the new paths |
 | [Kiro CLI](https://kiro.dev/docs/cli/)                                               | `kiro-cli`       | Kiro CLI does not substitute `$ARGUMENTS` in file-based prompts, so Spec Kit ships a prose fallback at render time (see [Manage prompts](https://kiro.dev/docs/cli/chat/manage-prompts/) and issue [#1926](https://github.com/github/spec-kit/issues/1926)). Alias: `--integration kiro` |
 | [Lingma](https://lingma.aliyun.com/)                                                 | `lingma`         | Skills-based integration; skills are installed automatically                                                                               |
@@ -95,8 +94,6 @@ Installs the specified integration into the current project. If another integrat

 Installing an additional integration does not change the default integration. Use `specify integration use <key>` to change the default.

-Installed extensions and presets are not registered for a non-default integration at install time — they follow the currently active (default) integration only. `specify integration use <key>` (or `switch <key>`) is what rescaffolds them for the newly active integration.
-
 > **Note:** All integration management commands require a project already initialized with `specify init`. To start a new project with a specific agent, use `specify init <project> --integration <key>` instead.

 **Version note:** Controlled multi-install support was introduced in Spec Kit 0.8.5. If `specify integration install <key>` says another integration is already installed and only suggests `switch` or `uninstall`, check your local CLI with `specify version` and upgrade it. Running a one-shot command such as `uvx --from git+https://github.com/github/spec-kit.git specify ...` uses a temporary copy for that command only; it does not update the persistent `specify` executable on your `PATH`.
@@ -130,7 +127,7 @@ specify integration switch <key>
 | `--refresh-shared-infra` | Also overwrite shared infrastructure files even if you customized them (otherwise customizations are preserved) |
 | `--integration-options`  | Options for the target integration when it is not already installed      |

-If the target integration is not already installed, equivalent to running `uninstall` followed by `install` in a single step. In this mode, `--force` controls whether modified files from the removed integration are deleted. If the target integration is already installed, `switch` only changes the default integration, like `use`; in this mode, `--force` controls whether managed shared templates are overwritten while the default changes. `--integration-options` is rejected for already-installed targets because changing integration options requires reinstalling managed files; run `upgrade <key> --integration-options ...` first, then `use <key>`. Like `use`, `switch` rescaffolds installed extensions and presets for the target integration once it becomes the default.
+If the target integration is not already installed, equivalent to running `uninstall` followed by `install` in a single step. In this mode, `--force` controls whether modified files from the removed integration are deleted. If the target integration is already installed, `switch` only changes the default integration, like `use`; in this mode, `--force` controls whether managed shared templates are overwritten while the default changes. `--integration-options` is rejected for already-installed targets because changing integration options requires reinstalling managed files; run `upgrade <key> --integration-options ...` first, then `use <key>`.

 ## Use an Installed Integration

@@ -144,8 +141,6 @@ specify integration use <key>

 Sets the default integration without uninstalling any other installed integrations. This also refreshes managed shared templates so command references match the new default integration's invocation style. Modified or untracked shared templates are preserved unless `--force` is used.

-`use` is also the activation point for installed extensions and presets: it re-registers every enabled extension's and preset's command overrides (and skills, for skills-mode agents) for the newly active integration, so artifacts installed while a different integration was active are rescaffolded here rather than at install time.
-
 ## Upgrade an Integration

 ```bash
@@ -160,10 +155,6 @@ specify integration upgrade [<key>]

 Reinstalls an installed integration with updated templates and commands (e.g., after upgrading Spec Kit). Defaults to the default integration; if a key is provided, it must be one of the installed integrations. Detects locally modified files and blocks the upgrade unless `--force` is used. Stale files from the previous install that are no longer needed are removed automatically. Shared templates stay aligned with the default integration even when upgrading a non-default integration.

-Enabled extensions and presets are re-registered only when upgrading the currently active (default) integration. A non-default upgrade still refreshes that integration's core commands, but does not re-register its extension or preset layers — `use`/`switch` that integration afterward to rescaffold them.
-
-If an upgrade would change an integration between command and skills layouts while preset artifacts are registered for it, the upgrade is rejected before changing files. Remove the affected presets, run the layout-changing upgrade, then reinstall them.
-
 ## Report Integration Status

 ```bash
@@ -234,8 +225,7 @@ Some integrations accept additional options via `--integration-options`:
 | ----------- | ------------------- | -------------------------------------------------------------- |
 | `generic`   | `--commands-dir`    | Required. Directory for command files                          |
 | `kimi`      | `--migrate-legacy`  | Migrate legacy `.kimi/skills/` installs to `.kimi-code/skills/` (including dotted→hyphenated skill naming, e.g. `speckit.xxx` → `speckit-xxx`) |
-| `copilot`   | `--commands`        | Scaffold `.github/agents/*.agent.md` commands with `.github/prompts/*.prompt.md` companions and merge `.vscode/settings.json` instead of using the default skills layout. |
-| `copilot`   | `--skills`          | Force the default skills layout, overriding an existing commands layout during an explicit migration. |
+| `copilot`   | `--skills`          | Scaffold commands as agent skills (`speckit-<command>/SKILL.md` under `.github/skills/`, invoked as `/speckit-<command>`) instead of the default legacy markdown mode (`.github/agents/*.agent.md` plus `.github/prompts/*.prompt.md` and a `.vscode/settings.json` merge). Without this flag, install warns that legacy markdown mode is deprecated. |

 Example:

@@ -273,23 +263,19 @@ The currently declared multi-install safe integrations are:

 | Key | Command directory |
 | --- | ----------------- |
-| `alquimia` | `.alquimia/skills` |
 | `auggie` | `.augment/commands` |
 | `claude` | `.claude/skills` |
 | `cline` | `.clinerules/workflows` |
 | `codebuddy` | `.codebuddy/commands` |
 | `codex` | `.agents/skills` |
 | `cursor-agent` | `.cursor/skills` |
-| `droid` | `.factory/skills` |
 | `firebender` | `.firebender/commands` |
 | `gemini` | `.gemini/commands` |
 | `grok` | `.grok/skills` |
 | `junie` | `.junie/commands` |
-| `kilocode` | `.kilo/commands` |
+| `kilocode` | `.kilocode/workflows` |
 | `kiro-cli` | `.kiro/prompts` |
-| `lingma` | `.lingma/skills` |
 | `omp` | `.omp/commands` |
-| `pi` | `.pi/prompts` |
 | `qodercli` | `.qoder/commands` |
 | `qwen` | `.qwen/commands` |
 | `shai` | `.shai/commands` |
@@ -314,7 +300,3 @@ CLI-based integrations (like Claude Code, Gemini CLI) require the tool to be ins
 ### When should I use `upgrade` vs `switch`?

 Use `upgrade` when you've upgraded Spec Kit and want to refresh an installed integration's managed files. Use `switch` when you want to replace the current default with another integration; if the target is already installed, `switch` behaves like `use`.
-
-### Do extensions and presets I install apply to every installed integration?
-
-No. Extensions (`specify extension add`) and presets (`specify preset add`) register their command overrides for the currently active (default) integration only, even if other integrations are installed. A non-default integration does not receive those artifacts until it becomes the default: `specify integration use <key>` (or `switch <key>`) rescaffolds every enabled extension and preset for the newly active integration. `specify integration upgrade` follows the same rule — it only re-registers extensions and presets when upgrading the active integration.
@@ -139,7 +139,7 @@ catalogs:

 Presets can provide command files, template files (like `plan-template.md`), and script files. Each file name is evaluated independently against the priority stack, so different files can come from different layers.

-Templates and scripts are looked up from the stack when Spec Kit needs them. Commands use the same stack for replacement and composition, but are materialized into the active integration's directory only, instead of being re-resolved by agents or written to every detected agent directory (#2948). During preset install, Spec Kit registers command files for the preset being installed against the currently active integration; post-install and post-removal reconciliation then recomputes and writes the effective command content for affected command names based on the active stack. Install and rescaffold remain active-only, but removal may also update previously targeted inactive directories recorded by the removed preset to restore the surviving command or skill layer. A non-active installed integration does not otherwise receive these command files until it becomes the default — `specify integration use <key>` (or `switch <key>`) rescaffolds enabled presets for the newly active integration. Agents do not re-resolve the stack each time they run a command.
+Templates and scripts are looked up from the stack when Spec Kit needs them. Commands use the same stack for replacement and composition, but are materialized into detected agent directories instead of being re-resolved by agents. During preset install, Spec Kit registers command files for the preset being installed; post-install and post-removal reconciliation then recomputes and writes the effective command content for affected command names based on the active stack. Agents do not re-resolve the stack each time they run a command.

 By default, files use a **replace** strategy: the first match in the priority stack wins and is used entirely. Templates and commands can also use composition strategies: **prepend** places preset content before lower-priority content, **append** places it after lower-priority content, and **wrap** replaces `{CORE_TEMPLATE}` with lower-priority content. Scripts support **replace** and **wrap**; script wrappers use `$CORE_SCRIPT` as the placeholder.

@@ -39,21 +39,6 @@ specify workflow run my-pipeline.yml --json

 `workflow_id` is the `workflow.id` declared inside the YAML, not the file name. The object is printed exactly as shown — pretty-printed with two-space indentation, on plain stdout with no Rich markup — so it always parses. While the workflow runs under `--json`, any progress a step would print (for example a gate prompt, or output from a prompt step's CLI subprocess) is redirected to stderr, so stdout carries only the JSON object. Read the object from stdout; leave stderr attached to the terminal or capture it separately.

-For `failed` and `aborted` runs, the payload includes an `error` field carrying the terminal step's error message:
-
-```json
-{
-  "run_id": "662bf791",
-  "workflow_id": "build-and-review",
-  "status": "failed",
-  "current_step_id": "boom",
-  "current_step_index": 0,
-  "error": "Command exited with code 3"
-}
-```
-
-`completed` and `paused` runs omit the `error` field. The error is persisted in the run's `state.json`, so `specify workflow status <run_id> --json` surfaces the same message after the fact.
-
 > **Note:** Most workflow commands require a project already initialized with `specify init`. The exception is `specify workflow run <local-file.{yml,yaml}>`, which can run outside a project; in that case, run state is stored under the current directory's `.specify/workflows/runs/<run_id>/`.

 ## Resume a Workflow
@@ -103,17 +88,10 @@ specify workflow add <source>

 | Option          | Description                                            |
 | --------------- | ------------------------------------------------------ |
-| `--dev`         | Install from a local YAML file, package directory, or archive |
+| `--dev`         | Install from a local workflow YAML file or directory   |
 | `--from <url>`  | Install from a custom URL (`<source>` names the expected workflow ID) |

-Installs a workflow from the catalog, an HTTPS URL, a local YAML file, a
-directory containing `workflow.yml`, or a `.zip`, `.tar.gz`, or `.tgz`
-archive. Archives may contain `workflow.yml` at the root or inside one
-top-level directory.
-
-Directory and archive installs preserve the complete workflow package,
-including scripts and other companion files. ZIP, `.tar.gz`, and `.tgz`
-archives follow the same validation and installation behavior.
+Installs a workflow from the catalog, a URL (HTTPS required), a local YAML file, or a local directory containing `workflow.yml`.

 ## Workflow Overlays

@@ -288,9 +266,7 @@ Lower priority values have higher precedence. Change this overlay to `priority:

 ### Interaction with Bundles and Updates

-`specify workflow add <local-directory>` installs the complete local workflow
-package into `.specify/workflows/<id>/`. Archive installs preserve the same
-package contents.
+`specify workflow add <local-directory>` installs `workflow.yml` from the local directory into `.specify/workflows/<id>/`.

 When an installed workflow is refreshed or reinstalled, project overlays in `.specify/workflows/overlays/<id>/` are preserved because they live outside the installed workflow directory.

@@ -526,32 +502,6 @@ args: "{{ inputs.spec }}"
 message: "{{ status | default('pending') }}"
 ```

-### Interpolation and shell safety
-
-Expressions are resolved by **plain string substitution** — the value of `{{ ... }}` is spliced into the surrounding text exactly as-is, with no quoting or escaping added. That is convenient for building `args` and `message` strings, but it has an important consequence for `shell` steps: a `run` field is handed to the system shell (`/bin/sh -c` on POSIX), so any interpolated value is interpreted as **shell syntax**, not just data.
-
-If an interpolated value can contain characters like `;`, `|`, `&`, `$( )`, backticks, or quotes, it can change or extend the command that actually runs. This matters most when the value is not fully under the workflow author's control:
-
- **Workflow `inputs.*`** — supplied by whoever runs the workflow.
- **A prior step's output**, e.g. `{{ steps.plan.output.stdout }}` — for a `prompt` step this is **text produced by the AI agent**, which can in turn be influenced by files, tickets, or web content the agent read. Treat agent output as untrusted when it flows into a `shell` step.
-
-There is **no shell-escaping filter** in the expression language and **no sandbox** around a `shell` step, so none of the practices below can be treated as a guarantee that a hostile value is neutralised. The only reliable control is to constrain what an interpolated value *can* be, and to keep values you cannot constrain out of `run` fields entirely. Scrutinise every `run` field that interpolates a value you do not control, and at minimum:
-
- **Constrain the value at the source with `enum`/an allowlist.** When `inputs.*` feeds a `run` field, restrict it to a fixed set of known-safe values so a caller cannot supply arbitrary shell text at all. This is the strongest control the engine offers — prefer it over any downstream mitigation.
-
-  ```yaml
-  inputs:
-    target:
-      type: string
-      enum: [staging, production]   # caller cannot inject arbitrary text
-  ```
-
- **Keep unconstrained values out of `run`.** If a value cannot be constrained to an allowlist — most agent/`prompt` output — do not interpolate it into a `run` field. Branch on it with `if`/`switch` against fixed conditions, or act on it in a `command`/`prompt` step rather than a shell command built from it.
- **Quoting is not a security boundary.** Surrounding a substitution with quotes (`'{{ inputs.x }}'`) helps the shell treat a *trusted* value as a single argument and avoids word-splitting on spaces, but a value that itself contains the matching quote character can still break out and inject shell syntax. Quote for correctness on constrained values; never rely on quoting to make an *unconstrained* substitution safe.
- **Gates do not inspect the next step, and `message` is printed verbatim.** A `gate` step renders only its own `message`/`show_file` — it does not display, resolve, or sanitise the command that follows it, and approval never neutralises an injectable interpolation. Do **not** interpolate raw untrusted data into `message`: it is printed as-is with no control-character stripping, so agent or caller output could inject terminal/ANSI escapes that alter or hide the approval prompt. Keep `message` to trusted, constrained text, and surface untrusted material for review via `show_file` instead — its path and contents are control/ANSI-stripped before display.
-
-A `shell` step is an arbitrary-command primitive by design; these practices reduce exposure and keep *which* command runs under the author's control, but they do not eliminate the risk of interpolating values you do not fully control.
-
 ## Shell Step Environment Variables

 Shell steps automatically receive the following environment variables:
@@ -578,64 +528,6 @@ Each workflow run persists its state at `.specify/workflows/runs/<run_id>/`:

 This enables `specify workflow resume` to continue from the exact step where a run was paused (e.g., at a gate) or failed.

-### Gate Verdict Inputs
-
-`verdict_input` binds a gate's verdict to a named workflow input. The input must be declared in the workflow's `inputs` block; `specify workflow validate` reports an undeclared reference.
-
-`verdict_input` is not supported inside a `fan-out` template. Fan-out items
-share workflow inputs, while workflow state can represent only one paused
-gate. Place a gate before the fan-out to approve the whole batch, or after a
-fan-in to review the aggregated results.
-
-**Input value semantics:**
-
-| Value | Behavior |
-|---|---|
-| Non-empty string, matches an option (case-insensitive) | Gate auto-decides; `output.choice` is set to the configured option spelling |
-| Non-empty string, no match | Gate fails immediately |
-| Non-string | Gate fails immediately |
-| Missing or empty | Gate prompts on a TTY; pauses otherwise |
-
-**Default value semantics:** A non-empty `default` is consumed as a verdict on the first run — matching an option auto-decides the gate, not matching fails it immediately.
-
-```yaml
-inputs:
-  spec_verdict:
-    type: string
-    default: ""
-steps:
-  - id: review-spec
-    type: gate
-    message: "Approve the specification?"
-    options: [approve, reject]
-    on_reject: retry
-    verdict_input: spec_verdict
-```
-
-Supply a verdict when resuming:
-
-```bash
-specify workflow resume <run_id> --input spec_verdict=approve
-```
-
-For `on_reject: retry`, a bound reject verdict is consumed before the gate
-pauses: the named stored input is reset to `""`. A later resume therefore
-prompts or pauses again until another verdict is supplied. Approve, abort, and
-skip outcomes leave the input unchanged.
-
-Because of that reset, a verdict input used with `on_reject: retry` must accept
-`""`. If it declares an `enum`, include the empty string — otherwise the reset
-value violates the input's own `enum` and the run can no longer be resumed with
-any input. `specify workflow add` reports this as a validation error.
-
-```yaml
-inputs:
-  spec_verdict:
-    type: string
-    enum: ["", approve, reject]
-    default: ""
-```
-
 ## FAQ

 ### What happens when a workflow hits a gate step?
@@ -195,87 +195,21 @@ Some IDE-based agents (like Kilo Code, Cline) may show **duplicate slash command
 **Example for Kilo Code:**

 ```bash
-# List current and legacy Kilo command folders
-ls -la .kilo/commands/
-ls -la .kilocode/workflows/
+# Navigate to the agent's commands folder
+cd .kilocode/workflows/
+
+# List files and identify duplicates
+ls -la

 # Delete old versions (example filenames - yours may differ)
-rm .kilocode/workflows/speckit.specify-old.md
-rm .kilocode/workflows/speckit.plan-v1.md
+rm speckit.specify-old.md
+rm speckit.plan-v1.md
 ```

 Restart your IDE to refresh the command list.

 ---

-## Behavior change: `/constitution` no longer propagates into templates
-
-The `/constitution` command ([#3790](https://github.com/github/spec-kit/pull/3790)) is scoped to
-its own artifact. It updates
-`.specify/memory/constitution.md` and writes a Sync Impact Report, and **no longer edits**
-`plan-template.md`, `spec-template.md`, `tasks-template.md`, installed command files, or
-guidance docs.
-
-### Why
-
-Spec Kit uses **runtime resolution**: `plan`, `tasks`, and `analyze` read
-`.specify/memory/constitution.md` live on every run, and `analyze` is the dedicated drift
-checker. The governed templates carry a pointer, not a copy — `plan-template.md` ships
-`[Gates determined based on constitution file]`, and `/plan` fills that section from the live
-constitution each run. Propagation duplicated the single source of truth and fought the
-preset/override composition system (a `replace` preset shadows an edited core template).
-
-More broadly, presets and extensions — not in-place file edits — are how Spec Kit now governs
-shared assets. Composing policy through the resolution stack keeps it centrally owned, versioned,
-and auditable across repositories, instead of frozen into per-repo copies no core team can see.
-
-### Is this a breaking change for existing projects?
-
-**No — your workflow keeps working.** You would only notice a difference if you relied on
-`/constitution` editing those files in place. The templates are scaffolds, not authorities. When you
-run `/plan`, it copies the template into a per-feature `plan.md` and re-derives the Constitution
-Check from the live constitution; `/analyze` validates against it. Even if a previous
-`/constitution` run materialized concrete gate text into `.specify/templates/plan-template.md`,
-the live constitution remains the source of truth at runtime.
-
-On a **non-forced upgrade**, a materialized template is *preserved* (its hash diverges from the
-recorded managed copy, so the refresh treats it as a customization and does not overwrite it).
-Nothing regresses.
-
-### Optional cleanup — return to the runtime pointer
-
-A frozen, pre-filled Constitution Check is a slightly misleading scaffold and can bias the first
-`/plan` pass. To move fully back to runtime resolution, reset the section body in
-`.specify/templates/plan-template.md` to the pointer:
-
-```text
-## Constitution Check
-
-*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
-
-[Gates determined based on constitution file]
-```
-
-Leave the rest of the file untouched. This is cleanup, not a required migration.
-
-### Keeping the old behavior (opt-in)
-
-If your team treats the materialized templates as **reviewed, committed artifacts** and wants
-`/constitution` to keep propagating, install the bundled **`constitution-sync`** preset:
-
-```bash
-specify preset add constitution-sync
-```
-
-It wraps the core `/constitution` command and re-adds the propagation pass. It does **not** edit
-versioned preset- or extension-provided templates or command files (those are owned by their
-packages and are recomposed on reconciliation). Note that this edit-in-place propagation model
-conflicts with the composition model used by the rest of the SDD commands when they are
-preset/extension-managed — see the "Interaction with the resolution stack" section in
-`presets/constitution-sync/README.md` for the tradeoffs and when to prefer the default instead.
-
---
-
 ## Common Scenarios

 ### Scenario 1: "I just want new slash commands"
@@ -314,12 +248,14 @@ specify extension update
 This happens with IDE-based agents (Kilo Code, Cline, etc.).

 ```bash
-# For Kilo Code, inspect both current and legacy command folders
-ls -la .kilo/commands/
-ls -la .kilocode/workflows/
+# Find the agent folder (example: .kilocode/workflows/)
+cd .kilocode/workflows/
+
+# List all files
+ls -la

 # Delete old command files
-rm .kilocode/workflows/speckit.old-command-name.md
+rm speckit.old-command-name.md

 # Restart your IDE
 ```
@@ -371,7 +307,7 @@ Alternatively, run the `/speckit.specify` command which creates `.specify/featur
 2. **For CLI-based agents**, verify files exist:

   ```bash
-   ls -la .claude/skills/        # Claude Code
+   ls -la .claude/commands/      # Claude Code
   ls -la .gemini/commands/      # Gemini
   ls -la .cursor/skills/      # Cursor
   ls -la .pi/prompts/           # Pi Coding Agent
@@ -420,7 +356,7 @@ This warning appears when you run `specify init --here` (or `specify init .`) in

 Only Spec Kit infrastructure files:

- Agent command/skill files (`.claude/skills/`, `.github/prompts/`, etc.)
+- Agent command files (`.claude/commands/`, `.github/prompts/`, etc.)
 - Scripts in `.specify/scripts/`
 - Templates in `.specify/templates/`
 - Missing memory files such as `.specify/memory/constitution.md` may be created from templates; an existing constitution is preserved
@@ -509,7 +445,7 @@ Once you've run `specify init`, the slash commands (like `/speckit.specify`, `/s
   ls -la .github/prompts/

   # For Claude
-   ls -la .claude/skills/
+   ls -la .claude/commands/

   # For Pi
   ls -la .pi/prompts/
@@ -2,7 +2,6 @@
  "_comment": "Default coding agent context file per integration, owned by the agent-context extension. Used to self-seed agent-context-config.yml when it declares no context_file/context_files. Keyed by the Spec Kit integration key recorded in .specify/init-options.json. This mapping is independent of the Specify CLI by design.",
  "agents": {
    "agy": "AGENTS.md",
-    "alquimia": "ALQUIMIA.md",
    "amp": "AGENTS.md",
    "auggie": ".augment/rules/specify-rules.md",
    "bob": "AGENTS.md",
@@ -176,18 +176,13 @@ _opts_lines=()
 while IFS= read -r _line || [[ -n "$_line" ]]; do
  _opts_lines+=("$_line")
 done < <(printf '%s\n' "$_raw_opts")
-if (( ${#_opts_lines[@]} < 1 )); then
-  echo "agent-context: malformed config parser output; expected at least the context_files line, got ${#_opts_lines[@]}; skipping update." >&2
+if (( ${#_opts_lines[@]} < 3 )); then
+  echo "agent-context: malformed config parser output; expected 3 lines (context_files, marker_start, marker_end), got ${#_opts_lines[@]}; skipping update." >&2
  exit 0
 fi
-# The marker lines may be absent: the $(...) capture above strips trailing
-# newlines, so blank markers (the config omitting context_markers and relying on
-# defaults) collapse the 3-line output to fewer lines. Default them to empty here
-# and let the DEFAULT_START/END substitution below fill them in, matching the
-# Python and PowerShell ports.
 CONTEXT_FILES_JSON="${_opts_lines[0]}"
-MARKER_START="${_opts_lines[1]:-}"
-MARKER_END="${_opts_lines[2]:-}"
+MARKER_START="${_opts_lines[1]}"
+MARKER_END="${_opts_lines[2]}"

 if ! _context_files_raw="$("$_python" - "$CONTEXT_FILES_JSON" <<'PY'
 import json
@@ -11,9 +11,8 @@ Usage: update_agent_context.py [plan_path]

 When ``plan_path`` is omitted, the script derives it from
 ``.specify/feature.json`` (written by /speckit-specify). Falls back to the most
-recently modified ``plan.md`` found anywhere under ``specs/`` — scoped layouts
-nest it as ``specs/<scope>/<feature>/plan.md`` — only when feature.json is
-absent or its plan does not exist yet.
+recently modified ``specs/*/plan.md`` only when feature.json is absent or its
+plan does not exist yet.
 """

 from __future__ import annotations
@@ -173,31 +172,16 @@ def _resolve_plan_path(project_root: str) -> str:

    if not plan_path:
        root = Path(project_root).resolve()
-        specs = root / "specs"
-
-        def _resolved_rel(p: Path) -> Path | None:
-            # Resolve symlinks before checking containment: relative_to() is
-            # lexical and would otherwise accept a plan reached through a specs/
-            # symlink that points outside the project, emitting an
-            # in-project-looking path for an out-of-project file (or picking it
-            # as "most recent").
+        plans = sorted(
+            (root / "specs").glob("*/plan.md"),
+            key=lambda p: p.stat().st_mtime,
+            reverse=True,
+        )
+        if plans:
            try:
-                return p.resolve().relative_to(root)
-            except (OSError, ValueError):
-                return None
-
-        # Recurse (rather than the old one-level specs/*/plan.md glob) so scoped
-        # layouts created via SPECIFY_FEATURE_DIRECTORY, e.g.
-        # specs/<scope>/<feature>/plan.md, are still discovered when
-        # feature.json is absent (#3024). Mirrors the bash and PowerShell twins.
-        candidates = []
-        for p in specs.rglob("plan.md"):
-            rel = _resolved_rel(p)
-            if rel is not None:
-                candidates.append((p, rel))
-        candidates.sort(key=lambda pr: pr[0].stat().st_mtime, reverse=True)
-        if candidates:
-            plan_path = candidates[0][1].as_posix()
+                plan_path = plans[0].relative_to(root).as_posix()
+            except ValueError:
+                plan_path = ""
    return plan_path


@@ -6,8 +6,6 @@ Discovery answers *"is this worth building?"* Delivery answers *"how do we build

 ## Overview

-`assess` runs inside an initialized Spec Kit project (it writes assessments under `.specify/assessments/`), but that project can be **completely empty of source code** — a freshly initialized project with no code works just as well as an established codebase. The input is just an idea: pasted text, a URL, or a ticket need no existing code, while a codebase pointer lets you assess an idea for code that already exists. Neither starting point is more "correct" than the other.
-
 Each idea lives in its own directory under `.specify/assessments/<slug>/`, with one Markdown artifact per stage:

 ```
@@ -21,8 +21,6 @@ The user input is the idea and (optionally) a slug. Treat it as one of:
 3. **A codebase pointer** — phrasing like "an idea for this repo" or a path. Read enough of the repository to record what the idea relates to.
 4. **A mix** of the above.

-There is **no requirement for existing source code**: within an initialized Spec Kit project, intake works just as well when the project is empty of code as when it already has a codebase. Pasted text or a URL (options 1–2) need no existing codebase; a codebase pointer (option 3) targets existing code. Both are equally valid.
-
 If the input is empty, ask the user for the idea (interactive), or stop with a note that there is nothing to intake (automated).

 ## Slug Resolution
@@ -1,43 +1,8 @@
 {
  "schema_version": "1.0",
-  "updated_at": "2026-08-04T00:00:00Z",
+  "updated_at": "2026-07-21T00:00:00Z",
  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/extensions/catalog.community.json",
  "extensions": {
-    "adrkit": {
-      "name": "adrkit — decision memory for spec-driven development",
-      "id": "adrkit",
-      "description": "Pulls the decisions governing this work into agent context, checks produced plans against them, and drafts an ADR from a plan artifact.",
-      "author": "Mark Beacom (@mbeacom)",
-      "version": "0.1.2",
-      "download_url": "https://github.com/mbeacom/adrkit/releases/download/spec-kit-v0.1.2/adrkit.zip",
-      "repository": "https://github.com/mbeacom/adrkit",
-      "homepage": "https://adrkit.dev",
-      "documentation": "https://github.com/mbeacom/adrkit/blob/main/packages/adapters/spec-kit/README.md",
-      "changelog": "https://github.com/mbeacom/adrkit/blob/main/CHANGELOG.md",
-      "license": "Apache-2.0",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.13.0,<0.16.0",
-        "tools": [{ "name": "adr", "version": ">=0.3.0", "required": true }]
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 1
-      },
-      "tags": [
-        "adr",
-        "governance",
-        "decision-records",
-        "architecture",
-        "compliance"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-08-03T00:00:00Z",
-      "updated_at": "2026-08-03T00:00:00Z"
-    },
    "aide": {
      "name": "AI-Driven Engineering (AIDE)",
      "id": "aide",
@@ -325,8 +290,8 @@
      "id": "architecture-guard",
      "description": "Framework-agnostic architecture review extension for validating implementation against governance and architecture constitutions, detecting architectural drift, and generating non-blocking refactor tasks.",
      "author": "DyanGalih",
-      "version": "1.13.1",
-      "download_url": "https://github.com/DyanGalih/spec-kit-architecture-guard/archive/refs/tags/v1.13.1.zip",
+      "version": "1.8.17",
+      "download_url": "https://github.com/DyanGalih/spec-kit-architecture-guard/archive/refs/tags/v1.8.17.zip",
      "repository": "https://github.com/DyanGalih/spec-kit-architecture-guard",
      "homepage": "https://github.com/DyanGalih/spec-kit-architecture-guard",
      "documentation": "https://github.com/DyanGalih/spec-kit-architecture-guard/blob/main/docs/architecture-overview.md",
@@ -338,7 +303,7 @@
        "speckit_version": ">=0.1.0"
      },
      "provides": {
-        "commands": 14,
+        "commands": 10,
        "hooks": 3
      },
      "tags": [
@@ -348,22 +313,21 @@
        "refactor",
        "workflow",
        "governance",
-        "guardrails",
-        "hygiene"
+        "guardrails"
      ],
      "verified": false,
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-05-05T07:26:00Z",
-      "updated_at": "2026-07-24T00:00:00Z"
+      "updated_at": "2026-06-08T00:00:00Z"
    },
    "archive": {
      "name": "Archive Extension",
      "id": "archive",
      "description": "Archive merged features into main project memory, resolving gaps and conflicts.",
      "author": "Stanislav Deviatov",
-      "version": "1.1.0",
-      "download_url": "https://github.com/stn1slv/spec-kit-archive/archive/refs/tags/v1.1.0.zip",
+      "version": "1.0.0",
+      "download_url": "https://github.com/stn1slv/spec-kit-archive/archive/refs/tags/v1.0.0.zip",
      "repository": "https://github.com/stn1slv/spec-kit-archive",
      "homepage": "https://github.com/stn1slv/spec-kit-archive",
      "documentation": "https://github.com/stn1slv/spec-kit-archive/blob/main/README.md",
@@ -388,7 +352,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-03-14T00:00:00Z",
-      "updated_at": "2026-08-04T00:00:00Z"
+      "updated_at": "2026-03-14T00:00:00Z"
    },
    "azure-devops": {
      "name": "Azure DevOps Integration",
@@ -525,46 +489,6 @@
      "created_at": "2026-04-17T00:00:00Z",
      "updated_at": "2026-04-17T00:00:00Z"
    },
-    "blueprint-index": {
-      "name": "Blueprint Index — Living Architecture Map",
-      "id": "blueprint-index",
-      "description": "Living architecture map for brownfield and greenfield projects, with a deterministic CI gate that blocks contradictions between the map, specs, and code while warning on non-blocking drift.",
-      "author": "ogil109",
-      "version": "0.2.0",
-      "download_url": "https://github.com/ogil109/spec-kit-blueprint/releases/download/v0.2.0/blueprint.zip",
-      "repository": "https://github.com/ogil109/spec-kit-blueprint",
-      "homepage": "https://github.com/ogil109/spec-kit-blueprint/tree/main",
-      "documentation": "https://github.com/ogil109/spec-kit-blueprint/blob/main/README.md",
-      "changelog": "https://github.com/ogil109/spec-kit-blueprint/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.10.0",
-        "tools": [
-          { "name": "bash", "required": false },
-          { "name": "git", "required": false }
-        ]
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 0
-      },
-      "tags": [
-        "blueprint",
-        "architecture",
-        "coherence",
-        "drift",
-        "brownfield",
-        "autonomous",
-        "ci"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-24T00:00:00Z",
-      "updated_at": "2026-07-24T00:00:00Z"
-    },
    "branch-convention": {
      "name": "Branch Convention",
      "id": "branch-convention",
@@ -811,8 +735,8 @@
      "id": "charter",
      "description": "Compose modular project constitutions from shared fragment registries. Centralize governance rules, select per-project fragments, track upstream changes, and keep multi-project setups consistent.",
      "author": "Fyloss",
-      "version": "0.5.1",
-      "download_url": "https://github.com/Fyloss/spec-kit-charter/archive/refs/tags/v0.5.1.zip",
+      "version": "0.3.1",
+      "download_url": "https://github.com/Fyloss/spec-kit-charter/archive/refs/tags/v0.3.1.zip",
      "repository": "https://github.com/Fyloss/spec-kit-charter",
      "homepage": "https://github.com/Fyloss/spec-kit-charter",
      "documentation": "https://github.com/Fyloss/spec-kit-charter/tree/master/docs",
@@ -821,8 +745,7 @@
      "category": "process",
      "effect": "read-write",
      "requires": {
-        "speckit_version": ">=0.11.9",
-        "tools": [{ "name": "git", "required": false }]
+        "speckit_version": ">=0.11.9"
      },
      "provides": {
        "commands": 5,
@@ -839,7 +762,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-07-06T00:00:00Z",
-      "updated_at": "2026-08-04T00:00:00Z"
+      "updated_at": "2026-07-06T00:00:00Z"
    },
    "ci-guard": {
      "name": "CI Guard",
@@ -1106,41 +1029,6 @@
      "created_at": "2026-03-29T00:00:00Z",
      "updated_at": "2026-03-29T00:00:00Z"
    },
-    "contextforge-mcp": {
-      "name": "ContextForge MCP",
-      "id": "contextforge-mcp",
-      "description": "Integrates codebase-memory-mcp + headroom into Spec Kit — graph-based code intelligence and context compression for the implement phase.",
-      "author": "capatinore",
-      "version": "0.1.0",
-      "download_url": "https://github.com/capatinore/contextforge-mcp/releases/download/ext-v0.1.0/contextforge-mcp-speckit-extension.zip",
-      "repository": "https://github.com/capatinore/contextforge-mcp",
-      "homepage": "https://github.com/capatinore/contextforge-mcp",
-      "documentation": "https://github.com/capatinore/contextforge-mcp/blob/main/README.md",
-      "changelog": "",
-      "license": "MIT",
-      "category": "code",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.10.0"
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 0
-      },
-      "tags": [
-        "mcp",
-        "code-intelligence",
-        "context-compression",
-        "tokens",
-        "claude",
-        "spec-driven-development"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-13T00:00:00Z",
-      "updated_at": "2026-07-13T00:00:00Z"
-    },
    "cost": {
      "name": "Cost Tracker",
      "id": "cost",
@@ -1690,8 +1578,8 @@
      "id": "gates",
      "description": "Deterministic quality enforcement for Spec Kit across agent hooks, git checks, and CI pipelines with one policy file and one verify entrypoint for identical results at every boundary.",
      "author": "schwichtgit",
-      "version": "0.3.3",
-      "download_url": "https://github.com/schwichtgit/spec-gates/releases/download/v0.3.3/gates-0.3.3.zip",
+      "version": "0.3.2",
+      "download_url": "https://github.com/schwichtgit/spec-gates/releases/download/v0.3.2/gates-0.3.2.zip",
      "repository": "https://github.com/schwichtgit/spec-gates",
      "homepage": "https://github.com/schwichtgit/spec-gates",
      "documentation": "https://github.com/schwichtgit/spec-gates/blob/main/docs/how-it-works.md",
@@ -1735,7 +1623,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-07-09T00:00:00Z",
-      "updated_at": "2026-07-27T00:00:00Z"
+      "updated_at": "2026-07-15T00:00:00Z"
    },
    "github-issues": {
      "name": "GitHub Issues Integration 1",
@@ -1932,40 +1820,6 @@
      "created_at": "2026-06-23T00:00:00Z",
      "updated_at": "2026-06-30T00:00:00Z"
    },
-    "intent": {
-      "name": "Intent Reconciliation",
-      "id": "intent",
-      "description": "Reconcile implementation-discovered decisions against approved feature intent",
-      "author": "SuhaibAslam",
-      "version": "1.0.2",
-      "download_url": "https://github.com/SuhaibAslam/spec-kit-reconcile/archive/refs/tags/v1.0.2.zip",
-      "repository": "https://github.com/SuhaibAslam/spec-kit-reconcile",
-      "homepage": "https://github.com/SuhaibAslam/spec-kit-reconcile",
-      "documentation": "https://github.com/SuhaibAslam/spec-kit-reconcile/blob/main/README.md",
-      "changelog": "https://github.com/SuhaibAslam/spec-kit-reconcile/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.12.0"
-      },
-      "provides": {
-        "commands": 3,
-        "hooks": 0
-      },
-      "tags": [
-        "intent",
-        "decisions",
-        "reconciliation",
-        "drift",
-        "workflow"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-07-29T00:00:00Z",
-      "updated_at": "2026-07-29T00:00:00Z"
-    },
    "issue": {
      "name": "GitHub Issues Integration 2",
      "id": "issue",
@@ -2180,11 +2034,11 @@
      "id": "linear-weave",
      "description": "Weave Spec Kit into Linear: pull requirements, mirror tasks.md into sub-issues, sync statuses.",
      "author": "Tony Woodhouse",
-      "version": "1.0.1",
-      "download_url": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.1.zip",
+      "version": "1.0.0",
+      "download_url": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.0.zip",
      "repository": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
      "homepage": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
-      "documentation": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/README.md",
+      "documentation": "https://github.com/tonydwoodhouse/spec-kit-linear-weave#readme",
      "changelog": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/CHANGELOG.md",
      "license": "MIT",
      "category": "integration",
@@ -2207,7 +2061,7 @@
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-07-21T00:00:00Z",
-      "updated_at": "2026-07-27T00:00:00Z"
+      "updated_at": "2026-07-21T00:00:00Z"
    },
    "loop": {
      "name": "Loop Engineering",
@@ -4489,47 +4343,6 @@
      "created_at": "2026-06-22T00:00:00Z",
      "updated_at": "2026-06-22T00:00:00Z"
    },
-    "tdd": {
-      "name": "TDD Extension",
-      "id": "tdd",
-      "description": "Drives spec-kit implementation with tests: a language-agnostic red-green-refactor loop with a per-feature test list, recorded red and green evidence, and mutation-checked test strength.",
-      "author": "d0whc3r",
-      "version": "1.1.2",
-      "download_url": "https://github.com/d0whc3r/spec-kit-tdd/releases/download/v1.1.2/tdd-1.1.2.zip",
-      "repository": "https://github.com/d0whc3r/spec-kit-tdd",
-      "homepage": "https://d0whc3r.github.io/spec-kit-tdd/",
-      "documentation": "https://github.com/d0whc3r/spec-kit-tdd/wiki",
-      "changelog": "https://github.com/d0whc3r/spec-kit-tdd/blob/main/CHANGELOG.md",
-      "license": "MIT",
-      "category": "process",
-      "effect": "read-write",
-      "requires": {
-        "speckit_version": ">=0.11.9"
-      },
-      "provides": {
-        "commands": 4,
-        "hooks": 3
-      },
-      "tags": [
-        "acceptance-tests",
-        "mutation-testing",
-        "property-based-testing",
-        "quality",
-        "red-green-refactor",
-        "spec-kit",
-        "spec-kit-extension",
-        "tdd",
-        "test-driven-development",
-        "test-first",
-        "testing",
-        "unit-tests"
-      ],
-      "verified": false,
-      "downloads": 0,
-      "stars": 0,
-      "created_at": "2026-08-04T00:00:00Z",
-      "updated_at": "2026-08-04T00:00:00Z"
-    },
    "team-assign": {
      "name": "Team Assign",
      "id": "team-assign",
@@ -4964,40 +4777,36 @@
    "verify-review-ship": {
      "name": "Verify Review Ship",
      "id": "verify-review-ship",
-      "description": "Post-convergence operational verification, technical review, learning governance, and transactional delivery.",
+      "description": "Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows.",
      "author": "Carlos Eduardo Gevaerd Araujo",
-      "version": "0.4.2",
-      "download_url": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.4.2.zip",
-      "sha256": "71dceef5bf81d7ac54faa26bb5cf279554815a4928ee8d0c8e9bfb4c3e2bb0ab",
+      "version": "0.1.0",
+      "download_url": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip",
      "repository": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
      "homepage": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
      "documentation": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/README.md",
      "changelog": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/CHANGELOG.md",
      "license": "MIT",
      "category": "process",
-      "effect": "read-write",
+      "effect": "read-only",
      "requires": {
-        "speckit_version": ">=0.11.2"
+        "speckit_version": ">=0.1.0"
      },
      "provides": {
        "commands": 3,
-        "hooks": 0
+        "hooks": 1
      },
      "tags": [
        "quality",
        "review",
        "shipping",
-        "merge",
-        "cleanup",
-        "learning",
-        "governance",
-        "agent-skills"
+        "workflow",
+        "testing"
      ],
      "verified": false,
      "downloads": 0,
      "stars": 0,
      "created_at": "2026-07-10T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-10T00:00:00Z"
    },
    "verify-tasks": {
      "name": "Verify Tasks Extension",
@@ -1,17 +1,8 @@
 {
  "schema_version": "1.0",
-  "updated_at": "2026-07-27T00:00:00Z",
+  "updated_at": "2026-07-17T00:00:00Z",
  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/integrations/catalog.json",
  "integrations": {
-    "alquimia": {
-      "id": "alquimia",
-      "name": "Alquimia AI",
-      "version": "1.0.0",
-      "description": "Alquimia AI CLI integration",
-      "author": "spec-kit-core",
-      "repository": "https://github.com/github/spec-kit",
-      "tags": ["alquimia"]
-    },
    "claude": {
      "id": "claude",
      "name": "Claude Code",
@@ -4,7 +4,7 @@ This edition covers Spec Kit activity in April 2026. Seventeen releases shipped

 | **Spec Kit Core (Apr 2026)** | **Community & Content** | **SDD Ecosystem & Next** |
 | --- | --- | --- |
-| Seventeen releases shipped with major features: integration plugin architecture, workflow engine, preset composition, integration catalog, bundled lean preset, documentation site, and academic citation support. Three new agents added (Forgecode, Goose, Devin for Terminal). The repo grew from ~82k to **92,038 stars**. [\[github.com\]](https://github.com/github/spec-kit/releases) | Thoughtworks Technology Radar placed Spec Kit in the "Assess" ring. Community catalog grew from 26 to **83 extensions** and from 2 to **12 presets**. External coverage continued across developer blogs and industry press. XB Software documented a real legacy project. Fabián Silva shipped the Caramelo VS Code extension. | Matt Rickard argued for "smaller specs, harder checks." Will Torber's three-framework comparison recommended OpenSpec for most teams. The "Spec Layer" debate emerged: specs as constraint surfaces for AI agents. Spec Kit leads in breadth and portability; competitors differentiate on drift detection and orchestration depth. |
+| Seventeen releases shipped with major features: integration plugin architecture, workflow engine, preset composition, integration catalog, bundled lean preset, documentation site, and academic citation support. Three new agents added (Forgecode, Goose, Devin for Terminal). The repo grew from ~82k to **92,038 stars**. [\[github.com\]](https://github.com/github/spec-kit/releases) | Thoughtworks Technology Radar placed Spec Kit in the "Assess" ring. Community catalog grew from 26 to **83 extensions** and from 2 to **12 presets**. 12 substantive external articles published. XB Software documented a real legacy project. Fabián Silva shipped the Caramelo VS Code extension. | Matt Rickard argued for "smaller specs, harder checks." Will Torber's three-framework comparison recommended OpenSpec for most teams. The "Spec Layer" debate emerged: specs as constraint surfaces for AI agents. Spec Kit leads in breadth and portability; competitors differentiate on drift detection and orchestration depth. |

 ***

@@ -94,7 +94,7 @@ On **April 15**, the **Thoughtworks Technology Radar Volume 34** placed GitHub S

 ### Developer Articles and Blog Posts

-April produced a steady stream of external articles.
+April produced 12 substantive external articles (plus one excluded as AI-generated SEO spam).

 **Matt Rickard** published *"The Spec Layer: Why Spec-Driven Development (SDD) Works"* on April 1. His thesis: specs reduce execution freedom for AI agents, functioning as constraint surfaces. He compared Spec Kit, Kiro, OpenSpec, Tessl, Intent, and Symphony, and advocated for **"smaller specs, harder checks, less guessing."** [\[blog.matt-rickard.com\]](https://blog.matt-rickard.com/p/the-spec-layer)

@@ -1,152 +0,0 @@
-# Spec Kit - July 2026 Newsletter
-
-This edition covers Spec Kit activity in July 2026 — a month of hardening and expanding the envelope. Twenty-eight releases shipped (v0.12.3 through v0.15.1), crossing three minor bumps and delivering three headline capabilities: the **`assess` "Idea Assessment Pipeline" extension**, which pushes spec-driven development *upstream* of the spec to answer "should we even build this?"; the new **`py` (Python) script type** and the broad shell→Python port that underpins it; and a **first-class agent-native runtime events layer** for integrations. Beneath the features, the month's dominant engineering theme was a sustained **security-hardening wave** — bounded HTTP reads, strict redirect validation, TOCTOU-race elimination, and defensive validation across the workflow engine. Externally, coverage broadened structurally: mainstream tech press (heise online) covered the v0.13 `assess` release in two languages, and a **companion-tooling ecosystem** bloomed around the project — spec↔code drift detectors, model-sizing advisors, and testing-gap tools all built *on top of* Spec Kit. A summary is in the table below, followed by details.
-
-| **Spec Kit Core (Jul 2026)** | **Community & Content** | **SDD Ecosystem & Next** |
-| --- | --- | --- |
-| Twenty-eight releases shipped (v0.12.3–v0.15.1), crossing v0.13, v0.14, and v0.15. Headline features: the `assess` **Idea Assessment Pipeline** extension (capture→evidence→refine→design→go/clarify/kill), the new **`py` script type** plus a shell→Python port of the core scripts, git extension, and agent-context updater, and an **agent-native runtime events layer** for integrations. Three agents joined (Grok Build, Factory Droid CLI, Alquimia AI), the label-driven **bug-fix/bug-test** automation completed the triage pipeline, and a heavy **security-hardening** wave landed. The repo grew from ~117,400 to **124,655 stars**. [\[github.com\]](https://github.com/github/spec-kit/releases) | The community extension catalog grew from 125 to **144 entries**; presets reached **29**, community workflows **2**, bundles **1**. **heise online** covered the v0.13 `assess` release in English and German. Coverage shifted toward comparisons, companion tooling, and "who verifies the spec?" critiques. **~258 contributors** now listed. | A **companion-tooling ecosystem** emerged — artgraph (deterministic spec↔code drift), SpecJudge (model right-sizing), GAUNTLEX (security-testing gap), and custom skills like `speckit-next` and `prefill`. Comparisons increasingly pit Spec Kit against Kiro; balanced reviews keep flagging documentation proliferation and cognitive load, precisely the gaps the `assess` upstream step and the drift/companion ecosystem are built to close. |
-
-***
-
-> **Hardening the Foundation, Expanding the Envelope.** If June was defined by external validation, July was defined by internal consolidation and reach. No single release carried the weight of `converge` or `bundle`, but the month moved the project in two directions at once. It reached *upstream* — the new `assess` pipeline lets a team evaluate an idea (capture evidence, refine, design, then go/clarify/kill) *before* a spec exists, extending SDD past the spec into the decision to build. And it reached *down to the metal* — a new `py` script type and a systematic port of the core scripts, git extension, and agent-context updater from shell to Python, alongside a security-hardening wave that bounded every HTTP read, validated every redirect hop, eliminated file-race conditions, and taught the workflow engine to fail loudly instead of crashing on malformed input. Meanwhile the ecosystem answered the project's most-cited critique — "who verifies the spec, and who reads all this documentation?" — not with complaints but with *code*: a wave of companion tools built directly on Spec Kit artifacts. None of this happens without the community — the contributors, extension and preset authors, bundle builders, agent-integration maintainers, and practitioners writing in more than 20 languages. Thank you.
-
-## Spec Kit Project Updates
-
-### Releases Overview
-
-**v0.12.3–v0.12.18** (July 1–17) was the month's longest patch run and carried two features amid heavy hardening. The **`py` script type** landed (#3285), adding Python interpreter resolution alongside the existing `sh`/`ps` options, and the **label-driven bug-fix (#3258) and bug-test (#3239) agentic workflows** completed the `bug-assess → bug-test → bug-fix` triage pipeline. The systematic shell→Python port began here: the **`update-agent-context` script** (#3387), the **git extension scripts** (#3400), and a **`check-prerequisites` proof-of-concept** (#3302) were all ported. **PyPI was documented as a first-class second install route** (#3516). New agents arrived — **Grok Build** (#3535) as a skills-based integration — while **Roo Code was retired** as a shut-down product (#3212). The rest was a broad defensive-validation sweep across the workflow engine (case-insensitive gate reject, quote-aware interpolation, host-less catalog-URL rejection, and dozens of "fail loudly on malformed input" guards). [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-**v0.13.0–v0.13.4** (July 17–22) delivered the month's headline feature: the **`assess` Idea Assessment Pipeline extension** (#3568), a pre-spec evaluation flow. The release also completed the Python port of the three core scripts — **`create-new-feature`, `setup-plan`, and `setup-tasks`** (#3386) — and added **Azure DevOps `az`-CLI token acquisition** hardening (#3527), **community bundle submission automation** (#3553), and the standalone **`WorkflowResolver`** refactor (#3557). **Factory Droid CLI** joined as an integration (#3587), **Bob was updated to a skills-based layout for Bob 2.0** (#3415), the **`pipeline` workflow** was added to the community catalog (#3338), and the **spec-of-specs feature-breakdown** approach was documented for handling complex features (#3648). [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-**v0.14.0–v0.14.4** (July 23–29) crossed a minor with a **security-hardening focus**: **bounded HTTP reads and strict redirect enforcement** (#3140, #3671), **secured extension/preset archive downloads** (#3141), and the **removal of the `shell` parameter from `run_command`** (#3716). The **git extension gained configurable Conventional Commit support** (#3413), the wheel now **bundles `scripts/python`** so `--script py` works from a clean install (#3665), and **Alquimia AI** joined as the month's third new agent (#2734). Documentation added a **Simplified Chinese README translation** (#3740), and the constitution stopped **propagating guidance into templates** (#3790). A long run of bundler, preset, and integration validation fixes rounded out the cluster. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-**v0.15.0–v0.15.1** (July 30–31) closed the month with a **first-class agent-native runtime events layer for integrations** (#3704) — the release's headline — plus a continued security pass: **TOCTOU-race elimination in file-unlink calls** (#3811, #3815, #3819), **UTF-8 encoding on registry file opens** (#3810, #3816), and **hardening of the extension URL-download cache against symlink/junction races** (#3869). Workflows gained the ability to **bind a gate verdict to a workflow input via `verdict_input`** (#3725), an opt-in **`constitution-sync` preset** shipped (#3873), the **`yolo` workflow** was added to the community catalog (#3864), and installs gained **tar-archive support** (#3874). [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### The Idea Assessment Pipeline: `assess`
-
-July's headline feature was the **`assess` extension** (#3568), an *idea-assessment pipeline* that ships as an opt-in extension and extends spec-driven development one step further upstream than it has ever reached. Where the core lifecycle begins at `/speckit.specify` — assuming the decision to build has already been made — `assess` addresses the question that comes *before* the spec: **should this idea be built at all, and is it understood well enough to specify?**
-
-The pipeline runs a staged flow — **capture → evidence → refine → design → decision** — that takes a raw idea, gathers supporting evidence, refines it into something concrete, sketches a design, and terminates in an explicit **go / clarify / kill** verdict. A `go` feeds a well-formed problem into the existing `/speckit.specify` step; a `clarify` routes back for more information; a `kill` stops work before a line of spec is written. Its input is just an idea — pasted text, a URL, a ticket, or a codebase pointer — so the pipeline works **equally well on an empty, freshly-initialized project or on an existing codebase** (#3732); a team can evaluate a green idea before any scaffolding exists, or assess a change against a repo that already has one.
-
-The feature drew the month's most prominent mainstream-press coverage: **heise online** ran *"From Idea to Spec: The New Feature in Spec Kit 0.13"* in both English and German, framing `assess` as the notable addition of the 0.13 line alongside the Azure DevOps CLI support and the bundler/preset validation fixes. Coming from a major European technology outlet rather than a developer blog, it was a signal that Spec Kit's release cadence is now tracked as mainstream tooling news. [\[heise.de\]](https://www.heise.de/en/news/From-Idea-to-Spec-The-New-Feature-in-Spec-Kit-0-13-11371866.html)
-
-### The Python Migration: the `py` Script Type
-
-Spec Kit's second July theme was quieter but structurally important: the project began migrating its shell scripts to **Python**. The new **`py` script type** (#3285) joins `sh` (bash) and `ps` (PowerShell) as a third option at `specify init`, backed by Python-interpreter resolution that skips broken stubs (including the Windows Store `python3` alias, #3385). The `py` type is the project's answer to the perennial bash/PowerShell parity tax — every script fix previously had to be written twice and kept in sync, a recurring source of the Windows-parity bugs that filled prior months' changelogs.
-
-Behind the new type, a systematic port landed piece by piece across the month: the **`update-agent-context`** updater (#3387), the **git extension scripts** (#3400), a **`check-prerequisites`** proof-of-concept (#3302), and finally the three core scripts — **`create-new-feature`, `setup-plan`, and `setup-tasks`** (#3386). The wheel was updated to bundle `scripts/python` so `--script py` works from a clean PyPI install (#3665), and the installation docs and init option table were updated to document the new type and the sh/ps migration plan (#3284, #3640). The end state is a single, cross-platform script implementation that removes an entire class of parity bugs. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### Agent-Native Runtime Events
-
-The v0.15.0 headline was a **first-class agent-native runtime events layer for integrations** (#3704). It bridges Spec Kit to the host agent's own lifecycle via a set of canonical, snake_case event names — `session_start`, `pre_tool_use`, `post_tool_use`, `user_prompt_submit`, `stop`, and `session_end`. A lightweight, zero-dependency **Event Dispatcher** (`.specify/events.py`) is scaffolded during `specify init`, and per-integration **Event Adapters** translate each canonical event into the agent's *native* hook configuration — `.github/hooks/speckit.json` (bash/PowerShell variants) for **Copilot CLI**, `.claude/settings.json` for Claude Code, `.cursor/hooks.json` for Cursor, `.codex/config.toml` for Codex, a TypeScript plugin for opencode, and native settings merges for Gemini, Qwen, Devin, and Tabnine — so extension authors declare `events:` in `extension.yml` once and never learn agent-specific names. Resolution is a four-tier stack (CLI `--events false` → user `.specify/integration-events.yml` override → extension-declared events → built-in defaults), and multiple extensions declaring the same event all run. The change accompanied a broader integration-refinement run: agents that use an always-slash invocation (Droid, Forge, Cline) now render hyphenated `/speckit-<name>` commands correctly (#3688, #3642, #3622), native skill-invocation prefixes are preserved (#3663), and several agents (kiro-cli, Lingma, Pi, omp) were declared multi-install-safe. The through-line is that integrations are increasingly *native* to each agent rather than a lowest-common-denominator overlay. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### The Security-Hardening Wave
-
-The dominant engineering theme across all twenty-eight releases was **security and robustness**. The work fell into three bands. **Bounded I/O:** every catalog, download, and bundle HTTP response is now read under a byte cap with strict redirect validation on every hop (#3140, #3671, #3763, #3141), closing a class of unbounded-read / DoS exposure. **Race elimination:** TOCTOU races in file-unlink and state-file handling were removed (#3811, #3815, #3819), the extension URL-download cache was hardened against symlink and junction races (#3869), and registry file opens were pinned to UTF-8 (#3810, #3816). **Injection and input hardening:** the `shell` parameter was removed from `run_command` (#3716), user-supplied catalog metadata is escaped in every discovery/list/`init` output path (#3772, #3773, #3774, #3806, #3826, #3863), and catalog URLs are re-validated *after* redirects to preserve HTTPS/host guarantees (#3523, #3524).
-
-Running alongside this was a systematic **"fail loudly, don't crash"** campaign across the workflow engine and catalog loaders: dozens of PRs replaced raw `ValueError`/`OverflowError`/crash paths with clean validation errors on malformed input — non-string commands, prompts, integrations, and models; non-list branches and `wait_for` entries; `priority: .inf` and boolean priorities; non-mapping manifest blocks; and superscript-digit gate prompts. The entire month's hardening arrived as prevention rather than response. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### The Workflow Engine & Bundles Mature
-
-Beyond hardening, the **workflow engine** kept gaining capability. Steps can now read their **workflow source directory** (#3469), the shell and prompt steps got **configurable, validated timeouts** (#3404, #3847, #3768), a **gate verdict can bind to a workflow input** via `verdict_input` (#3725), and the **`WorkflowResolver`** was extracted as a standalone component (#3557). Two community workflows reached the catalog — the guided **`pipeline`** (#3338, which chains into the core `/speckit.converge`) and **`yolo`** (#3864) — bringing the standalone-workflow count to two.
-
-The **bundle subsystem** introduced in June matured through a long tail of correctness work — reproducible builds via canonical POSIX arcnames (#3658), literal UTF-8 manifest dumps (#3660), strict rejection of malformed `requires`/`provides`/`integration`/`catalogs` blocks, and a clean `BundlerError` on malformed download URLs (#3586). **Community bundle submission automation** landed (#3553) and the **SicarioSpec Security & Governance Bundle** became a cataloged community bundle (#3636), making bundles a live community-submittable artifact type in practice. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### Agent Integrations
-
-The agent portfolio grew net **+3 to 37 integrations**. Three joined — **Grok Build** (#3535), **Factory Droid CLI** (#3587, closing the 300+-day #822), and **Alquimia AI** (#2734) — while **Roo Code** was retired as a shut-down product (#3212). **Bob** was migrated to a skills-based layout for Bob 2.0 (#3415), **Kilocode** now installs commands under `.kilo/commands` (#3672), and a broad correctness pass fixed hyphenated-command rendering and dispatch for the always-slash agents (Droid, Forge, Cline) and preserved native skill-invocation prefixes (#3663). The pattern continues from June — pruning dead products while making the surviving integrations more native to each agent. [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-### The Extension & Preset Ecosystem
-
-The community extension catalog grew from 125 to **144 entries** during July — nineteen net additions. Community presets grew from 23 to **29**, community workflows reached **2**, and the first community **bundle** (SicarioSpec) was cataloged.
-
-Notable new extensions by category:
-
- **Verification, drift & evidence**: Test Coverage Drift Control, PatchWarden Evidence Pack, Quality Gates (Enforcement Layer), Verify Review Ship, Intent Reconciliation
- **Requirements & intake**: EARS Requirements Syntax, the `assess` Idea Assessment Pipeline, Spec-Kit BDD, Charter
- **External trackers & round-trip**: Linear Weave, Multi-Repo Branch Sync, ContextForge MCP
- **Design & docs**: Spec Kit Figma, Figma Starter, Blueprint Index — Living Architecture Map, LLM Wiki, Dotdog
- **Knowledge & orchestration**: OKF Knowledge Bundle Generator, Orchestration Task Context Management, Spec Kit Memory
-
-The catalog also showed strong maintenance activity: **DocGuard — CDD Enforcement** advanced through several releases (to v0.33.0), **Verify Review Ship** and **Quality Gates (Enforcement Layer)** iterated rapidly, and **Architecture Guard**, **Golden Demo**, **Coding Standards Drift Control**, **Ripple**, and the **Ralph Loop** all shipped updates. The preset side was the month's busiest: a large **governance-preset** family expanded and iterated — the **Autonomous Run Governance** and **Parallel Autonomous Run Governance** presets, a full **Intake** governance suite (Authoring, Review, Sequencing), **Test-First Governance**, and coordinated version bumps across the A11Y, Agent-Parity, Cross-Platform, iSAQB-Architecture, Architecture, and Security governance presets. [\[github.com\]](https://github.github.io/spec-kit/community/extensions.html)
-
-### Documentation & Docs Site
-
-July's documentation work paired the new features with a landing-page refresh. The **spec-of-specs feature-breakdown** approach was documented for handling complex features (#3648), the **`py` (Python) script type** was documented in the installation guide and init option table (#3284, #3625, #3640), and the **`__SPECKIT_COMMAND`** token for portable cross-command references was documented (#3503). The landing page was reframed to weave the **harness/SDLC framing** and modernize the install and positioning story (#3565, #3567), ecosystem stats were refreshed (#3561), and **`extensions.yml` hook configuration** was documented (#3563). Upgrade guidance clarified that project-file upgrades flow through `integration upgrade` / `extension update` (#3326) and that Claude Code files live in `.claude/skills` (#3708). [\[github.com\]](https://github.com/github/spec-kit/releases)
-
-## Community & Content
-
-### Press and Industry Coverage
-
-July's coverage shifted from "what is SDD" explainers toward tool comparisons, companion tooling, and pointed "who verifies the spec?" critiques. No first-party Microsoft or GitHub post appeared in July; the nearest remained June's Microsoft Developer Blog piece.
-
-**heise online** (Wolf Hosbach, July 21) was the month's most prominent mainstream-press coverage, publishing *"From Idea to Spec: The New Feature in Spec Kit 0.13"* in both English and German — news coverage of the `assess` Idea Assessment Pipeline, the Azure DevOps CLI support, and the 0.13 validation fixes. Mainstream European tech press now tracks Spec Kit's minor releases as tooling news. [\[heise.de\]](https://www.heise.de/en/news/From-Idea-to-Spec-The-New-Feature-in-Spec-Kit-0-13-11371866.html)
-
-**Towards AI** (Rost Glukhov, July 12) compared **GitHub Spec Kit vs Kiro vs Claude Code** on SDD workflow rather than model capability, part of a July-long current of "which SDD tool?" comparisons that increasingly pit Spec Kit specifically against Kiro. [\[pub.towardsai.net\]](https://pub.towardsai.net/github-spec-kit-vs-kiro-vs-claude-code-sdd-workflows-a9e7fab3e545)
-
-**ranjankumar.in** (Ranjan Kumar, July 13) argued that four SDD frameworks — BMAD, Spec Kit, Kiro, and Superpowers — converge on the same structural "invariants," engaging Spec Kit's actual internals (`workflows.md`, run-state `state.json`) rather than treating it as a black box. [\[ranjankumar.in\]](https://ranjankumar.in/spec-driven-development-invariants-not-frameworks)
-
-Release-trackers continued their factual coverage of the 0.13–0.15 run, and **Level Up Coding** (JingJing "Chris" Bao) published a three-part practitioner series on Spec Kit's presets, extensions, and pipeline/workflow features as the path beyond linear slash-commands. [\[levelup.gitconnected.com\]](https://levelup.gitconnected.com/from-linear-commands-to-automated-pipelines-how-spec-kit-orchestrates-nonlinear-ai-development-55ca03c5617b)
-
-### The Companion-Tooling Ecosystem
-
-July's most telling signal was not an article but a pattern: independent developers responded to Spec Kit's most-cited critiques by **building tools on top of it**. The recurring complaint — documentation proliferation and "who verifies the generated spec?" — turned into code.
-
- **artgraph** (mori-shin, July 20) — a deterministic, hash-based spec↔code drift-detection CLI with an `artgraph integrate speckit` hook, built specifically to give Spec Kit's LLM-prompt-based verification a deterministic backstop. [\[zenn.dev\]](https://zenn.dev/mrmtsntr/articles/artgraph-spec-code-drift)
- **SpecJudge** (Joaquín Ruiz, July 21) — a companion CLI that reads Spec Kit's constitution/spec/tasks artifacts to recommend a *right-sized* model for the project. [\[dev.to\]](https://dev.to/jokiruiz/specjudge-which-ai-model-is-right-sized-for-your-project-ask-your-specs-2edp)
- **GAUNTLEX** (Sanjoy Ghosh, July 16) — named Spec Kit a leading SDD tool while arguing SDD leaves a security-testing gap, and shipped a tool to fill it. [\[hashnode.dev\]](https://sanjoy1234.hashnode.dev/the-testing-gap-nobody-s-talking-about-in-spec-driven-development)
- **Custom skills** — [`speckit-next`](https://qiita.com/htcd/items/ec76f2b7194be3297b93) (htcd, July 31), a skill that recommends the next command because the names and order are hard to remember, and [`prefill`](https://velog.io/@k3nta/ai-adoption-journey-1-tools) (k3nta, July 1), a skill that patches `clarify`'s blind spots.
-
-Together these are the clearest evidence yet that Spec Kit has become a *platform* — its artifacts are stable enough, and its gaps well-enough understood, that a third-party tooling layer is forming around it. [\[zenn.dev\]](https://zenn.dev/mrmtsntr/articles/artgraph-spec-code-drift)
-
-### Developer Articles and Blog Posts
-
-July's articles skewed heavily multilingual — strong hands-on series in Japanese, Chinese, and Korean — with a clear thread of honest, use-it-in-anger critique.
-
-Notable articles:
-
- **ta_kawano** (note.com, July 28–31) published a consolidated four-part **Kiro vs Spec Kit** head-to-head, completing a 108-task / 301-test build with Spec Kit where Kiro ran out of credit, praising measurable Success Criteria and auto-listed edge cases while flagging ~15,000 lines of generated documentation — and reframing Spec Kit as a requirements-elicitation tool. [\[note.com\]](https://note.com/takawano/n/ncb552ee37331)
- **magebyte / 码哥字节** (SegmentFault, July 26) built a Go REST API through the five-step workflow, covered the three spec-persistence models and the extension/preset system, and claimed ~80% less AI "hallucination" rework. [\[segmentfault.com\]](https://segmentfault.com/a/1190000048082146)
- **Nil Seri** (Medium, July 16) published a brownfield guide adding Spec Kit to an existing Spring Boot / Maven project with Jira and Confluence integration — "from Jira ticket to verified code." [\[medium.com\]](https://medium.com/@senoritadeveloper/using-spec-kit-in-an-existing-spring-boot-maven-project-from-jira-ticket-to-verified-code-4e6da99b5d19)
- **kitroc7134** (Qiita, July 4) tested `/speckit.converge` with deliberate fault-injection on a FastAPI Todo API — detect drift → append convergence tasks → re-implement — validating June's convergence loop in the field. [\[qiita.com\]](https://qiita.com/kitroc7134/items/117d4839f259bc403626)
- **yutakaosada** (Zenn, July 25) — a Microsoft-MVP .NETラボ talk that uses Spec Kit but candidly flags AI-credit consumption, over-production of docs, and single-source-of-truth collapse, comparing it with Copilot Plan mode. [\[zenn.dev\]](https://zenn.dev/yutakaosada/articles/70e01981647159)
-
-Additional coverage appeared on TechWealthBuzz, Hashnode, TabNews-adjacent outlets, CSDN and 腾讯云 (Chinese), Naver/velog/Tistory (Korean), and Qiita/note (Japanese) — including several "is it too heavy?" and documentation-proliferation critiques, and a [Korean instructor's piece](https://blog.naver.com/gaussian88/224363268926) citing Spec Kit's star growth from ~90k in May to ~120k in July. [\[note.com\]](https://note.com/takawano/n/ncb552ee37331)
-
-### Community Growth by the Numbers
-
-| Metric | Start of July | End of July | Change |
-| --- | --- | --- | --- |
-| GitHub stars | 117,423 | 124,655 | +7,232 (+6%) |
-| Forks | 10,382 | 11,125 | +743 |
-| Contributors | 245 | ~258 | +~13 |
-| Releases (total) | 177 | 205 | +28 (v0.12.3–v0.15.1) |
-| Community extensions | 125 | 144 | +19 |
-| Community presets | 23 | 29 | +6 |
-| Community workflows | 1 | 2 | +1 |
-| Community bundles | 1 | 1 | steady |
-| Agent integrations | 34 | 37 | +3 (net) |
-| Discussions (open) | 457 | ~467 | +~10 |
-
-## SDD Ecosystem & Industry Trends
-
-### From Tool to Platform
-
-July's clearest ecosystem signal was structural: the conversation moved from "how do I use Spec Kit?" to "what do I build *around* it?" The companion tools — artgraph for deterministic drift, SpecJudge for model sizing, GAUNTLEX for the testing gap, and a growing set of custom agent skills — treat Spec Kit's artifacts (constitution, spec, tasks, run-state) as a stable substrate to build against. The public community catalog reinforces the point: the loudest theme across the 144 cataloged extensions is verification and quality (review, validate, drift, sync, verify, audit), and core SDD verbs are increasingly *re-expressed* by extensions rather than merely overridden — evidence of demand for composable, overridable core commands. [\[github.com\]](https://github.github.io/spec-kit/community/extensions.html)
-
-### Competitive Landscape
-
-The "which SDD tool?" comparison remained the dominant content genre, but July's framing narrowed: where June's surveys ran a seven-tool field, July's most substantive pieces increasingly went head-to-head **Spec Kit vs Kiro** (ta_kawano, [faruryo](https://qiita.com/faruryo/items/87a14728299e89f80ff4), Towards AI). The recurring verdict held — Spec Kit is the heaviest and most flexible option, strong on measurable Success Criteria, requirements elicitation, and greenfield decomposition, while its documentation proliferation and cognitive load are the consistent trade-off. The convergence-invariants analyses (ranjankumar.in) went further, arguing the frameworks are converging on the same structural primitives, which shifts the competitive question from "which tool" to "which ecosystem and governance model." On that axis, Spec Kit's widening catalog, agent-neutrality, and now a forming companion-tooling layer are its differentiators. [\[note.com\]](https://note.com/takawano/n/ncb552ee37331)
-
-## Roadmap
-
-Areas under discussion or in progress for future development:
-
- **Upstream of the spec** — the `assess` Idea Assessment Pipeline extends SDD before the spec exists. Expect the capture→evidence→refine→design→decision flow to deepen, and the boundary between idea assessment and `/speckit.specify` to be a key area to refine as the pipeline sees real use. [\[heise.de\]](https://www.heise.de/en/news/From-Idea-to-Spec-The-New-Feature-in-Spec-Kit-0-13-11371866.html)
- **The Python migration** — the `py` script type and the port of the core scripts, git extension, and agent-context updater establish Python as the path out of the bash/PowerShell parity tax. Completing the port and making `py` a well-trodden default (rather than sh/ps) is the payoff: an entire class of Windows-parity bugs disappears. [\[github.com\]](https://github.com/github/spec-kit/releases)
- **Agent-native runtime events** — the first-class events layer lets integrations wire Spec Kit into each agent's own runtime through canonical event names and per-agent adapters. The layer is **actively evolving** — early signals point to opencode context injection and JSON-envelope agent hooks. Expect more agents to gain event adapters and extension authors to lean on the declarative `events:` surface as the integration layer shifts from lowest-common-denominator overlay to genuinely native behavior. [\[github.com\]](https://github.com/github/spec-kit/releases)
- **Copilot skills as the default** — July shipped a warning ahead of the skills-default rollout, and the signals now point to the **default flip being in progress** — moving `specify init --integration copilot` to the skills-based layout and making the default init integration overridable via an environment variable, with the markdown-command layout becoming the legacy path. [\[github.com\]](https://github.com/github/spec-kit/releases)
- **A Copilot-native surface** — the first-party [`github/spec-kit-copilot`](https://github.com/github/spec-kit-copilot) repo (a listed community friend) wraps the `specify` CLI as a **Copilot skills plugin** (nine skills across setup, init, extensions, presets, bundles, workflows, and self-upgrade) for the Copilot CLI and App, aligned to CLI v0.15.0. The emerging direction is a **visual, Copilot-driven surface** — early work explores canvas dashboards for the Spec-Driven Development flow, a Bug Fix Pipeline, and `assess` — turning the CLI's flows into an interactive layer. [\[github.com\]](https://github.com/github/spec-kit-copilot)
- **The companion-tooling layer** — artgraph, SpecJudge, GAUNTLEX, and custom skills signal a third-party ecosystem forming on Spec Kit artifacts. The open question is whether the project absorbs these patterns (as it did drift → `converge`) or leaves them to the ecosystem; the verification/drift demand in the extension catalog suggests continued upstream pull. [\[github.com\]](https://github.com/github/spec-kit/releases)
- **Security and robustness as a standing discipline** — July's hardening wave (bounded reads, strict redirects, TOCTOU elimination, fail-loudly validation) shifted from feature to routine, and the signals point to it **continuing as an ongoing campaign** — a stdin read cap to close a DoS path and a broader atomicity push (atomic temp-file writes, subprocess timeouts, structured logging, and narrowed exception handlers). Sustaining the no-unbounded-read invariant as the surface (bundles, workflows, catalogs, events) grows is the ongoing work. [\[github.com\]](https://github.com/github/spec-kit/releases)
- **Experience simplification** — documentation proliferation and cognitive load remain the single most-cited concern across July's balanced reviews (ta_kawano, yutakaosada, and multiple Japanese/Korean pieces). The `assess` upstream gate, the lean/TinySpec presets, `/speckit.converge`, and the forming companion-tooling layer all provide answers; surfacing them to new users is the persistent opportunity. [\[note.com\]](https://note.com/takawano/n/ncb552ee37331)
@@ -1,14 +1,14 @@
 # Spec Kit - June 2026 Newsletter

-This edition covers Spec Kit activity in June 2026 — a month of maturation and mainstream validation. Twenty-five releases shipped (v0.9.0 through v0.12.2), spanning four minor bumps and delivering two headline capabilities: the **`/speckit.converge` command**, which closes the loop between a spec and the code that implements it, and the new **`specify bundle` subsystem**, a role-based distribution layer that composes extensions, presets, workflows, and steps into a single installable unit. The workflow engine became programmable, the git extension went opt-in as the first real breaking change, and the ecosystem crossed **120+ community extensions**. Externally, June brought broad validation — Microsoft's own Developer Blog published a first-party spec-driven development post, an enterprise reported 2–4× velocity gains, and coverage spanned dozens of languages. A summary is in the table below, followed by details.
+This edition covers Spec Kit activity in June 2026 — a month of maturation and mainstream validation. Twenty-five releases shipped (v0.9.0 through v0.12.2), spanning four minor bumps and delivering two headline capabilities: the **`/speckit.converge` command**, which closes the loop between a spec and the code that implements it, and the new **`specify bundle` subsystem**, a role-based distribution layer that composes extensions, presets, workflows, and steps into a single installable unit. The workflow engine became programmable, the git extension went opt-in as the first real breaking change, and the ecosystem crossed **120+ community extensions**. Externally, June was the highest-volume press month on record — Microsoft's own Developer Blog published a first-party spec-driven development post, an enterprise reported 2–4× velocity gains, and 75 substantive articles appeared across 25+ languages. A summary is in the table below, followed by details.

 | **Spec Kit Core (Jun 2026)** | **Community & Content** | **SDD Ecosystem & Next** |
 | --- | --- | --- |
-| Twenty-five releases shipped (v0.9.0–v0.12.2) with key features: the `/speckit.converge` convergence loop, the `specify bundle` role-based packaging subsystem, a programmable workflow engine (step catalog, JSON output, `from_json`), the git extension becoming opt-in (`--no-git` removed), and six new agents (Cline, rovodev, Zed, Firebender, ZCode, omp). The repo grew from ~107k to **~116,500 stars**. [\[github.com\]](https://github.com/github/spec-kit/releases) | The community extension catalog grew from 105 to **124 entries**; presets reached **23**. Microsoft's Developer Blog published a first-party SDD post naming Spec Kit as the operationalizing toolkit. Press coverage spanned dozens of languages. **245 contributors** now listed. | An enterprise (SNCF Connect & Tech) reported **2–4× velocity** from SDD. Analysts and comparisons increasingly name Spec Kit "the category anchor" and agent-neutral default. Competitors differentiate on brownfield and drift; balanced reviews continue to flag review-overload and ceremony for small tasks. |
+| Twenty-five releases shipped (v0.9.0–v0.12.2) with key features: the `/speckit.converge` convergence loop, the `specify bundle` role-based packaging subsystem, a programmable workflow engine (step catalog, JSON output, `from_json`), the git extension becoming opt-in (`--no-git` removed), and six new agents (Cline, rovodev, Zed, Firebender, ZCode, omp). The repo grew from ~107k to **~116,500 stars**. [\[github.com\]](https://github.com/github/spec-kit/releases) | The community extension catalog grew from 105 to **124 entries**; presets reached **23**. Microsoft's Developer Blog published a first-party SDD post naming Spec Kit as the operationalizing toolkit. June was the highest-volume press month yet — **75 substantive articles** across 25+ languages. **245 contributors** now listed. | An enterprise (SNCF Connect & Tech) reported **2–4× velocity** from SDD. Analysts and comparisons increasingly name Spec Kit "the category anchor" and agent-neutral default. Competitors differentiate on brownfield and drift; balanced reviews continue to flag review-overload and ceremony for small tasks. |

 ***

-> **Spec-Driven Development, Institutionalized.** If May was defined by milestone 100s, June was defined by validation from outside the project. Microsoft's own Developer Blog published a first-party post presenting spec-driven development and positioning Spec Kit as the toolkit that operationalizes it. An enterprise — SNCF Connect & Tech — went on the record with **2–4× velocity gains** from adopting SDD. Coverage appeared in dozens of languages, and the recurring verdict across independent comparisons was that Spec Kit is "the category anchor" and the agent-neutral default. Meanwhile the core matured from v0.9 to v0.12: the workflow engine became genuinely programmable, the first real breaking change shipped, and the new convergence loop and bundle subsystem gave the project answers to its two most-cited gaps — drift and distribution. None of this happens without the community — the contributors, extension and preset authors, bundle builders, and practitioners writing in a dozen languages. Thank you.
+> **Spec-Driven Development, Institutionalized.** If May was defined by milestone 100s, June was defined by validation from outside the project. Microsoft's own Developer Blog published a first-party post presenting spec-driven development and positioning Spec Kit as the toolkit that operationalizes it. An enterprise — SNCF Connect & Tech — went on the record with **2–4× velocity gains** from adopting SDD. A record **75 substantive articles** appeared in more than 25 languages, and the recurring verdict across independent comparisons was that Spec Kit is "the category anchor" and the agent-neutral default. Meanwhile the core matured from v0.9 to v0.12: the workflow engine became genuinely programmable, the first real breaking change shipped, and the new convergence loop and bundle subsystem gave the project answers to its two most-cited gaps — drift and distribution. None of this happens without the community — the contributors, extension and preset authors, bundle builders, and practitioners writing in a dozen languages. Thank you.

 ## Spec Kit Project Updates

@@ -84,7 +84,7 @@ On **June 10**, the **Microsoft Developer Blog** published *"Spec-Driven Develop

 ### Press and Industry Coverage

-June's press coverage spanned dozens of languages and platforms.
+June was the **highest-volume coverage month on record — 75 substantive articles** across more than 25 languages.

 **Xebia / XPRT Magazine #21** (Hidde de Smet & Emanuele Bartolesi, June 17) published a 32-minute full six-command walkthrough covering both greenfield and brownfield, honest about markdown-review overhead and where spec quality becomes the bottleneck. [\[xebia.com\]](https://xebia.com/blog/building-software-with-spec-kit/)

@@ -102,7 +102,7 @@ June's press coverage spanned dozens of languages and platforms.

 ### Developer Articles and Blog Posts

-June's coverage skewed heavily multilingual, with deep hands-on series in Chinese, Japanese, and Korean, and a strong current of "which tool should I choose?" comparisons.
+June's 75 articles skewed heavily multilingual, with deep hands-on series in Chinese, Japanese, and Korean, and a strong current of "which tool should I choose?" comparisons.

 Notable English-language articles:

@@ -137,7 +137,7 @@ Coverage also appeared on TabNews (Portuguese), Habr and CSDN, note.com, Substac

 ### The Category Consolidates

-Across June's broad article coverage, a consistent framing emerged: spec-driven development is now an established category, and Spec Kit is its reference implementation. SSOJet called it "the category anchor," Design News and multiple comparison pieces called it the agent-neutral default, and ToolTwist's CxO guide named it the "safe default for scaling teams." The Microsoft Developer Blog post and the SNCF enterprise interview extended that framing beyond the developer press into institutional and enterprise contexts. [\[ssojet.com\]](https://ssojet.com/blog/best-spec-driven-development-tools)
+Across June's record article volume, a consistent framing emerged: spec-driven development is now an established category, and Spec Kit is its reference implementation. SSOJet called it "the category anchor," Design News and multiple comparison pieces called it the agent-neutral default, and ToolTwist's CxO guide named it the "safe default for scaling teams." The Microsoft Developer Blog post and the SNCF enterprise interview extended that framing beyond the developer press into institutional and enterprise contexts. [\[ssojet.com\]](https://ssojet.com/blog/best-spec-driven-development-tools)

 ### Competitive Landscape

@@ -4,7 +4,7 @@ This edition covers Spec Kit activity in May 2026 — a month defined by three m

 | **Spec Kit Core (May 2026)** | **Community & Content** | **SDD Ecosystem & Next** |
 | --- | --- | --- |
-| Fourteen releases shipped with key features: multi-install for concurrent agent integrations, constitution governance in implement, authentication provider registry, Hermes and Lingma agents, and a `__init__.py` decomposition series. The repo grew from ~92k to **106,951 stars**, crossing **100K** on May 21. [\[github.com\]](https://github.com/github/spec-kit/releases) | The community extension catalog crossed **100 entries** (now 105). Open Source Friday livestream drove a press wave: Visual Studio Magazine, DevOps.com, MarkTechPost, HackerNoon, and many more across multiple languages. **217 contributors** now listed. | MarkTechPost called Spec Kit "the most community-adopted open-source option" for SDD. The Futurum Group's Mitch Ashley framed specs as "the unit of governance across agents and contributors." Truong Phung published a 61-min production playbook referencing Spec Kit. Competitors grew but differentiate on orchestration; Spec Kit leads in portability and community. |
+| Fourteen releases shipped with key features: multi-install for concurrent agent integrations, constitution governance in implement, authentication provider registry, Hermes and Lingma agents, and a `__init__.py` decomposition series. The repo grew from ~92k to **106,951 stars**, crossing **100K** on May 21. [\[github.com\]](https://github.com/github/spec-kit/releases) | The community extension catalog crossed **100 entries** (now 105). Open Source Friday livestream drove a press wave: Visual Studio Magazine, DevOps.com, MarkTechPost, HackerNoon, and 25+ more articles — now tracked across multiple languages following an expanded discovery methodology. **217 contributors** now listed. | MarkTechPost called Spec Kit "the most community-adopted open-source option" for SDD. The Futurum Group's Mitch Ashley framed specs as "the unit of governance across agents and contributors." Truong Phung published a 61-min production playbook referencing Spec Kit. Competitors grew but differentiate on orchestration; Spec Kit leads in portability and community. |

 ***

@@ -76,7 +76,7 @@ May produced the broadest press coverage to date, with publications from the mai

 ### Developer Articles and Blog Posts

-May produced a wave of independent coverage across many languages.
+May produced a wave of independent coverage — well beyond any previous month. Starting this month, article discovery was expanded beyond English-centric search engines to include language-appropriate engines for 25+ languages, so the broader coverage partly reflects wider discovery rather than a sudden spike.

 Notable non-English coverage:

@@ -1,19 +1,19 @@
 {
  "schema_version": "1.0",
-  "updated_at": "2026-07-28T00:00:00Z",
+  "updated_at": "2026-07-23T00:00:00Z",

  "catalog_url": "https://raw.githubusercontent.com/github/spec-kit/main/presets/catalog.community.json",
  "presets": {
    "a11y-governance": {
      "name": "A11Y Governance",
      "id": "a11y-governance",
-      "version": "0.4.2",
-      "description": "Adds accessibility (WCAG 2.2 AA), accessible text and JSON status parity, bilingual DE/EN delivery, CEFR-B2 readability, inclusive-content governance, didactic inline-code-comment review, and audit-ready Spec-Kit run evidence to Spec Kit.",
+      "version": "0.4.1",
+      "description": "Adds WCAG 2.2 AA governance, accessible text/JSON status parity, bilingual DE/EN delivery, CEFR-B2 readability, inclusive content, didactic-comment review, and audit-ready evidence.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-a11y-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-a11y-governance/archive/refs/tags/v0.4.2.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-a11y-governance/archive/refs/tags/v0.4.1.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-a11y-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-a11y-governance/blob/v0.4.2/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-a11y-governance/blob/v0.4.1/README.md",
      "license": "MIT",
      "requires": {
        "speckit_version": ">=0.8.0"
@@ -34,18 +34,18 @@
        "didactic-comments"
      ],
      "created_at": "2026-04-27T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-23T00:00:00Z"
    },
    "agent-parity-governance": {
      "name": "Agent Parity Governance",
      "id": "agent-parity-governance",
-      "version": "0.4.1",
-      "description": "Adds shared-guidance and generated-command parity, repository-fleet completion evidence, secret-free runner/status metadata, audit-ready Spec-Kit run evidence, and agent-neutral model-routing guidance across declared AI-agent surfaces.",
+      "version": "0.4.0",
+      "description": "Adds shared-guidance and generated-command parity, fleet-completion evidence, secret-free runner/status metadata, audit-ready evidence, and agent-neutral model routing.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance/archive/refs/tags/v0.4.1.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance/archive/refs/tags/v0.4.0.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance/blob/v0.4.1/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-agent-parity-governance/blob/v0.4.0/README.md",
      "license": "MIT",
      "requires": {
        "speckit_version": ">=0.8.0"
@@ -64,7 +64,7 @@
        "multi-agent"
      ],
      "created_at": "2026-04-27T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-23T00:00:00Z"
    },
    "aide-in-place": {
      "name": "AIDE In-Place Migration",
@@ -135,13 +135,13 @@
    "autonomous-run-governance": {
      "name": "Autonomous Run Governance",
      "id": "autonomous-run-governance",
-      "version": "0.3.3",
-      "description": "Adds permission-bounded autonomous delivery, an optional intake-review gate, and preservation of the project's learner and accessibility contract.",
+      "version": "0.3.2",
+      "description": "Adds permission-bounded, evidence-first governance for complete autonomous Spec Kit delivery, including validated status, stop, explicit resume, exact-head proof, post-merge closeout, retrospective learning, and an optional policy-driven intake-review gate before feature creation.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/archive/refs/tags/v0.3.3.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/archive/refs/tags/v0.3.2.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/blob/v0.3.3/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-autonomous-run-governance/blob/v0.3.2/README.md",
      "license": "MIT",
      "requires": {
        "speckit_version": ">=0.8.3"
@@ -156,10 +156,11 @@
        "governance",
        "evidence",
        "permissions",
-        "accessibility"
+        "resume",
+        "intake-review"
      ],
      "created_at": "2026-07-13T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-21T00:00:00Z"
    },
    "canon-core": {
      "name": "Canon Core",
@@ -367,42 +368,42 @@
    "intake-authoring-governance": {
      "name": "Intake Authoring Governance",
      "id": "intake-authoring-governance",
-      "version": "0.3.0",
-      "description": "Governs traceable intake CRUD and language-aware requirements collections with atomic migrations, rollback evidence, and safe series authoring.",
+      "version": "0.1.1",
+      "description": "Creates traceable Spec Kit intakes from ordered text sources and now truthfully adopts legacy intakes without inventing predecessor receipts.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance/archive/refs/tags/v0.3.0.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance/archive/refs/tags/v0.1.1.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance/blob/v0.3.0/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-intake-authoring-governance/blob/v0.1.1/README.md",
      "license": "MIT",
      "requires": {
        "speckit_version": ">=0.8.3"
      },
      "provides": {
-        "templates": 12,
-        "commands": 5,
-        "scripts": 7
+        "templates": 7,
+        "commands": 2,
+        "scripts": 2
      },
      "tags": [
        "intake",
        "authoring",
        "governance",
-        "requirements",
-        "migration"
+        "traceability",
+        "legacy-adoption"
      ],
      "created_at": "2026-07-22T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-23T00:00:00Z"
    },
    "intake-review-governance": {
      "name": "Intake Review Governance",
      "id": "intake-review-governance",
-      "version": "0.2.0",
-      "description": "Reviews single, series, campaign, and language-aware requirements collections before Spec Kit execution.",
+      "version": "0.1.0",
+      "description": "Adds hash-bound review, repair, and status gates for single, series, and campaign intake files before interactive, autonomous, or parallel Spec Kit execution.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-intake-review-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-intake-review-governance/archive/refs/tags/v0.2.0.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-intake-review-governance/archive/refs/tags/v0.1.0.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-intake-review-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-intake-review-governance/blob/v0.2.0/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-intake-review-governance/blob/v0.1.0/README.md",
      "license": "MIT",
      "requires": {
        "speckit_version": ">=0.8.3"
@@ -410,46 +411,17 @@
      "provides": {
        "templates": 8,
        "commands": 3,
-        "scripts": 4
+        "scripts": 2
      },
      "tags": [
        "intake",
        "review",
        "governance",
-        "requirements",
-        "quality-gate"
+        "quality-gate",
+        "autonomous"
      ],
      "created_at": "2026-07-21T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
-    },
-    "intake-sequencing-governance": {
-      "name": "Intake Sequencing Governance",
-      "id": "intake-sequencing-governance",
-      "version": "0.2.2",
-      "description": "Manages language-aware intake-series order, typed dependencies, lifecycle, and authority-neutral next-candidate selection.",
-      "author": "Thorsten Hindermann",
-      "repository": "https://github.com/hindermath/spec-kit-preset-intake-sequencing-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-intake-sequencing-governance/archive/refs/tags/v0.2.2.zip",
-      "homepage": "https://github.com/hindermath/spec-kit-preset-intake-sequencing-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-intake-sequencing-governance/blob/v0.2.2/README.md",
-      "license": "MIT",
-      "requires": {
-        "speckit_version": ">=0.8.3"
-      },
-      "provides": {
-        "templates": 11,
-        "commands": 6,
-        "scripts": 8
-      },
-      "tags": [
-        "intake",
-        "sequencing",
-        "governance",
-        "dag",
-        "lifecycle"
-      ],
-      "created_at": "2026-07-27T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-21T00:00:00Z"
    },
    "isaqb-architecture-governance": {
      "name": "iSAQB Architecture Governance",
@@ -571,16 +543,16 @@
    "parallel-autonomous-run-governance": {
      "name": "Parallel Autonomous Run Governance",
      "id": "parallel-autonomous-run-governance",
-      "version": "0.2.4",
-      "description": "Coordinates permission-bounded autonomous campaigns while preserving the project's learner and accessibility contract across workers and consolidation.",
+      "version": "0.2.3",
+      "description": "Coordinates isolated autonomous Spec Kit campaigns with bounded concurrency, mixed agents, resumable consolidation, governed post-merge closeout, schema 1.2, and an optional current intake-review gate before worker scheduling.",
      "author": "Thorsten Hindermann",
      "repository": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance",
-      "download_url": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance/archive/refs/tags/v0.2.4.zip",
+      "download_url": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance/archive/refs/tags/v0.2.3.zip",
      "homepage": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance",
-      "documentation": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance/blob/v0.2.4/README.md",
+      "documentation": "https://github.com/hindermath/spec-kit-preset-parallel-autonomous-run-governance/blob/v0.2.3/README.md",
      "license": "MIT",
      "requires": {
-"speckit_version": ">=0.8.3"
+        "speckit_version": ">=0.8.3"
      },
      "provides": {
        "templates": 9,
@@ -591,11 +563,12 @@
        "parallel",
        "autonomous",
        "governance",
-        "accessibility",
-        "orchestration"
+        "orchestration",
+        "resume",
+        "intake-review"
      ],
      "created_at": "2026-07-22T00:00:00Z",
-      "updated_at": "2026-07-28T00:00:00Z"
+      "updated_at": "2026-07-22T00:00:00Z"
    },
    "pirate": {
      "name": "Pirate Speak (Full)",
@@ -25,29 +25,6 @@
        "workflow",
        "core"
      ]
-    },
-    "constitution-sync": {
-      "name": "Constitution Template Sync",
-      "id": "constitution-sync",
-      "version": "1.0.0",
-      "description": "Opt-in: restores /constitution propagation of amended guidance into plan/spec/tasks templates and installed command files, for teams that treat materialized templates as reviewed artifacts.",
-      "author": "github",
-      "repository": "https://github.com/github/spec-kit",
-      "license": "MIT",
-      "bundled": true,
-      "requires": {
-        "speckit_version": ">=0.14.4"
-      },
-      "provides": {
-        "commands": 1,
-        "templates": 0
-      },
-      "tags": [
-        "constitution",
-        "governance",
-        "templates",
-        "compatibility"
-      ]
    }
  }
 }
@@ -1,126 +0,0 @@
-# Constitution Template Sync
-
-An **opt-in** preset that restores `/constitution`'s ability to propagate amended guidance into your
-project's own templates and command files. After you update the constitution, it aligns
-`plan-template.md`, `spec-template.md`, `tasks-template.md`, project-local command files, and
-guidance docs so they reflect the current principles.
-
-This propagation used to be built into `/constitution`; it was dropped when the command moved to the
-preset model. Installing this preset opts you back into it: you get the guidance materialized into
-reviewed, committed artifacts instead of relying on runtime resolution alone.
-
-> **What you're opting into.** Propagation was removed deliberately — it duplicates the constitution
-> as the source of truth and can fight the composition stack (materialized edits get shadowed or
-> clobbered on the next recompose). This preset knowingly **reintroduces** that behavior, and those
-> tradeoffs, for teams that want it. Read the [caveats](#caveats-you-take-on) before installing.
-
-For most projects the default composable stack is the **recommended** approach, and at organization
-scale it is usually the stronger governance model. Runtime resolution keeps the live constitution as
-the single source of truth (nothing to re-sync, so nothing drifts), and the stack composes the
-**entire** Spec Kit ecosystem — not just the SDD commands, but every command, template, script and
-extension — with explicit priority levels, strategies, and independent versioning. It is a
-capability, not automatic governance: a core team authors its own organizational presets and
-extensions, then owns, versions, and audits that policy in one place and rolls it across many
-repositories, instead of scattering frozen, per-repo copies no central team can see. This preset is
-a supported escape hatch for teams whose workflow depends on reviewing materialized artifacts
-directly — useful as a bridge, though for org-wide policy the better long-term path is usually a
-versioned preset a core team maintains.
-
-## What it does
-
-Ships a single `wrap`-strategy override of `speckit.constitution`. It composes on top of the
-current core command (via `{CORE_TEMPLATE}`), so it stays forward-compatible with core changes, and
-appends a propagation pass that, after the constitution is written:
-
- Aligns `plan/spec/tasks-template.md` in `.specify/templates/` with the updated principles.
- Updates **project-local** command files and guidance docs to correct stale references.
- Extends the Sync Impact Report in `.specify/memory/constitution.md` with the files it touched.
-
-## What it does not do
-
- It does **not** change behavior for anyone who does not install it — the default runtime
-  resolution model is untouched.
- It does **not** disable runtime resolution. `plan`, `tasks`, and `analyze` still read the live
-  constitution every run; this preset adds materialized copies on top — it does not replace the
-  source of truth.
- It does **not** edit versioned, package-owned files — templates or command files provided or
-  wrapped by another preset or extension. Those are recomposed from the resolution stack, so it
-  only ever writes into your project's own `.specify/templates/` scaffolds and command files that
-  are not managed by a preset/extension.
-
-## When to use it
-
-Install it **only** if your team treats the materialized templates and commands as
-**reviewed, committed artifacts** — for example, if `plan-template.md`'s Constitution Check is
-read in PRs as "here are our current gates" and is expected to track the constitution.
-
-If you rely on the default runtime-resolution model, you do **not** need this preset: the live
-constitution is already the single source of truth and there is nothing to sync.
-
-## Caveats you take on
-
-The preset resolution stack is how Spec Kit composes templates and commands going forward: they are
-**layered, package-owned artifacts recomposed on demand**, not frozen files you edit in place.
-Propagation is the opposite idea — it **materializes** guidance into files and freezes it. That
-tension is the main thing to understand before installing:
-
- **Materialized copies can drift.** Anything propagated is a snapshot; if you amend the
-  constitution and do not re-run `/constitution`, the copies fall out of sync. The default runtime
-  model has no drift because it reads the live constitution every run.
-
- **Edits to composed files do not survive reconciliation.** If the rest of your SDD flow is
-  preset/extension-managed, the commands it materializes (`speckit.plan`, `speckit.specify`,
-  `speckit.tasks`, `speckit.analyze`, `speckit.implement`, …) are recomputed from the stack. Any
-  guidance propagated into them is clobbered the next time the stack reconciles — on
-  `specify integration use <key>` / `switch`, `specify integration upgrade`, or any preset/extension
-  install or remove. The same applies to templates owned by another preset/extension. This is why
-  the preset restricts itself to project-local files; propagation is reliable **only** for
-  artifacts you own outright.
-
- **A pre-filled Constitution Check can bias `/plan`.** Materializing concrete gates into
-  `plan-template.md` replaces the runtime pointer, so the first `/plan` pass may anchor on the
-  frozen text. Keep the pointer unless you specifically want committed gates.
-
-**Bottom line:** this preset fits projects whose governed templates and commands are project-local
-artifacts they review, with the rest of the SDD flow on the plain bundled core. If your
-`plan`/`specify`/`tasks`/`analyze` commands or templates come from other presets or extensions,
-prefer the default runtime-resolution model.
-
-## Installation
-
-```bash
-# constitution-sync is a bundled preset — no download needed
-specify preset add constitution-sync
-```
-
-## Development
-
-```bash
-# Test from local directory
-specify preset add --dev ./presets/constitution-sync
-
-# Verify the wrapped command resolves
-specify preset resolve speckit.constitution
-
-# Remove when done
-specify preset remove constitution-sync
-```
-
-## Migrating back to the default
-
-To move back to runtime resolution, reset each materialized `## Constitution Check` section in
-`.specify/templates/plan-template.md` to the pointer:
-
-```text
-## Constitution Check
-
-*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
-
-[Gates determined based on constitution file]
-```
-
-Then remove this preset. See `docs/upgrade.md` for details.
-
-## License
-
-MIT
@@ -1,54 +0,0 @@
---
-description: Create or update the project constitution, then propagate the amended guidance into dependent templates and installed command files (opt-in template sync).
-strategy: wrap
-handoffs:
-  - label: Build Specification
-    agent: speckit.specify
-    prompt: Implement the feature specification based on the updated constitution. I want to build...
---
-
-{CORE_TEMPLATE}
-
-## Constitution Template Sync
-
-> **This section supersedes the "Scope Guard" above for template and command propagation.**
-> The core Scope Guard states that dependent templates and commands "are not modified here" —
-> that restriction is intentionally lifted by this preset. Propagating amended guidance into the
-> project's own dependent scaffolds and installed command files (as described below) **is in
-> scope** whenever this preset is installed. The Scope Guard's other constraints still apply:
-> do not implement features, generate application code, or touch artifacts unrelated to the
-> constitution/template workflow.
-
-After you have written the updated constitution above, perform a consistency propagation pass
-so the dependent artifacts reflect the amended principles:
-
-1. Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align
-   with the updated principles. Only materialize concrete gate text here if your team intends to
-   review it as committed content; otherwise leave the runtime pointer
-   `[Gates determined based on constitution file]` in place so `/plan` fills it from the live
-   constitution.
-2. Read `.specify/templates/spec-template.md` for scope/requirements alignment — update if the
-   constitution adds/removes mandatory sections or constraints.
-3. Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or
-   removed principle-driven task types (e.g., observability, versioning, testing discipline).
-4. Read each installed Spec Kit command file for your agent (including this one) — named
-   `speckit.*` or `speckit-*` (dot or hyphen depending on the agent), or laid out as
-   `speckit-<name>/SKILL.md` for skills-based integrations, e.g. in `.github/agents/`,
-   `.github/skills/`, `.claude/skills/`, or your agent's equivalent commands directory — to verify
-   no outdated references (CLAUDE-only or other agent-specific names) remain when generic guidance
-   is required. **Only hand-edit a command file if it is a project-local file not managed by a
-   preset or extension.** Command files that are composed from the resolution stack (anything
-   provided or wrapped by a preset/extension) must be regenerated through the stack — do **not**
-   edit them in place, because reconciliation (`specify integration use`, `specify integration
-   upgrade`, or any preset/extension install/remove) will clobber the edits.
-5. Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific
-   guidance files if present) and update references to principles that changed.
-
-Then extend the Sync Impact Report at the top of `.specify/memory/constitution.md` with:
-
- Templates requiring updates (✅ updated / ⚠ pending) with file paths.
-
-**Do not edit versioned preset- or extension-provided template or command files directly.** Those
-artifacts are owned by their packages and are recomposed on the package's next update or on stack
-reconciliation — hand edits are clobbered. Limit propagation to the project's own
-`.specify/templates/` scaffolds and to command files that are not managed by a preset or extension.
@@ -1,30 +0,0 @@
-schema_version: "1.0"
-
-preset:
-  id: "constitution-sync"
-  name: "Constitution Template Sync"
-  version: "1.0.0"
-  description: "Opt-in: restores /constitution propagation of amended guidance into plan/spec/tasks templates and installed command files, for teams that treat materialized templates as reviewed artifacts."
-  author: "github"
-  repository: "https://github.com/github/spec-kit"
-  license: "MIT"
-
-requires:
-  # Requires the runtime-resolution baseline (#3790, shipped in 0.14.4) where the
-  # core /constitution command no longer propagates. Installing this preset on an
-  # older core would double-apply propagation.
-  speckit_version: ">=0.14.4"
-
-provides:
-  templates:
-    - type: "command"
-      name: "speckit.constitution"
-      file: "commands/speckit.constitution.md"
-      description: "Wrap /constitution to also propagate guidance into dependent templates and command files"
-      strategy: "wrap"
-
-tags:
-  - "constitution"
-  - "governance"
-  - "templates"
-  - "compatibility"
@@ -1,6 +1,6 @@
 [project]
 name = "specify-cli"
-version = "0.16.1"
+version = "0.14.1"
 description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -49,7 +49,6 @@ packages = ["src/specify_cli"]
 "workflows/speckit" = "specify_cli/core_pack/workflows/speckit"
 # Bundled presets (installable via `specify preset add <name>` or `specify init --preset <name>`)
 "presets/lean" = "specify_cli/core_pack/presets/lean"
-"presets/constitution-sync" = "specify_cli/core_pack/presets/constitution-sync"
 # Community bundle catalog snapshot (used for offline discovery)
 "bundles/catalog.community.json" = "specify_cli/core_pack/bundles/catalog.community.json"

@@ -8,7 +8,6 @@ ALLOW_EXISTING=false
 SHORT_NAME=""
 BRANCH_NUMBER=""
 USE_TIMESTAMP=false
-NUMBER_EXPLICIT=false
 ARGS=()
 i=1
 while [ $i -le $# ]; do
@@ -49,9 +48,6 @@ while [ $i -le $# ]; do
                exit 1
            fi
            BRANCH_NUMBER="$next_arg"
-            if [ -n "$BRANCH_NUMBER" ]; then
-                NUMBER_EXPLICIT=true
-            fi
            ;;
        --timestamp)
            USE_TIMESTAMP=true
@@ -64,7 +60,7 @@ while [ $i -le $# ]; do
            echo "  --dry-run           Compute feature name and paths without creating directories or files"
            echo "  --allow-existing-branch  Reuse an existing feature directory if it already exists"
            echo "  --short-name <name> Provide a custom short name (2-4 words) for the feature"
-            echo "  --number N          Prefer a feature number (auto-corrected if its specs prefix exists)"
+            echo "  --number N          Specify branch number manually (overrides auto-detection)"
            echo "  --timestamp         Use timestamp prefix (YYYYMMDD-HHMMSS) instead of sequential numbering"
            echo "  --help, -h          Show this help message"
            echo ""
@@ -95,7 +91,6 @@ if [ -z "$FEATURE_DESCRIPTION" ]; then
 fi

 MAX_FEATURE_NUMBER=9223372036854775807
-MAX_BRANCH_LENGTH=244

 is_feature_number_in_range() {
    local value="$1"
@@ -133,40 +128,12 @@ get_highest_from_specs() {
    echo "$highest"
 }

-# Return success when a spec directory owns the given numeric prefix.
-spec_prefix_exists() {
-    local specs_dir="$1"
-    local feature_num="$2"
-
-    for spec_path in "$specs_dir/${feature_num}-"*; do
-        [ -d "$spec_path" ] && return 0
-    done
-    return 1
-}
-
 # Function to clean and format a branch name
 clean_branch_name() {
    local name="$1"
    echo "$name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//'
 }

-# Fit a feature prefix and suffix within GitHub's branch-name limit.
-fit_branch_name() {
-    local feature_num="$1"
-    local branch_suffix="$2"
-    local branch_name="${feature_num}-${branch_suffix}"
-
-    if [ ${#branch_name} -gt $MAX_BRANCH_LENGTH ]; then
-        local prefix_length=$(( ${#feature_num} + 1 ))
-        local max_suffix_length=$((MAX_BRANCH_LENGTH - prefix_length))
-        local truncated_suffix
-        truncated_suffix=$(printf '%s' "$branch_suffix" | cut -c "1-$max_suffix_length" | sed 's/-$//')
-        branch_name="${feature_num}-${truncated_suffix}"
-    fi
-
-    printf '%s' "$branch_name"
-}
-
 # Quote a value for POSIX shell reuse, byte-identical to Python's shlex.quote
 # so the persistence hints match the Python variant exactly (printf %q output
 # differs between bash versions and from shlex.quote for spaces/metachars).
@@ -286,41 +253,26 @@ else

    # Force base-10 interpretation to prevent octal conversion (e.g., 010 → 8 in octal, but should be 10 in decimal)
    FEATURE_NUM=$(printf "%03d" "$((10#$BRANCH_NUMBER))")
-
-    # Treat an explicit number as a preference when its prefix is already used
-    # by a feature directory. Auto-detected numbers are already conflict-free.
-    if [ "$NUMBER_EXPLICIT" = true ]; then
-        SPEC_CONFLICT=false
-        REQUESTED_BRANCH_NAME=$(fit_branch_name "$FEATURE_NUM" "$BRANCH_SUFFIX")
-        REQUESTED_DIR="$SPECS_DIR/$REQUESTED_BRANCH_NAME"
-        if [ "$ALLOW_EXISTING" != true ] || [ ! -d "$REQUESTED_DIR" ]; then
-            spec_prefix_exists "$SPECS_DIR" "$FEATURE_NUM" && SPEC_CONFLICT=true
-        fi
-
-        if [ "$SPEC_CONFLICT" = true ]; then
-            REQUESTED_NUM="$FEATURE_NUM"
-            HIGHEST=$(get_highest_from_specs "$SPECS_DIR")
-            BRANCH_NUMBER=$HIGHEST
-            while true; do
-                if [ "$BRANCH_NUMBER" -eq "$MAX_FEATURE_NUMBER" ]; then
-                    echo "Error: feature number must be between 0 and $MAX_FEATURE_NUMBER, got '9223372036854775808'" >&2
-                    exit 1
-                fi
-                BRANCH_NUMBER=$((BRANCH_NUMBER + 1))
-                FEATURE_NUM=$(printf "%03d" "$((10#$BRANCH_NUMBER))")
-                spec_prefix_exists "$SPECS_DIR" "$FEATURE_NUM" || break
-            done
-            >&2 echo "[specify] Warning: --number $REQUESTED_NUM conflicts with an existing spec directory; using $FEATURE_NUM instead"
-        fi
-    fi
-
+    BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
 fi

 # GitHub enforces a 244-byte limit on branch names
 # Validate and truncate if necessary
-ORIGINAL_BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
-BRANCH_NAME=$(fit_branch_name "$FEATURE_NUM" "$BRANCH_SUFFIX")
-if [ "$BRANCH_NAME" != "$ORIGINAL_BRANCH_NAME" ]; then
+MAX_BRANCH_LENGTH=244
+if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
+    # Calculate how much we need to trim from suffix
+    # Account for prefix length: timestamp (15) + hyphen (1) = 16, or sequential (3) + hyphen (1) = 4
+    PREFIX_LENGTH=$(( ${#FEATURE_NUM} + 1 ))
+    MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - PREFIX_LENGTH))
+
+    # Truncate suffix at word boundary if possible
+    TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
+    # Remove trailing hyphen if truncation created one
+    TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
+
+    ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
+    BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
+
    >&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
    >&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
    >&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"
@@ -55,17 +55,9 @@ function Resolve-SpecifyInitDir {
    }
    # Resolve-Path echoes back any trailing separator from the input; trim it so
    # the returned root matches the bash resolver, whose `cd && pwd` never yields
-    # one. TrimEnd (not [Path]::TrimEndingDirectorySeparator, which is .NET Core
-    # only) keeps this working on Windows PowerShell 5.1 / .NET Framework, as
-    # Get-FeaturePathsEnv already does below. Unlike a bare TrimEnd, the
-    # GetPathRoot check preserves a path that *is* its own root ('C:\' must not
-    # become 'C:', which every later API re-resolves against the current
-    # directory instead of the drive root). No-op on a path with no trailing
-    # separator.
-    $initRoot = $resolved.Path.TrimEnd('/', '\')
-    if ($initRoot.Length -lt [System.IO.Path]::GetPathRoot($resolved.Path).Length) {
-        $initRoot = $resolved.Path
-    }
+    # one. TrimEndingDirectorySeparator is a no-op on a bare root and on a path
+    # that already has no trailing separator.
+    $initRoot = [System.IO.Path]::TrimEndingDirectorySeparator($resolved.Path)
    if (-not (Test-Path -LiteralPath (Join-Path $initRoot '.specify') -PathType Container)) {
        [Console]::Error.WriteLine("ERROR: SPECIFY_INIT_DIR is not a Spec Kit project (no .specify/ directory): $initRoot")
        if ($ReturnNullOnError) { return $null }
@@ -14,7 +14,6 @@ param(
    [string[]]$FeatureDescription
 )
 $ErrorActionPreference = 'Stop'
-$maxBranchLength = 244

 # Show help if requested
 if ($Help) {
@@ -25,7 +24,7 @@ if ($Help) {
    Write-Host "  -DryRun             Compute feature name and paths without creating directories or files"
    Write-Host "  -AllowExistingBranch  Reuse an existing feature directory if it already exists"
    Write-Host "  -ShortName <name>   Provide a custom short name (2-4 words) for the feature"
-    Write-Host "  -Number N           Prefer a feature number (auto-corrected if its specs prefix exists)"
+    Write-Host "  -Number N           Specify branch number manually (overrides auto-detection)"
    Write-Host "  -Timestamp          Use timestamp prefix (YYYYMMDD-HHMMSS) instead of sequential numbering"
    Write-Host "  -Help               Show this help message"
    Write-Host ""
@@ -68,44 +67,11 @@ function Get-HighestNumberFromSpecs {
    return $highest
 }

-function Test-SpecPrefixInUse {
-    param(
-        [string]$SpecsDir,
-        [string]$FeatureNum
-    )
-
-    if (-not (Test-Path -LiteralPath $SpecsDir -PathType Container)) {
-        return $false
-    }
-
-    return $null -ne (Get-ChildItem -LiteralPath $SpecsDir -Directory -ErrorAction SilentlyContinue |
-        Where-Object { $_.Name -like "$FeatureNum-*" } |
-        Select-Object -First 1)
-}
-
 function ConvertTo-CleanBranchName {
    param([string]$Name)

    return $Name.ToLower() -replace '[^a-z0-9]', '-' -replace '-{2,}', '-' -replace '^-', '' -replace '-$', ''
 }
-
-function Get-FittedBranchName {
-    param(
-        [string]$FeatureNum,
-        [string]$BranchSuffix
-    )
-
-    $fittedName = "$FeatureNum-$BranchSuffix"
-    if ($fittedName.Length -gt $maxBranchLength) {
-        $prefixLength = $FeatureNum.Length + 1
-        $maxSuffixLength = $maxBranchLength - $prefixLength
-        $truncatedSuffix = $BranchSuffix.Substring(0, [Math]::Min($BranchSuffix.Length, $maxSuffixLength))
-        $truncatedSuffix = $truncatedSuffix -replace '-$', ''
-        $fittedName = "$FeatureNum-$truncatedSuffix"
-    }
-
-    return $fittedName
-}
 # Load common functions (includes Get-RepoRoot and Resolve-Template)
 . "$PSScriptRoot/common.ps1"

@@ -210,40 +176,26 @@ if ($Timestamp) {
    }

    $featureNum = ('{0:000}' -f $resolvedNumber)
-
-    # Treat an explicit number as a preference when its prefix is already used
-    # by a feature directory. Auto-detected numbers are already conflict-free.
-    $specConflict = $false
-    if ($hasNumber -and (Test-Path -LiteralPath $specsDir -PathType Container)) {
-        $requestedBranchName = Get-FittedBranchName -FeatureNum $featureNum -BranchSuffix $branchSuffix
-        $requestedDir = Join-Path $specsDir $requestedBranchName
-        if (-not $AllowExistingBranch -or -not (Test-Path -LiteralPath $requestedDir -PathType Container)) {
-            $specConflict = Test-SpecPrefixInUse -SpecsDir $specsDir -FeatureNum $featureNum
-        }
-    }
-
-    if ($specConflict) {
-        $requestedNum = $featureNum
-        $highestNumber = Get-HighestNumberFromSpecs -SpecsDir $specsDir
-        $resolvedNumber = $highestNumber
-        do {
-            if ($resolvedNumber -eq [long]::MaxValue) {
-                Write-Error "Error: feature number must be between 0 and $([long]::MaxValue), got '9223372036854775808'"
-                exit 1
-            }
-            $resolvedNumber++
-            $featureNum = ('{0:000}' -f $resolvedNumber)
-        } while (Test-SpecPrefixInUse -SpecsDir $specsDir -FeatureNum $featureNum)
-        [Console]::Error.WriteLine("[specify] Warning: -Number $requestedNum conflicts with an existing spec directory; using $featureNum instead")
-    }
-
+    $branchName = "$featureNum-$branchSuffix"
 }

 # GitHub enforces a 244-byte limit on branch names
 # Validate and truncate if necessary
-$originalBranchName = "$featureNum-$branchSuffix"
-$branchName = Get-FittedBranchName -FeatureNum $featureNum -BranchSuffix $branchSuffix
-if ($branchName -ne $originalBranchName) {
+$maxBranchLength = 244
+if ($branchName.Length -gt $maxBranchLength) {
+    # Calculate how much we need to trim from suffix
+    # Account for prefix length: timestamp (15) + hyphen (1) = 16, or sequential (3) + hyphen (1) = 4
+    $prefixLength = $featureNum.Length + 1
+    $maxSuffixLength = $maxBranchLength - $prefixLength
+
+    # Truncate suffix
+    $truncatedSuffix = $branchSuffix.Substring(0, [Math]::Min($branchSuffix.Length, $maxSuffixLength))
+    # Remove trailing hyphen if truncation created one
+    $truncatedSuffix = $truncatedSuffix -replace '-$', ''
+
+    $originalBranchName = $branchName
+    $branchName = "$featureNum-$truncatedSuffix"
+
    [Console]::Error.WriteLine("[specify] Warning: Branch name exceeded GitHub's 244-byte limit")
    [Console]::Error.WriteLine("[specify] Original: $originalBranchName ($($originalBranchName.Length) bytes)")
    [Console]::Error.WriteLine("[specify] Truncated to: $branchName ($($branchName.Length) bytes)")
@@ -130,31 +130,14 @@ def _print_paths_only(paths: FeaturePaths, json_mode: bool) -> None:
    print(f"TASKS: {paths.tasks}")


-def _status_marker(ok: bool) -> str:
-    """Return the status glyph, downgraded to ASCII when stdout cannot encode it.
-
-    On Windows sys.stdout falls back to the ANSI code page whenever it is not a
-    console - a pipe or a file redirect, which is how agents and workflow steps
-    invoke these scripts - and U+2713 is unencodable in cp1252, so printing it
-    raised UnicodeEncodeError and aborted the report right after
-    "AVAILABLE_DOCS:". "[OK]"/"[FAIL]" is the ASCII rendering these markers
-    already have in-tree: see Test-FileExists in scripts/powershell/common.ps1
-    and normalize_status_text in tests/parity_helpers.py.
-    """
-    glyph = "✓" if ok else "✗"
-    try:
-        glyph.encode(getattr(sys.stdout, "encoding", None) or "utf-8")
-    except (LookupError, UnicodeEncodeError):
-        return "[OK]" if ok else "[FAIL]"
-    return glyph
-
-
 def _check_file(path: Path, description: str) -> None:
-    print(f"  {_status_marker(path.is_file())} {description}")
+    marker = "✓" if path.is_file() else "✗"
+    print(f"  {marker} {description}")


 def _check_dir(path: Path, description: str) -> None:
-    print(f"  {_status_marker(_dir_has_entries(path))} {description}")
+    marker = "✓" if _dir_has_entries(path) else "✗"
+    print(f"  {marker} {description}")


 def _print_text_results(paths: FeaturePaths, include_tasks: bool) -> None:
@@ -258,27 +258,16 @@ def get_invoke_separator(repo_root: Path) -> str:
    integration_json = repo_root / ".specify" / "integration.json"
    if not integration_json.is_file():
        return "."
-    # Split the parse out of the lookup and guard the top-level shape, matching
-    # read_feature_json_feature_directory above and the bash/PowerShell twins,
-    # which both fall back to "." for any unusable integration.json:
-    #   * a non-mapping top level ([], "forge", 42, null) is valid JSON, so
-    #     json.JSONDecodeError never fires and state.get(...) raised
-    #     AttributeError;
-    #   * a non-UTF-8 file raises UnicodeDecodeError, which is a ValueError --
-    #     not an OSError -- so it escaped the except tuple. Realistic on
-    #     Windows, where PowerShell 5.1's Out-File/`>` default to UTF-16.
    try:
        state = json.loads(integration_json.read_text(encoding="utf-8"))
-    except (OSError, UnicodeError, json.JSONDecodeError):
-        return "."
-    if not isinstance(state, dict):
-        return "."
-    key = state.get("default_integration") or state.get("integration") or ""
-    settings = state.get("integration_settings")
-    if isinstance(key, str) and isinstance(settings, dict):
-        entry = settings.get(key)
-        if isinstance(entry, dict) and entry.get("invoke_separator") in {".", "-"}:
-            return entry["invoke_separator"]
+        key = state.get("default_integration") or state.get("integration") or ""
+        settings = state.get("integration_settings")
+        if isinstance(key, str) and isinstance(settings, dict):
+            entry = settings.get(key)
+            if isinstance(entry, dict) and entry.get("invoke_separator") in {".", "-"}:
+                return entry["invoke_separator"]
+    except (OSError, json.JSONDecodeError):
+        pass
    return "."


@@ -76,7 +76,7 @@ Options:
  --dry-run           Compute feature name and paths without creating directories or files
  --allow-existing-branch  Reuse an existing feature directory if it already exists
  --short-name <name> Provide a custom short name (2-4 words) for the feature
-  --number N          Prefer a feature number (auto-corrected if its specs prefix exists)
+  --number N          Specify branch number manually (overrides auto-detection)
  --timestamp         Use timestamp prefix (YYYYMMDD-HHMMSS) instead of sequential numbering
  --help, -h          Show this help message

@@ -204,43 +204,6 @@ def _get_highest_from_specs(specs_dir: Path) -> int:
    return highest


-def _fit_branch_name(feature_num: str, branch_suffix: str) -> str:
-    """Fit a feature prefix and suffix within GitHub's branch-name limit."""
-    branch_name = f"{feature_num}-{branch_suffix}"
-    if len(branch_name) <= _MAX_BRANCH_LENGTH:
-        return branch_name
-
-    max_suffix_length = _MAX_BRANCH_LENGTH - (len(feature_num) + 1)
-    truncated_suffix = re.sub(r"-$", "", branch_suffix[:max_suffix_length])
-    return f"{feature_num}-{truncated_suffix}"
-
-
-def _spec_prefix_exists(specs_dir: Path, feature_num: str) -> bool:
-    """Return whether a spec directory owns the given numeric prefix."""
-    try:
-        return any(
-            entry.is_dir() and entry.name.startswith(f"{feature_num}-")
-            for entry in specs_dir.iterdir()
-        )
-    except OSError:
-        # Match Bash globbing and PowerShell's ErrorAction=SilentlyContinue.
-        return False
-
-
-def _has_spec_prefix_conflict(
-    specs_dir: Path,
-    feature_num: str,
-    requested_dir: Path,
-    *,
-    allow_existing: bool,
-) -> bool:
-    """Return whether another spec directory owns the requested prefix."""
-    if allow_existing and requested_dir.is_dir():
-        return False
-
-    return _spec_prefix_exists(specs_dir, feature_num)
-
-
 def main(argv: list[str] | None = None) -> int:
    argv0 = sys.argv[0]
    args = _parse_args(list(argv if argv is not None else sys.argv[1:]), argv0)
@@ -298,48 +261,18 @@ def main(argv: list[str] | None = None) -> int:
            return 1
        feature_num = f"{number:03d}"

-        # Treat an explicit number as a preference when its prefix is already used
-        # by a feature directory. Auto-detected numbers are already conflict-free.
-        if branch_number:
-            requested_branch_name = _fit_branch_name(feature_num, branch_suffix)
-            requested_dir = specs_dir / requested_branch_name
-            spec_conflict = _has_spec_prefix_conflict(
-                specs_dir,
-                feature_num,
-                requested_dir,
-                allow_existing=args.allow_existing,
-            )
-            if spec_conflict:
-                requested_num = feature_num
-                number = _get_highest_from_specs(specs_dir)
-                while True:
-                    number += 1
-                    if number > _MAX_FEATURE_NUMBER:
-                        print(
-                            f"Error: feature number must be between 0 and "
-                            f"{_MAX_FEATURE_NUMBER}, got '{number}'",
-                            file=sys.stderr,
-                        )
-                        return 1
-                    feature_num = f"{number:03d}"
-                    if not _spec_prefix_exists(specs_dir, feature_num):
-                        break
-                print(
-                    f"[specify] Warning: --number {requested_num} conflicts with "
-                    f"an existing spec directory; using {feature_num} instead",
-                    file=sys.stderr,
-                )
-
    max_suffix_length = _MAX_BRANCH_LENGTH - (len(feature_num) + 1)
    if max_suffix_length <= 0:
        print("Error: feature number is too long for a branch name", file=sys.stderr)
        return 1

-    original_branch_name = f"{feature_num}-{branch_suffix}"
-    branch_name = _fit_branch_name(feature_num, branch_suffix)
+    branch_name = f"{feature_num}-{branch_suffix}"

    # GitHub enforces a 244-byte limit on branch names.
-    if branch_name != original_branch_name:
+    if len(branch_name) > _MAX_BRANCH_LENGTH:
+        truncated_suffix = re.sub(r"-$", "", branch_suffix[:max_suffix_length])
+        original_branch_name = branch_name
+        branch_name = f"{feature_num}-{truncated_suffix}"
        print(
            "[specify] Warning: Branch name exceeded GitHub's 244-byte limit",
            file=sys.stderr,
@@ -55,31 +55,14 @@ def _available_docs(paths: FeaturePaths) -> list[str]:
    return docs


-def _status_marker(ok: bool) -> str:
-    """Return the status glyph, downgraded to ASCII when stdout cannot encode it.
-
-    On Windows sys.stdout falls back to the ANSI code page whenever it is not a
-    console - a pipe or a file redirect, which is how agents and workflow steps
-    invoke these scripts - and U+2713 is unencodable in cp1252, so printing it
-    raised UnicodeEncodeError and aborted the report mid-listing.
-    "[OK]"/"[FAIL]" is the ASCII rendering these markers already have in-tree:
-    see Test-FileExists in scripts/powershell/common.ps1 and
-    normalize_status_text in tests/parity_helpers.py.
-    """
-    glyph = "✓" if ok else "✗"
-    try:
-        glyph.encode(getattr(sys.stdout, "encoding", None) or "utf-8")
-    except (LookupError, UnicodeEncodeError):
-        return "[OK]" if ok else "[FAIL]"
-    return glyph
-
-
 def _check_file(path: Path, description: str) -> None:
-    print(f"  {_status_marker(path.is_file())} {description}")
+    marker = "✓" if path.is_file() else "✗"
+    print(f"  {marker} {description}")


 def _check_dir(path: Path, description: str) -> None:
-    print(f"  {_status_marker(_dir_has_entries(path))} {description}")
+    marker = "✓" if _dir_has_entries(path) else "✗"
+    print(f"  {marker} {description}")


 def main(argv: list[str] | None = None) -> int:
@@ -77,9 +77,7 @@ from ._version import (
 from ._agent_config import (
    AGENT_CONFIG as AGENT_CONFIG,
    DEFAULT_INIT_INTEGRATION as DEFAULT_INIT_INTEGRATION,
-    DEFAULT_INIT_INTEGRATION_ENV_VAR as DEFAULT_INIT_INTEGRATION_ENV_VAR,
    SCRIPT_TYPE_CHOICES as SCRIPT_TYPE_CHOICES,
-    resolve_default_init_integration as resolve_default_init_integration,
 )
 from ._init_options import (
    INIT_OPTIONS_FILE as INIT_OPTIONS_FILE,
@@ -116,7 +114,6 @@ def _refresh_shared_templates(
    project_path: Path,
    *,
    invoke_separator: str,
-    invoke_prefix: str = "/",
    force: bool = False,
 ) -> None:
    """Refresh default-sensitive shared templates without touching scripts."""
@@ -127,7 +124,6 @@ def _refresh_shared_templates(
        repo_root=_repo_root(),
        console=console,
        invoke_separator=invoke_separator,
-        invoke_prefix=invoke_prefix,
        force=force,
    )

@@ -138,7 +134,6 @@ def _install_shared_infra(
    tracker: StepTracker | None = None,
    force: bool = False,
    invoke_separator: str = ".",
-    invoke_prefix: str = "/",
    refresh_managed: bool = False,
    refresh_hint: str | None = None,
 ) -> bool:
@@ -182,7 +177,6 @@ def _install_shared_infra(
        console=console,
        force=force,
        invoke_separator=invoke_separator,
-        invoke_prefix=invoke_prefix,
        refresh_managed=refresh_managed,
        refresh_hint=refresh_hint,
    )
@@ -194,7 +188,6 @@ def _install_shared_infra_or_exit(
    tracker: StepTracker | None = None,
    force: bool = False,
    invoke_separator: str = ".",
-    invoke_prefix: str = "/",
    refresh_managed: bool = False,
    refresh_hint: str | None = None,
 ) -> bool:
@@ -205,7 +198,6 @@ def _install_shared_infra_or_exit(
            tracker=tracker,
            force=force,
            invoke_separator=invoke_separator,
-            invoke_prefix=invoke_prefix,
            refresh_managed=refresh_managed,
            refresh_hint=refresh_hint,
        )
@@ -516,11 +508,6 @@ _register_extension_cmds(app)
 from .integrations._commands import register as _register_integration_cmds  # noqa: E402
 _register_integration_cmds(app)

-
-# ===== Event Commands =====
-from .commands.event import register as _register_event_cmds  # noqa: E402
-_register_event_cmds(app)
-
 # Re-export selected helpers to preserve the public import surface.
 from .integrations._helpers import (  # noqa: E402
    _clear_init_options_for_integration as _clear_init_options_for_integration,
@@ -1,8 +1,6 @@
 """Agent configuration constants derived from the integration registry."""
 from __future__ import annotations

-import os
-import sys
 from typing import Any


@@ -19,36 +17,6 @@ AGENT_CONFIG: dict[str, dict[str, Any]] = _build_agent_config()

 DEFAULT_INIT_INTEGRATION = "copilot"

-#: Environment variable used to override the fallback integration that
-#: ``specify init`` selects in non-interactive sessions.  Follows the existing
-#: ``SPECKIT_INTEGRATION_*`` namespace (see ``SPECKIT_INTEGRATION_<KEY>_EXECUTABLE``
-#: and ``SPECKIT_INTEGRATION_CATALOG_URL``).
-DEFAULT_INIT_INTEGRATION_ENV_VAR = "SPECKIT_INTEGRATION_DEFAULT"
-
-
-def resolve_default_init_integration() -> str:
-    """Return the default init integration, honoring an env-var override.
-
-    Reads :data:`DEFAULT_INIT_INTEGRATION_ENV_VAR`
-    (``SPECKIT_INTEGRATION_DEFAULT``).  When it names a registered integration
-    key, that key is returned; otherwise the hardcoded
-    :data:`DEFAULT_INIT_INTEGRATION` (``"copilot"``) is used.  An invalid value
-    emits a warning to stderr rather than silently falling back, so operators
-    can tell a typo from an intentional default.
-    """
-    override = (os.environ.get(DEFAULT_INIT_INTEGRATION_ENV_VAR) or "").strip()
-    if not override:
-        return DEFAULT_INIT_INTEGRATION
-    if override in AGENT_CONFIG:
-        return override
-    print(
-        f"Warning: {DEFAULT_INIT_INTEGRATION_ENV_VAR}='{override}' is not a "
-        f"recognized integration; falling back to '{DEFAULT_INIT_INTEGRATION}'. "
-        f"Choose from: {', '.join(sorted(AGENT_CONFIG.keys()))}.",
-        file=sys.stderr,
-    )
-    return DEFAULT_INIT_INTEGRATION
-
 SCRIPT_TYPE_CHOICES: dict[str, str] = {
    "sh": "POSIX Shell (bash/zsh)",
    "ps": "PowerShell",
@@ -102,17 +102,8 @@ def resolve_github_release_asset_api_url(

    from specify_cli._download_security import read_response_limited

-    # Accessing ``.hostname`` (like ``.port`` below) raises ValueError on a
-    # malformed authority, e.g. an invalid bracketed IPv6 host
-    # ``https://[not-an-ip]/...``. The function's contract is to return None for
-    # anything it can't resolve, not to raise, so guard the read. ``download_url``
-    # is server-controlled here (a catalog ``download_url`` payload), so a
-    # malformed value must not leak a raw traceback past the caller.
-    try:
-        parsed = urlparse(download_url)
-        hostname = (parsed.hostname or "").lower()
-    except ValueError:
-        return None
+    parsed = urlparse(download_url)
+    hostname = (parsed.hostname or "").lower()
    parts = [unquote(part) for part in parsed.path.strip("/").split("/")]

    is_ghes = (
@@ -159,9 +150,8 @@ def resolve_github_release_asset_api_url(
    if len(parts) < 6 or parts[2:4] != ["releases", "download"]:
        return None

-    owner, repo = parts[0], parts[1]
-    tag = "/".join(parts[4:-1])
-    asset_name = parts[-1]
+    owner, repo, tag = parts[0], parts[1], parts[4]
+    asset_name = "/".join(parts[5:])
    encoded_tag = quote(tag, safe="")
    release_url = f"{api_base}/repos/{owner}/{repo}/releases/tags/{encoded_tag}"

@@ -3,22 +3,12 @@
 import json
 from collections.abc import Mapping
 from pathlib import Path
-from typing import Any, Union
+from typing import Any


 INIT_OPTIONS_FILE = ".specify/init-options.json"


-class _MissingInitOptionsFile:
-    """Sentinel: init-options.json does not exist at all (legacy layout)."""
-
-    def __repr__(self) -> str:  # pragma: no cover - debug aid only
-        return "MISSING_INIT_OPTIONS_FILE"
-
-
-MISSING_INIT_OPTIONS_FILE = _MissingInitOptionsFile()
-
-
 def save_init_options(project_path: Path, options: dict[str, Any]) -> None:
    """Persist the CLI options used during ``specify init``."""
    dest = project_path / INIT_OPTIONS_FILE
@@ -44,40 +34,3 @@ def load_init_options(project_path: Path) -> dict[str, Any]:
 def is_ai_skills_enabled(opts: Mapping[str, Any] | None) -> bool:
    """Return True only when init options explicitly enable AI skills."""
    return isinstance(opts, Mapping) and opts.get("ai_skills") is True
-
-
-def resolve_active_agent_for_registration(
-    project_path: Path,
-) -> Union[str, None, _MissingInitOptionsFile]:
-    """Resolve the active integration key for active-only registration (#2948).
-
-    ``load_init_options`` collapses "no file", "unreadable/malformed file",
-    and "valid file with no recorded active agent" into the same ``{}``
-    result, which previously made corrupted-but-present init-options behave
-    like a legacy pre-init-options project and fall back to registering
-    every detected agent. This helper distinguishes those cases explicitly:
-
-    - Returns :data:`MISSING_INIT_OPTIONS_FILE` when init-options.json does
-      not exist at all (pre-init-options layout or direct library use).
-      Callers should fall back to detection-based registration for all
-      agents, matching the original pre-#2948 behavior for such projects.
-    - Returns ``None`` when init-options.json exists but could not provide a
-      valid non-empty string active agent (malformed/unreadable JSON,
-      non-object payload, or a non-string/empty ``ai`` value). Callers must
-      fail closed (register nothing) rather than treat this like "no file"
-      or pass a non-string key into agent-config lookups.
-    - Returns the active agent key (a non-empty string) otherwise.
-    """
-    path = project_path / INIT_OPTIONS_FILE
-    # A dangling symlink's target doesn't exist, so Path.exists() (which
-    # follows symlinks) returns False even though the path itself is
-    # present as a broken/corrupted entry. Treat any symlink as "present"
-    # so a dangling one fails closed via the invalid-file branch below
-    # instead of being mistaken for "no file at all" (legacy fallback).
-    if not path.is_symlink() and not path.exists():
-        return MISSING_INIT_OPTIONS_FILE
-
-    active_agent = load_init_options(project_path).get("ai")
-    if isinstance(active_agent, str) and active_agent:
-        return active_agent
-    return None
@@ -12,7 +12,7 @@ from __future__ import annotations
 DOLLAR_SKILLS_AGENTS: frozenset[str] = frozenset({"codex", "zcode"})

 # Agents that always render /speckit-<name>, regardless of ai_skills.
-ALWAYS_SLASH_AGENTS: frozenset[str] = frozenset({"devin", "droid", "grok", "trae", "zed"})
+ALWAYS_SLASH_AGENTS: frozenset[str] = frozenset({"devin", "grok", "trae", "zed"})

 # Agents that render /speckit-<name> only when ai_skills is enabled.
 CONDITIONAL_SLASH_AGENTS: frozenset[str] = frozenset(
@@ -29,9 +29,6 @@ CONDITIONAL_SLASH_AGENTS: frozenset[str] = frozenset(
    }
 )

-# Agents that render /skill:<name> (skill-colon invocation) when in skills mode.
-SKILL_COLON_AGENTS: frozenset[str] = frozenset({"kimi"})
-

 def is_dollar_skills_agent(selected_ai: str | None, ai_skills_enabled: bool) -> bool:
    """Return ``True`` if *selected_ai* uses ``$speckit-<name>`` invocations.
@@ -44,21 +41,6 @@ def is_dollar_skills_agent(selected_ai: str | None, ai_skills_enabled: bool) ->
    return selected_ai in DOLLAR_SKILLS_AGENTS and ai_skills_enabled


-def get_invocation_prefix(selected_ai: str | None, ai_skills_enabled: bool) -> str:
-    """Return the native invocation prefix for *selected_ai* in skills mode.
-
-    Returns ``"$"`` for dollar-skills agents (Codex, ZCode),
-    ``"/skill:"`` for skill-colon agents (Kimi), and ``"/"`` for all others.
-    """
-    if not isinstance(selected_ai, str):
-        return "/"
-    if selected_ai in DOLLAR_SKILLS_AGENTS and ai_skills_enabled:
-        return "$"
-    if selected_ai in SKILL_COLON_AGENTS and ai_skills_enabled:
-        return "/skill:"
-    return "/"
-
-
 def is_slash_skills_agent(selected_ai: str | None, ai_skills_enabled: bool) -> bool:
    """Return ``True`` if *selected_ai* uses ``/speckit-<name>`` invocations.

@@ -12,7 +12,6 @@ import yaml
 from pathlib import Path, PurePosixPath, PureWindowsPath
 from typing import Any
 from ._console import console
-from ._download_security import normalize_zip_member_name

 CLAUDE_LOCAL_PATH = Path.home() / ".claude" / "local" / "claude"
 CLAUDE_NPM_LOCAL_PATH = Path.home() / ".claude" / "local" / "node_modules" / ".bin" / "claude"
@@ -28,22 +27,19 @@ def relative_extension_path_violation(value: Any) -> str | None:
    ``None`` when it is an acceptable relative path within the extension
    directory.

-    Policy: the value must be a non-empty, portable file path with no
-    leading/trailing whitespace, absolute/anchored form, ``..`` traversal,
-    platform-reserved component, or directory-only suffix. The value is
+    Policy: the value must be a non-empty string with no leading/trailing
+    whitespace, no absolute/anchored form, and no ``..`` traversal. The value is
    evaluated under both POSIX and Windows path semantics because a native
    ``Path`` is OS-dependent (a ``PurePosixPath`` on POSIX does not interpret
-    Windows drive/UNC forms, and ``C:foo`` is anchored but not
-    ``is_absolute()`` yet resolves against the CWD on its drive). Rejecting any
-    non-empty anchor covers POSIX-absolute (``/abs``), Windows drive-relative
-    (``C:foo``), Windows absolute (``C:\\foo``), and UNC/rooted forms.
+    Windows drive/UNC forms, and ``C:foo`` is anchored but not ``is_absolute()``
+    yet resolves against the CWD on its drive). Rejecting any non-empty anchor
+    covers POSIX-absolute (``/abs``), Windows drive-relative (``C:foo``), Windows
+    absolute (``C:\\foo``), and UNC/rooted forms.
    """
    if not isinstance(value, str) or not value:
        return "must be a non-empty string"
    if value.strip() != value:
        return "must not have leading or trailing whitespace"
-    if "\\" in value:
-        return "must use forward slashes as path separators"
    posix_path = PurePosixPath(value)
    win_path = PureWindowsPath(value)
    if (
@@ -56,15 +52,6 @@ def relative_extension_path_violation(value: Any) -> str | None:
            "must be a relative path within the extension directory "
            "(no absolute paths, drive letters, or '..' segments)"
        )
-    if value.endswith(("/", "\\")):
-        return "must name a file or command, not a directory"
-    try:
-        normalize_zip_member_name(value)
-    except ValueError:
-        return (
-            "must use portable path components "
-            "(no reserved names or platform-invalid characters)"
-        )
    return None


@@ -82,14 +69,21 @@ def run_command(
    cmd: list[str],
    check_return: bool = True,
    capture: bool = False,
+    shell: bool = False,
 ) -> str | None:
    """Run a command without invoking a shell and optionally capture output.

-    Commands are always executed with ``shell=False`` and must be passed as an
-    argv ``list[str]``. There is deliberately no ``shell`` parameter: the
-    argv-list contract makes shell interpolation impossible by construction, so
-    the shell-injection surface cannot be re-enabled at a call site.
+    The ``shell`` parameter is kept in the signature so existing keyword
+    callers (and the re-export from ``specify_cli``) don't raise ``TypeError``,
+    but only the default ``shell=False`` is honoured. ``shell=True`` is
+    rejected with ``ValueError`` rather than silently ignored, so the
+    unsupported mode fails loudly instead of running with a different meaning.
    """
+    if shell:
+        raise ValueError(
+            "run_command() does not support shell=True; pass argv as a list"
+        )
+
    try:
        if capture:
            result = subprocess.run(cmd, check=check_return, capture_output=True, text=True)
@@ -192,8 +186,8 @@ def handle_vscode_settings(sub_item, dest_file, rel_path, verbose=False, tracker

            os.replace(temp_path, target_file)
        except Exception:
-            if temp_path:
-                temp_path.unlink(missing_ok=True)
+            if temp_path and temp_path.exists():
+                temp_path.unlink()
            raise

    try:
@@ -27,7 +27,6 @@ from pathlib import Path

 import typer
 from packaging.version import InvalidVersion, Version
-from rich.markup import escape as _escape_markup

 from ._download_security import MAX_JSON_METADATA_BYTES, read_response_limited
 from ._console import console
@@ -1231,10 +1230,7 @@ def self_upgrade(
    tag: str | None = typer.Option(
        None,
        "--tag",
-        # Typer renders help through Rich, so escape the literal bracket (\[)
-        # or `[suffix]` is parsed as a style tag and dropped -- `--help` then
-        # advertises only `(vX.Y.Z)`, contradicting docs/upgrade.md and README.
-        help="Pin the target version (vX.Y.Z\\[suffix]). Without --tag, the "
+        help="Pin the target version (vX.Y.Z[suffix]). Without --tag, the "
        "latest stable release is resolved via GitHub Releases.",
    ),
 ) -> None:
@@ -1274,14 +1270,7 @@ def self_upgrade(
        try:
            tag = _validate_tag(tag)
        except typer.BadParameter as exc:
-            # Escape at the print site rather than baking `\[` into
-            # _INVALID_TAG_MESSAGE: the message is also raised through
-            # typer.BadParameter, which Click renders without Rich, so the
-            # constant must stay plain text. Unescaped, Rich parses the literal
-            # `[suffix]` as a style tag and drops it, leaving the user with
-            # "expected vMAJOR.MINOR.PATCH" -- implying a bare vX.Y.Z is the only
-            # accepted form when -rc1 / .dev0 / +build.42 are all valid.
-            console.print(_escape_markup(str(exc)), soft_wrap=True)
+            console.print(str(exc), soft_wrap=True)
            raise typer.Exit(1) from exc

    plan, failure_reason = _build_upgrade_plan(target_tag_override=tag)
@@ -10,12 +10,11 @@ import os
 import re
 from copy import deepcopy
 from pathlib import Path
-from typing import Any, Dict, Iterable, List, Optional
+from typing import Any, Dict, List, Optional

 import yaml

 from ._init_options import is_ai_skills_enabled, load_init_options
-from ._invocation_style import get_invocation_prefix
 from ._toml_string import escape_toml_basic as _escape_toml_basic
 from ._toml_string import has_illegal_toml_control as _has_illegal_toml_control
 from ._utils import relative_extension_path_violation
@@ -157,11 +156,7 @@ class CommandRegistrar:
            return ""

        yaml_str = yaml.dump(
-            fm,
-            default_flow_style=False,
-            sort_keys=False,
-            allow_unicode=True,
-            width=float("inf"),
+            fm, default_flow_style=False, sort_keys=False, allow_unicode=True
        )
        return f"---\n{yaml_str}---\n"

@@ -275,7 +270,7 @@ class CommandRegistrar:
        return text

    def render_markdown_command(
-        self, frontmatter: dict, body: str, source_id: str, context_note: Optional[str] = None
+        self, frontmatter: dict, body: str, source_id: str, context_note: str = None
    ) -> str:
        """Render command in Markdown format.

@@ -306,20 +301,8 @@ class CommandRegistrar:
        toml_lines = []

        if "description" in frontmatter:
-            # Frontmatter comes from ``yaml.safe_load``, so ``description`` can
-            # be any YAML type: ``description:`` with no value yields None,
-            # ``description: 2`` an int, an unquoted ``true`` a bool.
-            # ``_render_basic_toml_string`` iterates the value and calls ord()
-            # on each character, so a non-string raises a raw TypeError -- and a
-            # list of single-character items is silently concatenated into a
-            # wrong value (``["a", "b"]`` -> ``"ab"``). Coerce first, matching
-            # ``render_yaml_command`` below and ``TomlIntegration
-            # ._extract_description``, which both normalise it already.
-            description = frontmatter["description"]
-            if not isinstance(description, str):
-                description = str(description) if description is not None else ""
            toml_lines.append(
-                f"description = {self._render_basic_toml_string(description)}"
+                f"description = {self._render_basic_toml_string(frontmatter['description'])}"
            )
            toml_lines.append("")

@@ -614,8 +597,8 @@ class CommandRegistrar:
        source_id: str,
        source_dir: Path,
        project_root: Path,
-        context_note: Optional[str] = None,
-        _resolved_dir: Optional[Path] = None,
+        context_note: str = None,
+        _resolved_dir: Path = None,
        link_outputs: bool = False,
        extension_id: Optional[str] = None,
    ) -> List[str]:
@@ -676,38 +659,22 @@ class CommandRegistrar:
        # correct when a stale ``.bob/skills`` directory coexists with
        # ``.bob/commands``.
        _sep = agent_config.get("invoke_separator", ".")
-        registrar_writes_skills = agent_config.get("extension") == "/SKILL.md"
        try:
            from specify_cli.integrations import get_integration  # noqa: PLC0415

            _integ = get_integration(agent_name)
            if _integ is not None:
+                registrar_writes_skills = (
+                    agent_config.get("extension") == "/SKILL.md"
+                )
                _sep = _integ.invoke_separator_for_mode(registrar_writes_skills)
-        except (ImportError, ValueError, KeyError):
+        except Exception:
            pass
-        _prefix = get_invocation_prefix(agent_name, registrar_writes_skills)

        for cmd_info in commands:
            cmd_name = cmd_info["name"]
            aliases = cmd_info.get("aliases", [])
            cmd_file = cmd_info["file"]
-            name_reason = relative_extension_path_violation(cmd_name)
-            if name_reason:
-                raise ValueError(
-                    f"Invalid command name {cmd_name!r}: {name_reason}"
-                )
-            if aliases is None:
-                aliases = []
-            if not isinstance(aliases, list):
-                raise ValueError(
-                    f"Aliases for command {cmd_name!r} must be a list"
-                )
-            for alias in aliases:
-                alias_reason = relative_extension_path_violation(alias)
-                if alias_reason:
-                    raise ValueError(
-                        f"Invalid command alias {alias!r}: {alias_reason}"
-                    )

            # Guard against path traversal using the single shared policy in
            # relative_extension_path_violation(), so the runtime guard stays
@@ -788,7 +755,7 @@ class CommandRegistrar:
            # (base.py itself imports CommandRegistrar lazily).
            from specify_cli.integrations.base import IntegrationBase  # noqa: PLC0415

-            body = IntegrationBase.resolve_command_refs(body, _sep, _prefix)
+            body = IntegrationBase.resolve_command_refs(body, _sep)

            output_name = self._compute_output_name(agent_name, cmd_name, agent_config)

@@ -990,16 +957,10 @@ class CommandRegistrar:
            project_root: Path to project root
            cmd_name: Command name (e.g. 'speckit.my-ext.example')
        """
-        name_reason = relative_extension_path_violation(cmd_name)
-        if name_reason:
-            raise ValueError(
-                f"Invalid Copilot prompt name {cmd_name!r}: {name_reason}"
-            )
        prompts_dir = project_root / ".github" / "prompts"
        prompts_dir.mkdir(parents=True, exist_ok=True)
        prompt_file = prompts_dir / f"{cmd_name}.prompt.md"
        CommandRegistrar._ensure_inside(prompt_file, prompts_dir)
-        prompt_file.parent.mkdir(parents=True, exist_ok=True)
        prompt_file.write_text(f"---\nagent: {cmd_name}\n---\n", encoding="utf-8")

    @staticmethod
@@ -1055,11 +1016,10 @@ class CommandRegistrar:
        source_id: str,
        source_dir: Path,
        project_root: Path,
-        context_note: Optional[str] = None,
+        context_note: str = None,
        link_outputs: bool = False,
        create_missing_active_skills_dir: bool = False,
        extension_id: Optional[str] = None,
-        only_agent: Optional[str] = None,
    ) -> Dict[str, List[str]]:
        """Register commands for all detected agents in the project.

@@ -1077,8 +1037,6 @@ class CommandRegistrar:
                skills directory) and is skipped when safe resolution or
                creation fails.
            extension_id: Extension id when rendering extension-owned commands.
-            only_agent: If set, restrict registration to this single agent
-                while keeping all detection and recovery safeguards (#2948).

        Returns:
            Dictionary mapping agent names to list of registered commands
@@ -1102,8 +1060,6 @@ class CommandRegistrar:
                )
        active_created_skills_dir: Optional[Path] = None
        for agent_name, agent_config in self.AGENT_CONFIGS.items():
-            if only_agent is not None and agent_name != only_agent:
-                continue
            active_skills_output = (
                agent_name == active_skills_agent
                and agent_config.get("extension") == "/SKILL.md"
@@ -1209,8 +1165,6 @@ class CommandRegistrar:
        context_note: Optional[str] = None,
        link_outputs: bool = False,
        extension_id: Optional[str] = None,
-        only_agent: Optional[str] = None,
-        extra_agents: Optional[Iterable[str]] = None,
    ) -> Dict[str, List[str]]:
        """Register commands for all non-skill agents in the project.

@@ -1227,29 +1181,13 @@ class CommandRegistrar:
            link_outputs: If True, create dev-mode symlinks for rendered
                command files when supported by the OS.
            extension_id: Extension id when rendering extension-owned commands.
-            only_agent: If set, restrict registration to this single agent
-                (#2948). An agent name that matches no configured agent
-                (e.g. an empty string) yields no registrations at all.
-            extra_agents: Additional agent names to register for besides
-                ``only_agent``. Used by post-removal reconciliation to also
-                restore surviving content into historical agent directories
-                a just-removed preset actually wrote to, not only the
-                currently active agent (#2948). Ignored when ``only_agent``
-                is ``None`` (already unrestricted).

        Returns:
            Dictionary mapping agent names to list of registered commands
        """
        results = {}
        self._ensure_configs()
-        extra_agents_set = frozenset(extra_agents) if extra_agents else frozenset()
        for agent_name, agent_config in self.AGENT_CONFIGS.items():
-            if (
-                only_agent is not None
-                and agent_name != only_agent
-                and agent_name not in extra_agents_set
-            ):
-                continue
            if agent_config.get("extension") == "/SKILL.md":
                continue
            detect_dir_str = agent_config.get("detect_dir")
@@ -5,7 +5,6 @@ from __future__ import annotations
 import base64
 import json as _json
 import os
-import shutil
 import subprocess
 from typing import TYPE_CHECKING

@@ -72,27 +71,9 @@ class AzureDevOpsAuth(AuthProvider):
    def _acquire_via_az_cli() -> str | None:
        """Run ``az account get-access-token`` and return the access token."""
        try:
-            # Windows: ``subprocess.run`` calls ``CreateProcess``, which does
-            # not consult ``PATHEXT``, so a bare ``"az"`` (installed as
-            # ``az.cmd``) fails with ``WinError 2`` even after ``az login``.
-            # Resolve via ``shutil.which`` (which honors ``PATHEXT``) so the
-            # ``.cmd`` shim works. On POSIX this is a harmless lookup that
-            # returns the same executable.
-            #
-            # Require an ABSOLUTE result: on Windows ``shutil.which`` prepends
-            # the current directory to the search path (unless
-            # ``NoDefaultCurrentDirectoryInExePath`` is set), so a stray
-            # ``.\az.cmd`` in the working directory would otherwise be resolved
-            # ahead of the real Azure CLI and run for a credential operation. A
-            # legitimate install always resolves to an absolute path, so this
-            # costs nothing; falling back to the bare ``"az"`` preserves the
-            # prior behavior (and the existing OSError path) when ``az`` is
-            # absent.
-            resolved = shutil.which("az")
-            az = resolved if resolved and os.path.isabs(resolved) else "az"
            result = subprocess.run(  # noqa: S603, S607
                [
-                    az,
+                    "az",
                    "account",
                    "get-access-token",
                    "--resource",
@@ -13,7 +13,6 @@ import stat
 from dataclasses import dataclass
 from fnmatch import fnmatch
 from pathlib import Path
-from typing import Any
 from urllib.parse import urlparse


@@ -54,19 +53,6 @@ def _is_valid_host_pattern(pattern: str) -> bool:
    return pattern.startswith("*.") and "*" not in pattern[2:]


-def _norm(value: Any) -> Any:
-    """Strip surrounding whitespace from a whitespace-insignificant string
-    config reference (env-var names, tenant/client ids) before it is stored.
-
-    These fields are validated on their ``.strip()``ed form, so an accidentally
-    padded value passes validation but then silently breaks the verbatim
-    ``os.environ.get(...)`` / URL lookups downstream. Normalizing at store time
-    mirrors how ``hosts`` is already handled (``h.strip().lower()``). Non-string
-    values (e.g. ``None``) pass through unchanged.
-    """
-    return value.strip() if isinstance(value, str) else value
-
-
 def load_auth_config(
    path: Path | None = None,
 ) -> list[AuthConfigEntry]:
@@ -196,10 +182,10 @@ def load_auth_config(
                provider=provider,
                auth=auth,
                token=token,
-                token_env=_norm(token_env),
-                tenant_id=_norm(entry_raw.get("tenant_id")),
-                client_id=_norm(entry_raw.get("client_id")),
-                client_secret_env=_norm(entry_raw.get("client_secret_env")),
+                token_env=token_env,
+                tenant_id=entry_raw.get("tenant_id"),
+                client_id=entry_raw.get("client_id"),
+                client_secret_env=entry_raw.get("client_secret_env"),
            )
        )

@@ -14,13 +14,14 @@ from .. import BundlerError
 from ..lib.yamlio import dump_yaml, ensure_within, load_yaml
 from ..models.catalog import (
    CONFIG_FILENAME,
-    CONFIG_SCHEMA_VERSION,
    BUILTIN_DEFAULT_STACK,
    CatalogSource,
    InstallPolicy,
    Scope,
 )

+CONFIG_SCHEMA_VERSION = "1.0"
+
 _BUILTIN_IDS = {raw["id"] for raw in BUILTIN_DEFAULT_STACK}

 # Windows absolute paths like ``C:\catalog.json`` parse with a single-letter
@@ -152,8 +153,6 @@ def add_source(
        # keeps that ValueError inside the guard instead of leaking a raw
        # traceback past the CLI's `except BundlerError`. Reuse the value below.
        hostname = parsed.hostname
-        # Accessing ``port`` performs urllib's syntax/range validation.
-        _ = parsed.port
    except ValueError as exc:
        raise BundlerError(f"Invalid catalog url: '{url}'.") from exc
    if not (parsed.scheme or parsed.path):
@@ -58,12 +58,7 @@ def load_yaml(path: Path) -> Any:
        raise BundlerError(f"File not found: {path}")
    try:
        text = path.read_text(encoding="utf-8")
-    except (OSError, UnicodeError) as exc:
-        # A non-UTF-8 file raises UnicodeDecodeError, which is a ValueError --
-        # NOT an OSError -- so it escaped this module's "IO failures degrade
-        # into actionable BundlerError" contract as a raw traceback. Realistic
-        # on Windows, where PowerShell 5.1's `Out-File`/`>` default to UTF-16.
-        # Matches the sibling catalog readers (catalogs.py, workflows/catalog.py).
+    except OSError as exc:
        raise BundlerError(f"Could not read {path}: {exc}") from exc
    try:
        has_node = yaml.compose(text) is not None
@@ -103,15 +98,9 @@ def load_json(path: Path) -> Any:
    try:
        with path.open("r", encoding="utf-8") as handle:
            return json.load(handle)
-    # JSONDecodeError stays FIRST: it and UnicodeDecodeError are sibling
-    # ValueError subclasses (neither subsumes the other), so malformed-but-
-    # decodable JSON keeps its more specific "Invalid JSON" message while a
-    # decode failure falls through to the read-error clause below.
    except json.JSONDecodeError as exc:
        raise BundlerError(f"Invalid JSON in {path}: {exc}") from exc
-    except (OSError, UnicodeError) as exc:
-        # See load_yaml: a non-UTF-8 file raises UnicodeDecodeError, which is
-        # not an OSError, and previously escaped as a raw traceback.
+    except OSError as exc:
        raise BundlerError(f"Could not read {path}: {exc}") from exc


@@ -15,11 +15,6 @@ from .. import BundlerError
 from ..lib.yamlio import ensure_within, load_yaml

 CONFIG_FILENAME = "bundle-catalogs.yml"
-# Supported bundle-catalogs.yml schema (major version). Both readers of the
-# file — this module's _merge_config and commands_impl/catalog_config._read —
-# reject an unsupported major version so a file written by a newer/incompatible
-# Spec Kit fails fast instead of being parsed under the wrong assumptions.
-CONFIG_SCHEMA_VERSION = "1.0"


 class InstallPolicy(str, Enum):
@@ -144,7 +139,6 @@ class CatalogEntry:
    license: str
    download_url: str
    requires_speckit_version: str
-    sha256: str | None = None
    provides: dict[str, int] = field(default_factory=dict)
    repository: str | None = None
    tags: tuple[str, ...] = ()
@@ -187,11 +181,6 @@ class CatalogEntry:
            license=str(data.get("license", "")).strip(),
            download_url=str(data.get("download_url", "")).strip(),
            requires_speckit_version=str(requires.get("speckit_version", "")).strip(),
-            sha256=(
-                None
-                if data.get("sha256") is None
-                else str(data["sha256"]).strip()
-            ),
            provides=dict(provides_raw),
            repository=(str(data["repository"]) if data.get("repository") else None),
            tags=_parse_tags(data.get("tags"), entry_id),
@@ -204,7 +193,6 @@ class CatalogEntry:
            description=self.description, author=self.author, license=self.license,
            download_url=self.download_url,
            requires_speckit_version=self.requires_speckit_version,
-            sha256=self.sha256,
            provides=self.provides, repository=self.repository, tags=self.tags,
            verified=self.verified, source_id=source.id,
            source_policy=source.install_policy,
@@ -279,23 +267,6 @@ def _merge_config(by_id: dict[str, CatalogSource], config_path: Path, scope: Sco
            f"Malformed catalog config at {config_path}: expected a mapping at "
            f"the top level, got {type(data).__name__}."
        )
-    # Reject an unsupported major schema version, matching the sibling reader
-    # commands_impl/catalog_config._read. Without this, a file written by a
-    # newer/incompatible Spec Kit was silently parsed under v1 assumptions on
-    # the resolution path (bundle search/install), while the other reader
-    # rejected it — the two readers disagreed. An absent schema_version stays
-    # valid (backward compatible with configs that omit it).
-    schema_version = data.get("schema_version")
-    if schema_version is not None and (
-        str(schema_version).strip().split(".")[0]
-        != CONFIG_SCHEMA_VERSION.split(".")[0]
-    ):
-        raise BundlerError(
-            f"Unsupported catalog config schema version "
-            f"'{str(schema_version).strip()}' at {config_path}; this Spec Kit "
-            f"understands version {CONFIG_SCHEMA_VERSION}. The file may have been "
-            "written by a newer version or is corrupt."
-        )
    catalogs = data.get("catalogs")
    if catalogs is None:
        return
@@ -96,19 +96,19 @@ class BundleManifest:
        if not isinstance(data, dict):
            raise BundlerError("Manifest must be a YAML mapping at the top level.")

-        schema_version = _text(data.get("schema_version"))
+        schema_version = str(data.get("schema_version", "")).strip()

        bundle_raw = data.get("bundle")
        if not isinstance(bundle_raw, dict):
            raise BundlerError("Manifest is missing the required 'bundle' mapping.")
        meta = BundleMeta(
-            id=_text(bundle_raw.get("id")),
-            name=_text(bundle_raw.get("name")),
-            version=_text(bundle_raw.get("version")),
-            role=_text(bundle_raw.get("role")),
-            description=_text(bundle_raw.get("description")),
-            author=_text(bundle_raw.get("author")),
-            license=_text(bundle_raw.get("license")),
+            id=str(bundle_raw.get("id", "")).strip(),
+            name=str(bundle_raw.get("name", "")).strip(),
+            version=str(bundle_raw.get("version", "")).strip(),
+            role=str(bundle_raw.get("role", "")).strip(),
+            description=str(bundle_raw.get("description", "")).strip(),
+            author=str(bundle_raw.get("author", "")).strip(),
+            license=str(bundle_raw.get("license", "")).strip(),
        )

        requires_raw = data.get("requires")
@@ -117,7 +117,7 @@ class BundleManifest:
        elif not isinstance(requires_raw, dict):
            raise BundlerError("'requires' must be a mapping when present.")
        requires = Requires(
-            speckit_version=_text(requires_raw.get("speckit_version")),
+            speckit_version=str(requires_raw.get("speckit_version", "")).strip(),
            tools=_parse_str_list(requires_raw.get("tools"), "requires.tools"),
            mcp=_parse_str_list(requires_raw.get("mcp"), "requires.mcp"),
        )
@@ -220,22 +220,6 @@ class BundleManifest:
        return self.integration is None


-def _text(raw: Any) -> str:
-    """Coerce a manifest scalar into stripped text, mapping an explicit null to ``""``.
-
-    A ``.get(key, "")`` default only covers a *missing* key. A key that is
-    present but null -- how YAML spells an empty field (``author:`` with nothing
-    after it) -- yields ``None``, and ``str(None)`` is the literal ``"None"``.
-    That text is non-empty, so it sailed past the ``if not value`` required-field
-    checks in :meth:`BundleManifest.structural_errors`: an empty required field
-    was silently accepted and the bundle shipped ``"None"`` as its
-    author/license/description.
-    """
-    if raw is None:
-        return ""
-    return str(raw).strip()
-
-
 def _parse_str_list(raw: Any, field_name: str) -> tuple[str, ...]:
    """Coerce a manifest list-of-strings field into a tuple of strings.

@@ -263,7 +247,7 @@ def _parse_refs(kind: str, raw: Any) -> list[ComponentRef]:
        refs.append(
            ComponentRef(
                kind=kind,
-                id=_text(item.get("id")),
+                id=str(item.get("id", "")).strip(),
                version=(str(item["version"]).strip() if item.get("version") else None),
                source=(str(item["source"]).strip() if item.get("source") else None),
                priority=priority,
@@ -16,9 +16,8 @@ from urllib.parse import ParseResult, urlparse
 from urllib.request import url2pathname

 from ..._assets import _locate_core_pack, _repo_root
-from ..._download_security import MAX_JSON_CATALOG_BYTES, read_response_limited
 from .. import BundlerError
-from ..lib.yamlio import load_json, loads_json
+from ..lib.yamlio import loads_json
 from ..models.catalog import CatalogSource
 from ..models.manifest import ComponentRef

@@ -77,8 +76,6 @@ def _validate_remote_url(source_id: str, url: str) -> None:
    try:
        parsed = urlparse(url)
        hostname = parsed.hostname
-        # Accessing ``port`` performs urllib's syntax/range validation.
-        _ = parsed.port
    except ValueError:
        raise BundlerError(
            f"Catalog '{source_id}' URL is malformed: {url}"
@@ -120,15 +117,7 @@ def make_catalog_fetcher(*, allow_network: bool = True):

    def fetch(source: CatalogSource) -> dict:
        url = source.url
-        try:
-            parsed = urlparse(url)
-            # Keep malformed authorities and ports inside the BundlerError
-            # contract even when a config file was edited by hand.
-            _ = parsed.port
-        except ValueError:
-            raise BundlerError(
-                f"Catalog {source.id!r} URL is malformed: {url!r}"
-            ) from None
+        parsed = urlparse(url)
        scheme = parsed.scheme.lower()

        if scheme == "builtin":
@@ -145,13 +134,13 @@ def make_catalog_fetcher(*, allow_network: bool = True):
            path = _file_url_to_path(parsed)
            if not path.exists():
                raise BundlerError(f"Catalog file not found: {path}")
-            return load_json(path)
+            return loads_json(path.read_text(encoding="utf-8"), origin=str(path))

        if scheme == "" or _is_windows_drive_path(url):
            path = Path(url)
            if not path.exists():
                raise BundlerError(f"Catalog file not found: {path}")
-            return load_json(path)
+            return loads_json(path.read_text(encoding="utf-8"), origin=str(path))

        if scheme in ("http", "https"):
            if not allow_network:
@@ -191,12 +180,7 @@ def _http_get_json(source_id: str, url: str) -> dict:
        ) as response:
            final_url = response.geturl()
            _validate_remote_url(source_id, final_url)
-            raw = read_response_limited(
-                response,
-                max_bytes=MAX_JSON_CATALOG_BYTES,
-                error_type=BundlerError,
-                label=f"bundle catalog '{source_id}'",
-            ).decode("utf-8")
+            raw = response.read().decode("utf-8")
    except BundlerError:
        raise
    except Exception as exc:  # noqa: BLE001
@@ -227,10 +211,6 @@ class DefaultPrimitiveInstaller:
        manager = self._manager_for(component, project_root)
        manager.install(component)

-    def refresh(self, project_root: Path, component: ComponentRef) -> None:
-        manager = self._manager_for(component, project_root)
-        manager.refresh(component)
-
    def remove(self, project_root: Path, component: ComponentRef) -> None:
        manager = self._manager_for(component, project_root)
        manager.remove(component)
@@ -93,11 +93,9 @@ def build_bundle(
            # extraction, but collapse to two canonical modes (0755 when any
            # execute bit is set on the source, otherwise 0644) so identical
            # inputs yield a byte-for-byte identical artifact.
-            with file_path.open("rb") as fh:
-                st = os.fstat(fh.fileno())
-                mode = 0o755 if st.st_mode & 0o111 else 0o644
-                info.external_attr = mode << 16
-                archive.writestr(info, fh.read())
+            mode = 0o755 if file_path.stat().st_mode & 0o111 else 0o644
+            info.external_attr = mode << 16
+            archive.writestr(info, file_path.read_bytes())

    return BuildResult(artifact_path=artifact_path, file_count=len(files))

@@ -85,17 +85,11 @@ def _bundled_manifest_version(manifest_path: Path, root_key: str) -> str | None:


 class _KindManager(Protocol):
-    def is_installed(self, component: ComponentRef) -> bool:
-        pass
+    def is_installed(self, component: ComponentRef) -> bool: ...

-    def install(self, component: ComponentRef) -> None:
-        pass
+    def install(self, component: ComponentRef) -> None: ...

-    def refresh(self, component: ComponentRef) -> None:
-        pass
-
-    def remove(self, component: ComponentRef) -> None:
-        pass
+    def remove(self, component: ComponentRef) -> None: ...


 def primitive_manager(
@@ -157,12 +151,6 @@ class _PresetKindManager:
            return False

    def install(self, component: ComponentRef) -> None:
-        self._do_install(component, force=False)
-
-    def refresh(self, component: ComponentRef) -> None:
-        self._do_install(component, force=True)
-
-    def _do_install(self, component: ComponentRef, *, force: bool) -> None:
        from ... import get_speckit_version
        from ..._assets import _locate_bundled_preset

@@ -180,9 +168,7 @@ class _PresetKindManager:
                component.version,
                _bundled_manifest_version(bundled / "preset.yml", "preset"),
            )
-            self._manager.install_from_directory(
-                bundled, speckit_version, priority, **({"force": True} if force else {})
-            )
+            self._manager.install_from_directory(bundled, speckit_version, priority)
            return

        if not self._allow_network:
@@ -208,9 +194,7 @@ class _PresetKindManager:
        )
        zip_path = catalog.download_pack(component.id)
        try:
-            self._manager.install_from_zip(
-                zip_path, speckit_version, priority, **({"force": True} if force else {})
-            )
+            self._manager.install_from_zip(zip_path, speckit_version, priority)
        finally:
            with contextlib.suppress(Exception):
                if zip_path.exists():
@@ -240,12 +224,6 @@ class _ExtensionKindManager:
            return False

    def install(self, component: ComponentRef) -> None:
-        self._do_install(component, force=False)
-
-    def refresh(self, component: ComponentRef) -> None:
-        self._do_install(component, force=True)
-
-    def _do_install(self, component: ComponentRef, *, force: bool) -> None:
        from ... import get_speckit_version
        from ..._assets import _locate_bundled_extension

@@ -264,7 +242,7 @@ class _ExtensionKindManager:
                _bundled_manifest_version(bundled / "extension.yml", "extension"),
            )
            self._manager.install_from_directory(
-                bundled, speckit_version, priority=priority, force=force
+                bundled, speckit_version, priority=priority
            )
            return

@@ -294,7 +272,7 @@ class _ExtensionKindManager:
        zip_path = catalog.download_extension(component.id)
        try:
            self._manager.install_from_zip(
-                zip_path, speckit_version, priority=priority, force=force
+                zip_path, speckit_version, priority=priority
            )
        finally:
            with contextlib.suppress(Exception):
@@ -340,11 +318,6 @@ class _WorkflowKindManager:
                lambda: workflow_add(component.id),
            )

-    def refresh(self, component: ComponentRef) -> None:
-        # workflow_add is idempotent for already-installed workflows; delegate
-        # to the standard install path which handles version refresh correctly.
-        self.install(component)
-
    def _assert_pinned_version(self, component: ComponentRef) -> None:
        if not component.version:
            return
@@ -405,35 +378,6 @@ class _StepKindManager:
                lambda: workflow_step_add(component.id),
            )

-    def refresh(self, component: ComponentRef) -> None:
-        # Preserve an existing step until we've validated we can perform refresh.
-        # For already-installed steps, keep a backup and restore it if the
-        # remove+reinstall path fails.
-        if not (self._allow_network and self.is_installed(component)):
-            self.install(component)
-            return
-
-        import shutil
-        import tempfile
-
-        step_dir = self._registry.steps_dir / component.id
-        metadata = self._registry.get(component.id)
-        backup_dir = Path(tempfile.mkdtemp(prefix="speckit-step-refresh-")) / component.id
-        try:
-            if step_dir.exists():
-                shutil.copytree(step_dir, backup_dir)
-            self.remove(component)
-            try:
-                self.install(component)
-            except BundlerError:
-                if backup_dir.exists():
-                    shutil.copytree(backup_dir, step_dir, dirs_exist_ok=True)
-                if metadata is not None and not self._registry.is_installed(component.id):
-                    self._registry.add(component.id, metadata)
-                raise
-        finally:
-            shutil.rmtree(backup_dir.parent, ignore_errors=True)
-
    def remove(self, component: ComponentRef) -> None:
        from ... import workflow_step_remove

@@ -74,13 +74,6 @@ class CatalogStackBase:
        try:
            parsed = urlparse(url)
            hostname = parsed.hostname
-            # Accessing ``port`` performs urllib's syntax/range validation;
-            # ``hostname`` alone does not, so a non-numeric or out-of-range
-            # port would otherwise pass validation here and only fail later,
-            # at fetch time, as an error this module does not translate --
-            # a raw http.client.InvalidURL for a non-numeric port, and a
-            # socket-layer failure for one that is merely out of range.
-            _ = parsed.port
        except ValueError:
            raise cls._error(f"Catalog URL is malformed: {url}") from None
        is_localhost = hostname in ("localhost", "127.0.0.1", "::1")
@@ -12,10 +12,8 @@ import re
 from pathlib import Path

 import typer
-from rich.markup import escape as _escape_markup

 from ..._console import console, err_console
-from ..._download_security import MAX_DOWNLOAD_BYTES, read_response_limited
 from ...bundler import BundlerError
 from ...bundler.lib.project import (
    active_integration,
@@ -119,8 +117,6 @@ def _run_init(integration: str, *, script_type: str, offline: bool = False) -> N
            preset=None,
            integration=integration,
            integration_options=None,
-            extensions=None,
-            trust_extension_urls=False,
        )
    except typer.Exit as exc:
        if exc.exit_code:
@@ -131,13 +127,13 @@ def _run_init(integration: str, *, script_type: str, offline: bool = False) -> N

 def _resolve_init_integration(override: str | None, manifest) -> str:
    """Precedence (FR-013): explicit override → bundle-declared → default."""
-    from ..._agent_config import resolve_default_init_integration
+    from ..._agent_config import DEFAULT_INIT_INTEGRATION

    if override:
        return override
    if manifest is not None and manifest.integration is not None:
        return manifest.integration.id
-    return resolve_default_init_integration()
+    return DEFAULT_INIT_INTEGRATION


 # ===== Consume =====
@@ -188,16 +184,11 @@ def bundle_search(
            else ""
        )
        console.print(
-            f"  [bold]{_escape_markup(str(r.entry.id))}[/bold] "
-            f"v{_escape_markup(str(r.entry.version))} — "
-            f"{_escape_markup(str(r.entry.name))} "
-            f"[dim]({_escape_markup(str(r.entry.role))})[/dim] "
-            f"{_trust_badge(r.entry.verified)} {policy}"
-        )
-        console.print(f"    {_escape_markup(str(r.entry.description))}")
-        console.print(
-            f"    [dim]source: {_escape_markup(str(r.source.id))}[/dim]"
+            f"  [bold]{r.entry.id}[/bold] v{r.entry.version} — {r.entry.name} "
+            f"[dim]({r.entry.role})[/dim] {_trust_badge(r.entry.verified)} {policy}"
        )
+        console.print(f"    {r.entry.description}")
+        console.print(f"    [dim]source: {r.source.id}[/dim]")


@bundle_app.command("info")
@@ -250,31 +241,16 @@ def bundle_info(
        print(_json.dumps(payload, indent=2))
        return

-    console.print(
-        f"\n[bold cyan]{_escape_markup(str(entry.id))}[/bold cyan] "
-        f"v{_escape_markup(str(entry.version))} — "
-        f"{_escape_markup(str(entry.name))}"
-    )
-    console.print(f"  Role: {_escape_markup(str(entry.role))}")
-    console.print(f"  {_escape_markup(str(entry.description))}")
-    console.print(
-        f"  Author: {_escape_markup(str(entry.author))}   "
-        f"License: {_escape_markup(str(entry.license))}"
-    )
-    console.print(
-        f"  Source: {_escape_markup(str(resolved.source.id))} "
-        f"({resolved.source.install_policy.value})"
-    )
+    console.print(f"\n[bold cyan]{entry.id}[/bold cyan] v{entry.version} — {entry.name}")
+    console.print(f"  Role: {entry.role}")
+    console.print(f"  {entry.description}")
+    console.print(f"  Author: {entry.author}   License: {entry.license}")
+    console.print(f"  Source: {resolved.source.id} ({resolved.source.install_policy.value})")
    console.print(f"  Trust: {_trust_badge(entry.verified)}")
    if entry.requires_speckit_version:
-        console.print(
-            f"  Requires Spec Kit: "
-            f"{_escape_markup(str(entry.requires_speckit_version))}"
-        )
+        console.print(f"  Requires Spec Kit: {entry.requires_speckit_version}")
    if manifest and manifest.integration:
-        console.print(
-            f"  Integration: {_escape_markup(str(manifest.integration.id))}"
-        )
+        console.print(f"  Integration: {manifest.integration.id}")

    if components:
        console.print("\n  [bold]Components[/bold] (added on install):")
@@ -284,22 +260,18 @@ def bundle_info(
                continue
            console.print(f"    [bold]{kind}:[/bold]")
            for item in items:
-                console.print(
-                    f"      - {_escape_markup(_format_component(item))}"
-                )
+                console.print(f"      - {_format_component(item)}")
    else:
        console.print("\n  [bold]Provides:[/bold]")
        for kind in ("extensions", "presets", "steps", "workflows"):
            count = entry.provides.get(kind, 0)
            if count:
-                console.print(f"    {kind}: {_escape_markup(str(count))}")
+                console.print(f"    {kind}: {count}")

    if overlaps:
        console.print("\n  [yellow]Overlaps with already-installed bundles:[/yellow]")
        for overlap in overlaps:
-            console.print(
-                f"    [yellow]-[/yellow] {_escape_markup(str(overlap))}"
-            )
+            console.print(f"    [yellow]-[/yellow] {overlap}")

    if not resolved.install_allowed:
        console.print(
@@ -365,10 +337,6 @@ def bundle_install(
        local_manifest = _local_manifest_source(bundle_id)
        if local_manifest is not None:
            manifest = local_manifest
-            _validate_manifest_structure(
-                manifest,
-                source=f"Local bundle source {bundle_id!r}",
-            )
        else:
            stack = _build_stack(project_root or Path.cwd(), offline=offline)
            resolved = stack.resolve(bundle_id)
@@ -382,16 +350,6 @@ def bundle_install(

        if project_root is None:
            init_integration = _resolve_init_integration(integration, manifest)
-            # Resolve all hard compatibility gates before ``specify init``.
-            # Otherwise an incompatible but structurally valid bundle would
-            # initialize a project and only then fail its version/integration
-            # checks, leaving state behind after a failed install.
-            resolve_install_plan(
-                manifest,
-                speckit_version=_speckit_version(),
-                active_integration=init_integration,
-                integration_explicit=True,
-            )
            console.print(
                f"[cyan]No Spec Kit project here; initializing with integration "
                f"'{init_integration}'…[/cyan]"
@@ -753,35 +711,18 @@ def _local_manifest_source(arg: str):

    if candidate.suffix == ".zip":
        import io
+        import zipfile

        import yaml as _yaml

-        from ..._download_security import open_zip_bounded, read_zip_member_limited
-
-        with open_zip_bounded(candidate, error_type=BundlerError) as archive:
+        with zipfile.ZipFile(candidate) as archive:
            try:
-                archive.getinfo("bundle.yml")
+                raw = archive.read("bundle.yml")
            except KeyError as exc:
                raise BundlerError(
                    f"Artifact '{candidate}' does not contain a bundle.yml."
                ) from exc
-            raw = read_zip_member_limited(
-                archive,
-                "bundle.yml",
-                error_type=BundlerError,
-                label="bundle manifest",
-            )
-        try:
-            data = _yaml.safe_load(io.BytesIO(raw))
-        except _yaml.YAMLError as exc:
-            # The sibling directory/bundle.yml branches reach YAML through
-            # load_yaml(), which turns a parse failure into a BundlerError. This
-            # branch parses inline, so without this it raises a raw YAMLError --
-            # neither a ValueError nor an OSError -- which escapes
-            # bundle_install()'s `except BundlerError` as a traceback.
-            raise BundlerError(
-                f"Invalid YAML in bundle.yml inside '{candidate}': {exc}"
-            ) from exc
+        data = _yaml.safe_load(io.BytesIO(raw))
        return BundleManifest.from_dict(data)

    if candidate.name == "bundle.yml" or candidate.suffix in (".yml", ".yaml"):
@@ -864,13 +805,7 @@ def _download_manifest(resolved, *, offline: bool):
            f"Network access disabled; cannot download bundle '{resolved.entry.id}' "
            f"from {url}."
        )
-    manifest = _download_remote_manifest(
-        resolved.entry.id,
-        url,
-        expected_sha256=getattr(resolved.entry, "sha256", None),
-    )
-    _validate_catalog_manifest(resolved.entry, manifest)
-    return manifest
+    return _download_remote_manifest(resolved.entry.id, url)


 def _require_https(label: str, url: str) -> None:
@@ -882,8 +817,6 @@ def _require_https(label: str, url: str) -> None:
    try:
        parsed = urlparse(url)
        hostname = parsed.hostname
-        # Accessing ``port`` performs urllib's syntax/range validation.
-        _ = parsed.port
    except ValueError:
        raise BundlerError(
            f"Refusing to download {label}: URL is malformed: {url}"
@@ -897,12 +830,7 @@ def _require_https(label: str, url: str) -> None:
        raise BundlerError(f"Refusing to download {label} from URL with no host: {url}")


-def _download_remote_manifest(
-    entry_id: str,
-    url: str,
-    *,
-    expected_sha256: str | None = None,
-):
+def _download_remote_manifest(entry_id: str, url: str):
    """Fetch a remote bundle artifact over HTTPS and extract its manifest."""
    import io
    import tempfile
@@ -914,7 +842,6 @@ def _download_remote_manifest(
    from ...authentication.http import github_provider_hosts, open_url
    from ..._github_http import resolve_github_release_asset_api_url
    from ...bundler.models.manifest import BundleManifest
-    from ...shared_infra import verify_archive_sha256

    def _validate_redirect(old_url: str, new_url: str) -> None:
        _require_https(f"bundle '{entry_id}'", new_url)
@@ -952,18 +879,7 @@ def _download_remote_manifest(
            extra_headers=extra_headers,
        ) as resp:
            _require_https(f"bundle '{entry_id}'", resp.geturl())
-            raw = read_response_limited(
-                resp,
-                max_bytes=MAX_DOWNLOAD_BYTES,
-                error_type=BundlerError,
-                label=f"bundle '{entry_id}' download",
-            )
-        verify_archive_sha256(
-            raw,
-            expected_sha256,
-            entry_id,
-            BundlerError,
-        )
+            raw = resp.read()
    except BundlerError:
        raise
    except Exception as exc:  # noqa: BLE001
@@ -1024,38 +940,6 @@ def _download_remote_manifest(
        ) from exc


-def _validate_manifest_structure(manifest, *, source: str) -> None:
-    """Reject a malformed manifest before any project mutation can occur."""
-    from ...bundler.services.validator import validate_manifest
-
-    report = validate_manifest(manifest)
-    if report.ok:
-        return
-    raise BundlerError(
-        f"{source} contains an invalid bundle manifest:\n  - "
-        + "\n  - ".join(report.errors)
-    )
-
-
-def _validate_catalog_manifest(entry, manifest) -> None:
-    """Bind a downloaded manifest to the catalog identity that selected it."""
-    if manifest.bundle.id != entry.id:
-        raise BundlerError(
-            f"Downloaded bundle id mismatch: catalog entry {entry.id!r} points to "
-            f"a manifest for {manifest.bundle.id!r}."
-        )
-    if manifest.bundle.version != entry.version:
-        raise BundlerError(
-            f"Downloaded bundle version mismatch for {entry.id!r}: catalog declares "
-            f"{entry.version!r}, but the manifest declares "
-            f"{manifest.bundle.version!r}."
-        )
-    _validate_manifest_structure(
-        manifest,
-        source=f"Downloaded bundle {entry.id!r}",
-    )
-
-
 def register(app: typer.Typer) -> None:
    """Attach the bundle command group to the root Typer app."""
    app.add_typer(bundle_app, name="bundle")
@@ -1,50 +0,0 @@
-"""specify event * command handlers."""
-
-from __future__ import annotations
-
-from pathlib import Path
-import sys
-import typer
-
-event_app = typer.Typer(
-    name="event",
-    help="Manage and execute event-driven commands",
-    add_completion=False,
-)
-
-
-@event_app.command("run")
-def event_run(
-    command_name: str = typer.Argument(..., help="Name of the command to execute"),
-    event_name: str = typer.Argument(..., help="Canonical event name (e.g., session_start)"),
-    timeout: int = typer.Argument(
-        120, help="Per-handler timeout in seconds (passed through from the native hook config)"
-    ),
-):
-    """Resolve and run an event-driven command script with stdin payload."""
-    from ..events import resolve_and_run_event_command
-
-    # Read payload from stdin if available (capped at 1 MiB to prevent DoS).
-    MAX_STDIN_BYTES = 1 * 1024 * 1024
-    if not sys.stdin.isatty():
-        raw = sys.stdin.read(MAX_STDIN_BYTES)
-        if not sys.stdin.eof:
-            raise typer.Exit(
-                code=1,
-                message="stdin payload exceeds 1 MiB limit; "
-                "truncate or pipe a smaller payload",
-            )
-        payload = raw
-    else:
-        payload = "{}"
-
-    # Run the event command
-    project_root = Path.cwd()  # The agent runs events from project root
-    exit_code = resolve_and_run_event_command(
-        command_name, event_name, payload, project_root, timeout=timeout
-    )
-    raise typer.Exit(code=exit_code)
-
-
-def register(app: typer.Typer) -> None:
-    app.add_typer(event_app, name="event")
@@ -3,22 +3,19 @@
 from __future__ import annotations

 import os
-import shlex
 import shutil
-import subprocess
 import sys
 from pathlib import Path
 from typing import Any

 import typer
 from rich.live import Live
-from rich.markup import escape as _escape_markup
 from rich.panel import Panel

 from .._agent_config import (
    AGENT_CONFIG,
+    DEFAULT_INIT_INTEGRATION,
    SCRIPT_TYPE_CHOICES,
-    resolve_default_init_integration,
 )
 from .._assets import (
    _locate_bundled_preset,
@@ -33,164 +30,6 @@ def _stdin_is_interactive() -> bool:
    return sys.stdin.isatty()


-def _ext_spec_is_url(ext_spec: str) -> bool:
-    """Return True when *ext_spec* is an http(s) URL rather than a name/path."""
-    from urllib.parse import urlparse
-
-    try:
-        return urlparse(ext_spec).scheme in ("http", "https")
-    except ValueError:
-        return False
-
-
-def _confirm_extension_url_trust(
-    url_specs: list[str], *, trust_override: bool
-) -> dict[str, bool]:
-    """Resolve trust for each URL-based extension before the Live display.
-
-    URL installs pull an arbitrary external extension, so they get the same
-    default-deny confirmation as ``extension add --from``. Returns a mapping of
-    ``url_spec -> approved``. With *trust_override* every URL is pre-approved.
-    In a non-interactive session without the override, every URL is denied
-    (the prompt cannot be answered), mirroring the default-deny posture.
-    """
-    from rich.markup import escape as _escape_markup
-    from rich.panel import Panel
-
-    approvals: dict[str, bool] = {}
-    interactive = _stdin_is_interactive()
-    for spec in url_specs:
-        if trust_override:
-            approvals[spec] = True
-            continue
-        if not interactive:
-            approvals[spec] = False
-            continue
-        console.print()
-        console.print(
-            Panel(
-                "[bold]You are installing an extension from an external URL that is not\n"
-                "listed in any of your configured extension catalogs.[/bold]\n\n"
-                f"URL: {_escape_markup(spec)}\n\n"
-                "Only install extensions from sources you trust.",
-                title="[bold yellow]⚠ Untrusted Source[/bold yellow]",
-                border_style="yellow",
-                padding=(1, 2),
-            )
-        )
-        console.print()
-        approvals[spec] = typer.confirm(
-            f"Install extension from {spec}?", default=False
-        )
-    return approvals
-
-
-def _install_extension_during_init(project_path: Path, ext_spec: str, speckit_version: str) -> str:
-    """Install a single extension during ``specify init``.
-
-    Handles bundled extension names, local directory paths, and HTTPS URLs.
-    Returns a short status message on success.
-    Raises ``ValueError`` on failure so the caller can convert it to a
-    tracker error without aborting the entire init.
-    """
-    from urllib.parse import urlparse
-
-    from .._assets import _locate_bundled_extension
-    from ..extensions import ExtensionCatalog, ExtensionError, ExtensionManager
-    from ..extensions._commands import (
-        _resolve_catalog_extension,
-        install_extension_from_url,
-    )
-
-    manager = ExtensionManager(project_path)
-
-    # --- URL ---
-    parsed = urlparse(ext_spec)
-    if parsed.scheme in ("http", "https"):
-        try:
-            manifest = install_extension_from_url(
-                manager, project_path, ext_spec, speckit_version
-            )
-        except ExtensionError as exc:
-            raise ValueError(str(exc)) from exc
-        return f"{manifest.name} v{manifest.version} installed"
-
-    # --- Local path ---
-    if ext_spec.startswith(("./", "../", "/", "~/", ".\\", "..\\")) or Path(ext_spec).is_absolute():
-        source_path = Path(ext_spec).expanduser().resolve()
-        if not source_path.exists():
-            raise ValueError(f"Directory not found: {source_path}")
-        if not (source_path / "extension.yml").exists():
-            raise ValueError(f"No extension.yml found in {source_path}")
-        manifest = manager.install_from_directory(source_path, speckit_version)
-        return f"{manifest.name} v{manifest.version} installed"
-
-    # --- Bundled extension name or catalog ID ---
-    bundled_path = _locate_bundled_extension(ext_spec)
-    if bundled_path is not None:
-        if manager.registry.is_installed(ext_spec):
-            return "already installed"
-        manifest = manager.install_from_directory(bundled_path, speckit_version)
-        return f"{manifest.name} v{manifest.version} installed"
-
-    # Fall back to catalog
-    catalog = ExtensionCatalog(project_path)
-    ext_info, catalog_error = _resolve_catalog_extension(ext_spec, catalog, "add")
-    if catalog_error:
-        raise ValueError(f"Could not query extension catalog: {catalog_error}")
-    if not ext_info:
-        raise ValueError(f"Extension '{ext_spec}' not found in bundled extensions or catalog")
-
-    resolved_id = ext_info["id"]
-    if resolved_id != ext_spec:
-        bundled_path = _locate_bundled_extension(resolved_id)
-        if bundled_path is not None:
-            if manager.registry.is_installed(resolved_id):
-                return "already installed"
-            manifest = manager.install_from_directory(bundled_path, speckit_version)
-            return f"{manifest.name} v{manifest.version} installed"
-
-    if ext_info.get("bundled") and not ext_info.get("download_url"):
-        from ..extensions import REINSTALL_COMMAND
-
-        raise ValueError(
-            f"Extension '{resolved_id}' is bundled with spec-kit but not found in the installed package. "
-            f"Try reinstalling spec-kit: {REINSTALL_COMMAND}"
-        )
-
-    if not ext_info.get("_install_allowed", True):
-        catalog_name = ext_info.get("_catalog_name", "community")
-        raise ValueError(
-            f"Extension '{ext_spec}' is in the '{catalog_name}' catalog but installation is not allowed from that catalog"
-        )
-
-    zip_path = catalog.download_extension(resolved_id)
-    try:
-        manifest = manager.install_from_zip(zip_path, speckit_version)
-    finally:
-        zip_path.unlink(missing_ok=True)
-    return f"{manifest.name} v{manifest.version} installed"
-
-
-def _shell_quote_arg(value: str) -> str:
-    """Quote *value* as one argument for the shells of the host OS.
-
-    The Next Steps ``cd`` line is copy-pasted into whichever shell ran
-    ``specify init``, so it is quoted for the host the same way
-    ``_version._render_argv`` renders its copy-pasteable installer command:
-    ``list2cmdline`` on Windows, ``shlex.quote`` elsewhere. The Windows branch
-    must emit double quotes -- ``cd 'my project'`` is a path-not-found in
-    cmd.exe, while ``cd "my project"`` is accepted by cmd.exe, PowerShell and
-    Git Bash alike. A value needing no quoting is returned unchanged.
-
-    Whitespace only. PowerShell also glob-expands ``[``/``]`` and expands
-    ``$``/backtick inside double quotes, so such a name still needs
-    ``Set-Location -LiteralPath`` there -- syntax invalid in cmd.exe and sh, so
-    this shell-neutral line cannot cover it.
-    """
-    return subprocess.list2cmdline([value]) if os.name == "nt" else shlex.quote(value)
-
-
 def ensure_constitution_from_template(
    project_path: Path, tracker: StepTracker | None = None
 ) -> None:
@@ -303,16 +142,6 @@ def register(app: typer.Typer) -> None:
            "--integration-options",
            help='Options for the integration (e.g. --integration-options="--commands-dir .myagent/cmds")',
        ),
-        extensions: list[str] | None = typer.Option(
-            None,
-            "--extension",
-            help="Install an extension during initialization (bundled name, local path, or HTTPS URL). Repeatable.",
-        ),
-        trust_extension_urls: bool = typer.Option(
-            False,
-            "--trust-extension-urls",
-            help="Pre-authorize installing extensions from external URLs without the interactive trust prompt (required for non-interactive URL installs).",
-        ),
    ):
        """
        Initialize a new Specify project.
@@ -345,10 +174,6 @@ def register(app: typer.Typer) -> None:
            specify init --here --integration gemini
            specify init my-project --integration generic --integration-options="--commands-dir .myagent/commands/"  # Bring your own agent; requires --commands-dir
            specify init my-project --integration claude --preset healthcare-compliance  # With preset
-            specify init my-project --integration copilot --extension git  # With bundled extension
-            specify init my-project --extension git --extension selftest  # Multiple extensions
-            specify init my-project --extension ./my-extensions/custom-ext  # Local path extension
-            specify init my-project --extension https://example.com/extensions/my-ext.zip --trust-extension-urls  # URL extension (non-interactive)
        """
        # Lazy imports to avoid circular dependency — __init__.py imports this module
        from .. import (
@@ -358,7 +183,6 @@ def register(app: typer.Typer) -> None:
            save_init_options,
        )
        from ..integration_runtime import (
-            invoke_prefix_for_integration as _invoke_prefix_for_integration,
            with_integration_setting as _with_integration_setting,
        )
        from ..integrations._commands import (
@@ -373,10 +197,7 @@ def register(app: typer.Typer) -> None:
        if integration:
            resolved_integration = get_integration(integration)
            if not resolved_integration:
-                console.print(
-                    f"[red]Error:[/red] Unknown integration: "
-                    f"'{_escape_markup(str(integration))}'"
-                )
+                console.print(f"[red]Error:[/red] Unknown integration: '{integration}'")
                available = ", ".join(sorted(INTEGRATION_REGISTRY))
                console.print(f"[yellow]Available integrations:[/yellow] {available}")
                raise typer.Exit(1)
@@ -453,27 +274,26 @@ def register(app: typer.Typer) -> None:
            project_path = Path(project_name).resolve()
            dir_existed_before = project_path.exists()
            if project_path.exists():
-                safe_name = _escape_markup(str(project_name))
                if not project_path.is_dir():
                    console.print(
-                        f"[red]Error:[/red] '{safe_name}' exists but is not a directory."
+                        f"[red]Error:[/red] '{project_name}' exists but is not a directory."
                    )
                    raise typer.Exit(1)
                existing_items = list(project_path.iterdir())
                if force:
                    if existing_items:
                        console.print(
-                            f"[yellow]Warning:[/yellow] Directory '{safe_name}' is not empty ({len(existing_items)} items)"
+                            f"[yellow]Warning:[/yellow] Directory '{project_name}' is not empty ({len(existing_items)} items)"
                        )
                        console.print(
                            "[yellow]Template files will be merged with existing content and may overwrite existing files[/yellow]"
                        )
                    console.print(
-                        f"[cyan]--force supplied: merging into existing directory '[cyan]{safe_name}[/cyan]'[/cyan]"
+                        f"[cyan]--force supplied: merging into existing directory '[cyan]{project_name}[/cyan]'[/cyan]"
                    )
                else:
                    error_panel = Panel(
-                        f"Directory already exists: '[cyan]{safe_name}[/cyan]'\n"
+                        f"Directory already exists: '[cyan]{project_name}[/cyan]'\n"
                        "Please choose a different project name or remove the existing directory.\n"
                        "Use [bold]--force[/bold] to merge into the existing directory.",
                        title="[red]Directory Conflict[/red]",
@@ -487,23 +307,22 @@ def register(app: typer.Typer) -> None:
        if integration:
            if integration not in AGENT_CONFIG:
                console.print(
-                    f"[red]Error:[/red] Invalid integration '{_escape_markup(str(integration))}'. Choose from: {', '.join(AGENT_CONFIG.keys())}"
+                    f"[red]Error:[/red] Invalid integration '{integration}'. Choose from: {', '.join(AGENT_CONFIG.keys())}"
                )
                raise typer.Exit(1)
            selected_ai = integration
        elif not _stdin_is_interactive():
-            default_integration = resolve_default_init_integration()
            console.print(
-                f"[dim]Non-interactive session detected: defaulting to '{default_integration}'. "
+                f"[dim]Non-interactive session detected: defaulting to '{DEFAULT_INIT_INTEGRATION}'. "
                "Use --integration to choose a different agent.[/dim]"
            )
-            selected_ai = default_integration
+            selected_ai = DEFAULT_INIT_INTEGRATION
        else:
            ai_choices = {key: config["name"] for key, config in AGENT_CONFIG.items()}
            selected_ai = select_with_arrows(
                ai_choices,
                "Choose your coding agent integration:",
-                resolve_default_init_integration(),
+                DEFAULT_INIT_INTEGRATION,
            )

        if not integration:
@@ -526,14 +345,12 @@ def register(app: typer.Typer) -> None:
        setup_lines = [
            "[cyan]Specify Project Setup[/cyan]",
            "",
-            f"{'Project':<15} [green]{_escape_markup(project_path.name)}[/green]",
-            f"{'Working Path':<15} [dim]{_escape_markup(str(current_dir))}[/dim]",
+            f"{'Project':<15} [green]{project_path.name}[/green]",
+            f"{'Working Path':<15} [dim]{current_dir}[/dim]",
        ]

        if not here:
-            setup_lines.append(
-                f"{'Target Path':<15} [dim]{_escape_markup(str(project_path))}[/dim]"
-            )
+            setup_lines.append(f"{'Target Path':<15} [dim]{project_path}[/dim]")

        console.print(
            Panel("\n".join(setup_lines), border_style="cyan", padding=(1, 2))
@@ -560,7 +377,7 @@ def register(app: typer.Typer) -> None:
        if script_type:
            if script_type not in SCRIPT_TYPE_CHOICES:
                console.print(
-                    f"[red]Error:[/red] Invalid script type '{_escape_markup(str(script_type))}'. Choose from: {', '.join(SCRIPT_TYPE_CHOICES.keys())}"
+                    f"[red]Error:[/red] Invalid script type '{script_type}'. Choose from: {', '.join(SCRIPT_TYPE_CHOICES.keys())}"
                )
                raise typer.Exit(1)
            selected_script = script_type
@@ -595,29 +412,10 @@ def register(app: typer.Typer) -> None:
            ("chmod", "Ensure scripts executable"),
            ("constitution", "Constitution setup"),
            ("workflow", "Install bundled workflow"),
+            ("final", "Finalize"),
        ]:
            tracker.add(key, label)

-        if extensions:
-            for i, ext_spec in enumerate(extensions):
-                tracker.add(
-                    f"extension-{i}", f"Install extension: {_escape_markup(ext_spec)}"
-                )
-
-        tracker.add("final", "Finalize")
-
-        # Resolve trust for URL-based extensions BEFORE entering the Live
-        # display: the confirmation prompt cannot be shown/answered underneath
-        # the Rich Live spinner. URL installs are default-deny unless the user
-        # confirms interactively or passes --trust-extension-urls.
-        extension_url_approvals: dict[str, bool] = {}
-        if extensions:
-            url_specs = [e for e in extensions if _ext_spec_is_url(e)]
-            if url_specs:
-                extension_url_approvals = _confirm_extension_url_trust(
-                    url_specs, trust_override=trust_extension_urls
-                )
-
        # Disable transient mode on Windows: PowerShell 5.1's legacy console
        # hangs when Rich tries to restore cursor state via VT escape sequences.
        _transient = sys.platform != "win32"
@@ -644,47 +442,15 @@ def register(app: typer.Typer) -> None:
                    if extra:
                        integration_parsed_options.update(extra)

-                from ..events import resolve_events
-                events_map = resolve_events(
-                    resolved_integration.key,
-                    resolved_integration.config,
-                    project_path,
-                    integration_parsed_options or None,
-                )
                resolved_integration.setup(
                    project_path,
                    manifest,
                    parsed_options=integration_parsed_options or None,
                    script_type=selected_script,
                    raw_options=integration_options,
-                    events=events_map,
                )
                manifest.save()

-                if force:
-                    from ..integrations._helpers import (
-                        _register_extensions_for_agent,
-                        _register_presets_for_agent,
-                    )
-
-                    _register_extensions_for_agent(
-                        project_path,
-                        resolved_integration.key,
-                        force=True,
-                        continuing=(
-                            "The project was re-initialized, but installed extensions"
-                            " may need re-registration."
-                        ),
-                    )
-                    _register_presets_for_agent(
-                        project_path,
-                        resolved_integration.key,
-                        continuing=(
-                            "The project was re-initialized, but installed presets"
-                            " may need re-registration."
-                        ),
-                    )
-
                integration_settings = _with_integration_setting(
                    {},
                    resolved_integration.key,
@@ -715,12 +481,6 @@ def register(app: typer.Typer) -> None:
                    invoke_separator=resolved_integration.effective_invoke_separator(
                        integration_parsed_options, project_root=project_path
                    ),
-                    invoke_prefix=_invoke_prefix_for_integration(
-                        resolved_integration,
-                        resolved_integration.key,
-                        integration_parsed_options,
-                        project_path,
-                    ),
                )
                tracker.complete(
                    "shared-infra", f"scripts ({selected_script}) + templates"
@@ -851,44 +611,6 @@ def register(app: typer.Typer) -> None:
                            continuing="Continuing without the optional preset.",
                        )

-                # Install extensions specified via --extension
-                if extensions:
-                    from ..extensions._commands import _refresh_events_and_warn
-
-                    speckit_ver = get_speckit_version()
-                    any_extension_installed = False
-                    for i, ext_spec in enumerate(extensions):
-                        tracker.start(f"extension-{i}")
-                        # Skip URL extensions the user did not confirm as trusted
-                        # (default-deny; resolved before the Live display).
-                        if _ext_spec_is_url(ext_spec) and not extension_url_approvals.get(
-                            ext_spec, False
-                        ):
-                            tracker.error(
-                                f"extension-{i}",
-                                "skipped: untrusted URL not confirmed "
-                                "(use --trust-extension-urls)",
-                            )
-                            continue
-                        try:
-                            status_msg = _install_extension_during_init(
-                                project_path, ext_spec, speckit_ver
-                            )
-                            tracker.complete(f"extension-{i}", status_msg)
-                            any_extension_installed = True
-                        except Exception as ext_err:
-                            sanitized_ext = str(ext_err).replace("\n", " ").strip()
-                            tracker.error(
-                                f"extension-{i}",
-                                f"failed: {_escape_markup(sanitized_ext[:120])}",
-                            )
-
-                    # Refresh native event configuration once after the batch so
-                    # that an extension declaring ``events:`` has its hooks
-                    # activated, mirroring the ``extension add`` path.
-                    if any_extension_installed:
-                        _refresh_events_and_warn(project_path)
-
                # Seed the constitution AFTER preset installation so that a
                # preset-provided constitution-template (resolved via the
                # priority stack) wins over the core template.
@@ -942,7 +664,7 @@ def register(app: typer.Typer) -> None:
            if agent_folder:
                security_notice = Panel(
                    f"Some agents may store credentials, auth tokens, or other identifying and private artifacts in the agent folder within your project.\n"
-                    f"Consider adding [cyan]{_escape_markup(str(agent_folder))}[/cyan] (or parts of it) to [cyan].gitignore[/cyan] to prevent accidental credential leakage.",
+                    f"Consider adding [cyan]{agent_folder}[/cyan] (or parts of it) to [cyan].gitignore[/cyan] to prevent accidental credential leakage.",
                    title="[yellow]Agent Folder Security[/yellow]",
                    border_style="yellow",
                    padding=(1, 2),
@@ -953,7 +675,7 @@ def register(app: typer.Typer) -> None:
        steps_lines = []
        if not here:
            steps_lines.append(
-                f"1. Go to the project folder: [cyan]cd {_escape_markup(_shell_quote_arg(str(project_name)))}[/cyan]"
+                f"1. Go to the project folder: [cyan]cd {project_name}[/cyan]"
            )
            step_num = 2
        else:
@@ -5,7 +5,6 @@ from __future__ import annotations
 from collections.abc import Callable
 from typing import Any

-from ._invocation_style import get_invocation_prefix
 from .integration_state import integration_setting, integration_settings


@@ -70,8 +69,8 @@ def with_integration_setting(
    # ``script_type`` changes (``parsed_options`` and ``raw_options`` both
    # None), the previously-stored ``parsed_options`` are retained above, so
    # deriving the separator from the argument (None) would drop an
-    # options-dependent separator (e.g. Copilot ``--commands`` -> ".") back to
-    # the default "-".
+    # options-dependent separator (e.g. Copilot ``--skills`` -> "-") back to
+    # the default ".".
    current["invoke_separator"] = integration.effective_invoke_separator(
        current.get("parsed_options"), project_root
    )
@@ -100,14 +99,3 @@ def invoke_separator_for_integration(
        return integration.effective_invoke_separator(stored_parsed, project_root)

    return integration.effective_invoke_separator(None, project_root)
-
-
-def invoke_prefix_for_integration(
-    integration: Any,
-    key: str,
-    parsed_options: dict[str, Any] | None = None,
-    project_root: Any = None,
-) -> str:
-    """Resolve the native invocation prefix for an integration's output mode."""
-    skills_mode = integration.is_skills_mode(parsed_options, project_root)
-    return get_invocation_prefix(key, skills_mode)
@@ -48,7 +48,6 @@ def _register_builtins() -> None:
    """
    # -- Imports (alphabetical) -------------------------------------------
    from .agy import AgyIntegration
-    from .alquimia import AlquimiaAIIntegration
    from .amp import AmpIntegration
    from .auggie import AuggieIntegration
    from .bob import BobIntegration
@@ -87,7 +86,6 @@ def _register_builtins() -> None:

    # -- Registration (alphabetical) --------------------------------------
    _register(AgyIntegration())
-    _register(AlquimiaAIIntegration())
    _register(AmpIntegration())
    _register(AuggieIntegration())
    _register(BobIntegration())
@@ -11,7 +11,6 @@ from rich.markup import escape
 from .._agent_config import SCRIPT_TYPE_CHOICES
 from .._console import console
 from ..integration_runtime import (
-    invoke_prefix_for_integration as _invoke_prefix_for_integration,
    invoke_separator_for_integration as _invoke_separator_for_integration,
    resolve_integration_options as _resolve_integration_options_impl,
    with_integration_setting as _with_integration_setting,
@@ -121,7 +120,8 @@ def _clear_init_options_for_integration(project_root: Path, integration_key: str
 def _remove_integration_json(project_root: Path) -> None:
    """Remove ``.specify/integration.json`` if it exists."""
    path = project_root / INTEGRATION_JSON
-    path.unlink(missing_ok=True)
+    if path.exists():
+        path.unlink()


 # ---------------------------------------------------------------------------
@@ -333,9 +333,6 @@ def _set_default_integration(
                    integration, {"integration_settings": settings}, key, parsed_options,
                    project_root=project_root,
                ),
-                invoke_prefix=_invoke_prefix_for_integration(
-                    integration, key, parsed_options, project_root
-                ),
                force=refresh_templates_force,
                refresh_managed=True,
                refresh_hint=refresh_hint,
@@ -394,24 +391,23 @@ def _register_extensions_for_agent(
    agent_key: str,
    *,
    continuing: str,
-    force: bool = False,
 ) -> None:
    """Register all enabled extensions' commands/skills for ``agent_key``.

    ``use`` / ``switch`` re-register enabled extensions for the agent they
-    activate (rescaffold); ``upgrade`` does so only for the *active*
-    integration. Plain ``install`` and upgrade of a non-active integration
-    deliberately skip this helper so a secondary integration has no extension
-    side effects until it is selected. See issues #2886 and #2948.
+    activate; ``upgrade`` backfills them for the refreshed agent. Plain
+    ``install`` deliberately does not call this helper so adding a secondary
+    integration has no extension side effects until it is selected or upgraded.
+    See issue #2886.

-    Callers always pass the active agent (use/switch activate the target
-    before registering), so extension *skill* rendering — which is scoped to
-    the active ``ai`` / ``ai_skills`` init-options — matches ``agent_key``.
-
-    When ``force=True``, existing skill files are overwritten even when they
-    are not dev-mode symlinks. Pass ``force=True`` in the upgrade path so that
-    extension content is layered on top of the core-template files that
-    ``setup()`` just regenerated (fixes the skip-guard bug for skills mode).
+    Known limitation: extension *skill* rendering is scoped to the active
+    agent (init-options track a single ``ai`` / ``ai_skills`` pair). A
+    skills-mode agent registered while it is *not* the active agent (e.g.
+    Copilot ``--skills`` registered while non-active) therefore
+    receives command files rather than skills here — matching ``extension
+    add``'s multi-agent behavior. ``use`` / ``switch`` avoid this because they
+    make the target the active agent first. Per-agent skills parity is tracked in
+    #2948.

    Best-effort: never aborts the surrounding integration operation. Callers
    invoke it *after* the use/upgrade/switch transaction has committed so a
@@ -420,7 +416,7 @@ def _register_extensions_for_agent(
    _best_effort_extension_op(
        project_root,
        agent_key,
-        lambda mgr, key: mgr.register_enabled_extensions_for_agent(key, force=force),
+        lambda mgr, key: mgr.register_enabled_extensions_for_agent(key),
        phase="register extension artifacts for",
        continuing=continuing,
    )
@@ -447,91 +443,6 @@ def _unregister_extensions_for_agent(
    )


-def _register_presets_for_agent(
-    project_root: Path,
-    agent_key: str,
-    *,
-    continuing: str,
-) -> None:
-    """Register all enabled presets' command overrides/skills for ``agent_key``.
-
-    Presets follow the same single-active rule as extensions (#2948):
-    ``use`` / ``switch`` re-register enabled presets for the agent they
-    activate (rescaffold), so a preset installed while a different
-    integration was active is not left targeting that inactive integration.
-
-    Best-effort: never aborts the surrounding integration operation.
-    """
-    try:
-        from ..presets import PresetManager
-
-        preset_mgr = PresetManager(project_root)
-        preset_mgr.register_enabled_presets_for_agent(agent_key)
-    except Exception as preset_err:
-        from .. import _print_cli_warning
-
-        _print_cli_warning(
-            "register preset artifacts for",
-            "integration",
-            agent_key,
-            preset_err,
-            continuing=continuing,
-        )
-
-
-def _unregister_presets_for_agent(
-    project_root: Path,
-    agent_key: str,
-    *,
-    continuing: str,
-) -> None:
-    """Best-effort removal of ``agent_key``'s preset command/skill artifacts.
-
-    Mirrors ``_unregister_extensions_for_agent``: used by ``switch`` when
-    uninstalling the previous integration so its preset command overrides
-    and skill mirrors don't linger as orphans in the old agent's directory
-    once a different (possibly not-yet-installed) integration becomes
-    active (#2948).
-
-    Best-effort: never aborts the surrounding integration operation.
-    """
-    try:
-        from ..presets import PresetManager
-
-        preset_mgr = PresetManager(project_root)
-        preset_mgr.unregister_agent_artifacts(agent_key)
-    except Exception as preset_err:
-        from .. import _print_cli_warning
-
-        _print_cli_warning(
-            "clean up preset artifacts for",
-            "integration",
-            agent_key,
-            preset_err,
-            continuing=continuing,
-        )
-
-
-def _unregister_enabled_extension_commands_for_agent(
-    project_root: Path,
-    agent_key: str,
-    *,
-    continuing: str,
-) -> None:
-    """Best-effort removal of enabled extension command artifacts for ``agent_key``."""
-    _best_effort_extension_op(
-        project_root,
-        agent_key,
-        lambda mgr, key: mgr.unregister_agent_artifacts(
-            key,
-            enabled_only=True,
-            commands_only=True,
-        ),
-        phase="clean up enabled extension command artifacts for",
-        continuing=continuing,
-    )
-
-
 # ---------------------------------------------------------------------------
 # CLI formatting helpers (re-exported from _commands.py)
 # ---------------------------------------------------------------------------
@@ -8,7 +8,6 @@ import typer
 from .._console import console
 from .._utils import _display_project_path
 from ..integration_runtime import (
-    invoke_prefix_for_integration as _invoke_prefix_for_integration,
    invoke_separator_for_integration as _invoke_separator_for_integration,
    with_integration_setting as _with_integration_setting,
 )
@@ -131,9 +130,6 @@ def integration_install(
            infra_integration, current, infra_key, infra_parsed,
            project_root=project_root,
        ),
-        invoke_prefix=_invoke_prefix_for_integration(
-            infra_integration, infra_key, infra_parsed, project_root
-        ),
    )
    if os.name != "nt":
        from .. import ensure_executable_scripts
@@ -143,21 +139,12 @@ def integration_install(
        integration.key, project_root, version=_get_speckit_version()
    )

-    from ..events import resolve_events
-    events_map = resolve_events(
-        integration.key,
-        integration.config,
-        project_root,
-        parsed_options,
-    )
-
    try:
        integration.setup(
            project_root, manifest,
            parsed_options=parsed_options,
            script_type=selected_script,
            raw_options=raw_options,
-            events=events_map,
        )
        manifest.save()
        new_installed = _dedupe_integration_keys([*installed_keys, integration.key])
@@ -9,7 +9,6 @@ import typer

 from .._console import console
 from ..integration_runtime import (
-    invoke_prefix_for_integration as _invoke_prefix_for_integration,
    invoke_separator_for_integration as _invoke_separator_for_integration,
    with_integration_setting as _with_integration_setting,
 )
@@ -30,16 +29,13 @@ from ._helpers import (
    _read_integration_json,
    _refresh_init_options_speckit_version,
    _register_extensions_for_agent,
-    _register_presets_for_agent,
    _remove_integration_json,
    _resolve_integration_options,
    _resolve_integration_script_type,
    _resolve_script_type,
    _set_default_integration,
    _set_default_integration_or_exit,
-    _unregister_enabled_extension_commands_for_agent,
    _unregister_extensions_for_agent,
-    _unregister_presets_for_agent,
    _update_init_options_for_integration,
    _write_integration_json,
 )
@@ -58,66 +54,6 @@ def _manifest_tracks_skill_layout(manifest) -> bool:
    return any(str(rel).endswith("/SKILL.md") for rel in manifest.files)


-def _manifest_path_under(rel_path: str, root: str) -> bool:
-    """Return True when manifest key *rel_path* is inside project-relative *root*."""
-    normalized_root = PurePath(root).as_posix().strip("/")
-    normalized_rel = PurePath(rel_path).as_posix().strip("/")
-    if not normalized_root:
-        return False
-    return normalized_rel == normalized_root or normalized_rel.startswith(
-        f"{normalized_root}/"
-    )
-
-
-def _legacy_command_root_changed(
-    integration,
-    project_root: Path,
-    old_manifest,
-    new_manifest,
-) -> bool:
-    """Return True when command artifacts moved from legacy_dir to canonical dir."""
-    config = integration.registrar_config or {}
-    canonical = config.get("dir")
-    legacy = config.get("legacy_dir")
-    if (
-        not isinstance(canonical, str)
-        or not canonical.strip()
-        or not isinstance(legacy, str)
-        or not legacy.strip()
-        or PurePath(canonical).as_posix() == PurePath(legacy).as_posix()
-    ):
-        return False
-
-    canonical_dir = project_root / canonical
-    legacy_dir = project_root / legacy
-    if not canonical_dir.is_dir() or not legacy_dir.is_dir():
-        return False
-
-    old_had_legacy = any(
-        _manifest_path_under(rel, legacy) for rel in old_manifest.files
-    )
-    new_has_canonical = any(
-        _manifest_path_under(rel, canonical) for rel in new_manifest.files
-    )
-    return old_had_legacy and new_has_canonical
-
-
-def _legacy_command_root_upgrade_pending(integration, old_manifest) -> bool:
-    """Return True when the old manifest tracks command files under legacy_dir."""
-    config = integration.registrar_config or {}
-    canonical = config.get("dir")
-    legacy = config.get("legacy_dir")
-    if (
-        not isinstance(canonical, str)
-        or not canonical.strip()
-        or not isinstance(legacy, str)
-        or not legacy.strip()
-        or PurePath(canonical).as_posix() == PurePath(legacy).as_posix()
-    ):
-        return False
-    return any(_manifest_path_under(rel, legacy) for rel in old_manifest.files)
-
-
 class _PresetRegistryUnreadableError(Exception):
    """Raised when an existing preset registry cannot be read or parsed.

@@ -128,21 +64,16 @@ class _PresetRegistryUnreadableError(Exception):
    """


-def _installed_presets_affecting_agent(
-    project_root,
-    agent_key: str,
-    *,
-    include_skills: bool = True,
-) -> list[str]:
+def _installed_presets_affecting_agent(project_root, agent_key: str) -> list[str]:
    """Return IDs of installed presets with artifacts registered for *agent_key*.

-    Preset registration is active-agent-only (#2948): command overrides are
-    written for the active non-skills agent and skills for the active skills
-    agent, tracked per preset in ``registered_commands`` /
-    ``registered_skills``. Entries for *other* agents may still exist from
-    when those agents were active. Callers use this to reject command-root or
-    command↔skills layout migrations before mutation: preset rescaffolding is
-    best-effort and cannot guarantee every tracked artifact has a replacement.
+    Presets register command overrides for every detected agent and mirror
+    skills for the active skills agent, tracking the result in each preset's
+    ``registered_commands`` / ``registered_skills`` metadata. There is no
+    agent-scoped preset re-registration mechanism, so a command↔skills *layout
+    change* cannot reconcile those artifacts (see ``integration_upgrade``).
+    Callers use this to detect the unsafe case and reject the migration rather
+    than silently orphaning preset files / leaving stale registry entries.

    Fails **closed**: a genuinely absent registry (no presets ever installed)
    returns an empty list, but if the registry file exists and cannot be read
@@ -181,53 +112,22 @@ def _installed_presets_affecting_agent(
                f"preset '{preset_id}' entry is malformed"
            )
        registered_commands = meta.get("registered_commands", {})
-        if not isinstance(registered_commands, dict) or not all(
-            isinstance(names, list) for names in registered_commands.values()
-        ):
+        if not isinstance(registered_commands, dict):
            raise _PresetRegistryUnreadableError(
                f"preset '{preset_id}' registered_commands is malformed"
            )
        registered_skills = meta.get("registered_skills", [])
-        if isinstance(registered_skills, dict):
-            # Per-agent provenance ({agent: [skill names]}): only entries for
-            # *this* agent make the preset affect it. Values must be lists —
-            # anything else (e.g. null) leaves ownership undecidable, so fail
-            # closed rather than read it as "no artifacts".
-            if not all(
-                isinstance(names, list) for names in registered_skills.values()
-            ):
-                raise _PresetRegistryUnreadableError(
-                    f"preset '{preset_id}' registered_skills is malformed"
-                )
-            has_skills = include_skills and bool(
-                registered_skills.get(agent_key)
-            )
-        elif isinstance(registered_skills, (list, tuple)):
-            # Legacy flat list: not agent-scoped, so any recorded skill may
-            # belong to this agent — fail closed and count it as affecting.
-            has_skills = include_skills and bool(registered_skills)
-        else:
+        if not isinstance(registered_skills, (list, tuple)):
            raise _PresetRegistryUnreadableError(
                f"preset '{preset_id}' registered_skills is malformed"
            )
        has_commands = bool(registered_commands.get(agent_key))
+        has_skills = bool(registered_skills)
        if has_commands or has_skills:
            affected.append(preset_id)
    return affected


-def _installed_command_presets_affecting_agent(
-    project_root,
-    agent_key: str,
-) -> list[str]:
-    """Return installed presets with command artifacts registered for *agent_key*."""
-    return _installed_presets_affecting_agent(
-        project_root,
-        agent_key,
-        include_skills=False,
-    )
-
-
@integration_app.command("switch")
 def integration_switch(
    target: str = typer.Argument(help="Integration key to switch to"),
@@ -318,27 +218,11 @@ def integration_switch(
                "need re-registration."
            ),
        )
-        _register_presets_for_agent(
-            project_root,
-            target,
-            continuing=(
-                "The integration switch succeeded, but installed presets may "
-                "need re-registration."
-            ),
-        )
        console.print(f"\n[green]✓[/green] Default integration set to [bold]{target}[/bold].")
        raise typer.Exit(0)

    selected_script = _resolve_script_type(project_root, script)

-    # Resolve and validate target options before uninstalling the current
-    # integration. Invalid options must not leave the project partially
-    # switched with the previous integration already removed.
-    target_raw_options, target_parsed_options = _resolve_integration_options(
-        target_integration, current, target, integration_options
-    )
-    target_integration.is_skills_mode(target_parsed_options, project_root)
-
    # Phase 1: Uninstall current integration (if any)
    if installed_key:
        current_integration = get_integration(installed_key)
@@ -391,19 +275,6 @@ def integration_switch(
            continuing="Continuing with integration switch; old extension artifacts may need manual cleanup.",
        )

-        # Unregister preset commands/skills for the old agent for the same
-        # reason: without this, a preset's command overrides (including
-        # custom preset commands) and skill mirrors rendered for
-        # installed_key would remain orphaned in its directory once a
-        # different, possibly not-yet-installed integration becomes active
-        # (#2948). Scoped strictly to installed_key; other agents' files,
-        # tracking, and the preset packs themselves are untouched.
-        _unregister_presets_for_agent(
-            project_root,
-            installed_key,
-            continuing="Continuing with integration switch; old preset artifacts may need manual cleanup.",
-        )
-
        # Clear metadata so a failed Phase 2 doesn't leave stale references
        installed_keys = [installed for installed in installed_keys if installed != installed_key]
        _clear_init_options_for_integration(project_root, installed_key)
@@ -411,10 +282,7 @@ def integration_switch(
            fallback_key = installed_keys[0]
            fallback_integration = get_integration(fallback_key)
            if fallback_integration is not None:
-                (
-                    fallback_raw_options,
-                    fallback_parsed_options,
-                ) = _resolve_integration_options(
+                raw_options, parsed_options = _resolve_integration_options(
                    fallback_integration, current, fallback_key, None
                )
                _set_default_integration_or_exit(
@@ -423,8 +291,8 @@ def integration_switch(
                    fallback_key,
                    fallback_integration,
                    installed_keys,
-                    raw_options=fallback_raw_options,
-                    parsed_options=fallback_parsed_options,
+                    raw_options=raw_options,
+                    parsed_options=parsed_options,
                )
            else:
                _write_integration_json(
@@ -434,6 +302,13 @@ def integration_switch(
            _remove_integration_json(project_root)
        current = _read_integration_json(project_root)

+    # Build parsed options from --integration-options so the integration
+    # can determine its effective invoke separator before shared infra
+    # is installed.
+    raw_options, parsed_options = _resolve_integration_options(
+        target_integration, current, target, integration_options
+    )
+
    # Refresh shared infrastructure to the current CLI version. Switching
    # integrations is exactly when stale vendored shared scripts (e.g.
    # update-agent-context.sh that pre-dates the target integration's
@@ -449,12 +324,9 @@ def integration_switch(
        force=refresh_shared_infra,
        refresh_managed=True,
        invoke_separator=_invoke_separator_for_integration(
-            target_integration, current, target, target_parsed_options,
+            target_integration, current, target, parsed_options,
            project_root=project_root,
        ),
-        invoke_prefix=_invoke_prefix_for_integration(
-            target_integration, target, target_parsed_options, project_root
-        ),
        refresh_hint=(
            "To overwrite customizations, re-run with "
            "[cyan]specify integration switch ... --refresh-shared-infra[/cyan]."
@@ -470,20 +342,12 @@ def integration_switch(
        target_integration.key, project_root, version=_get_speckit_version()
    )

-    from ..events import resolve_events
-    events_map = resolve_events(
-        target_integration.key,
-        target_integration.config,
-        project_root,
-        target_parsed_options,
-    )
    try:
        target_integration.setup(
            project_root, manifest,
-            parsed_options=target_parsed_options,
+            parsed_options=parsed_options,
            script_type=selected_script,
-            raw_options=target_raw_options,
-            events=events_map,
+            raw_options=raw_options,
        )
        manifest.save()
        _set_default_integration(
@@ -493,8 +357,8 @@ def integration_switch(
            target_integration,
            _dedupe_integration_keys([*installed_keys, target_integration.key]),
            script_type=selected_script,
-            raw_options=target_raw_options,
-            parsed_options=target_parsed_options,
+            raw_options=raw_options,
+            parsed_options=parsed_options,
        )

    except Exception as exc:
@@ -532,24 +396,6 @@ def integration_switch(
                        f"[yellow]Warning:[/yellow] Failed to restore default "
                        f"integration '{fallback_key}': {restore_err}"
                    )
-                else:
-                    # Under active-only registration the fallback may never
-                    # have received any extension/preset artifacts (it was
-                    # installed while another integration was active), and
-                    # Phase 1 already unregistered the outgoing agent's
-                    # artifacts. Rescaffold so the restored default is
-                    # actually usable. Both helpers are best-effort and
-                    # cannot raise past this point.
-                    _register_extensions_for_agent(
-                        project_root,
-                        fallback_key,
-                        continuing="The switch was rolled back; installed extensions may need re-registration.",
-                    )
-                    _register_presets_for_agent(
-                        project_root,
-                        fallback_key,
-                        continuing="The switch was rolled back; installed presets may need re-registration.",
-                    )
            else:
                _write_integration_json(
                    project_root, fallback_key, installed_keys, _integration_settings(current)
@@ -570,11 +416,6 @@ def integration_switch(
        target,
        continuing="The integration switch succeeded, but installed extensions may need re-registration.",
    )
-    _register_presets_for_agent(
-        project_root,
-        target,
-        continuing="The integration switch succeeded, but installed presets may need re-registration.",
-    )

    name = (target_integration.config or {}).get("name", target)
    console.print(f"\n[green]✓[/green] Switched to integration '{name}'")
@@ -646,65 +487,18 @@ def integration_upgrade(
        integration, current, key, integration_options
    )

-    legacy_command_root_upgrade_pending = _legacy_command_root_upgrade_pending(
-        integration,
-        old_manifest,
-    )
-
-    # Guard: Kilo's legacy command root moves from .kilocode/workflows to
-    # .kilo/commands. Preset command artifacts are tracked outside the
-    # integration manifest, and their agent-scoped rescaffold is best-effort,
-    # not transactional with command-root cleanup. Refuse before setup writes
-    # .kilo/commands rather than risking orphaned legacy files or missing
-    # registry-tracked overrides in the canonical directory.
-    if key == "kilocode" and legacy_command_root_upgrade_pending:
-        config = integration.registrar_config or {}
-        legacy = config.get("legacy_dir", "legacy command directory")
-        canonical = config.get("dir", "canonical command directory")
-        try:
-            affected_presets = _installed_command_presets_affecting_agent(
-                project_root,
-                key,
-            )
-        except _PresetRegistryUnreadableError as exc:
-            console.print(
-                f"[red]Error:[/red] Cannot migrate '{key}' command directory "
-                f"from [cyan]{legacy}[/cyan] to [cyan]{canonical}[/cyan]: "
-                "the preset registry could not be read to verify installed presets."
-            )
-            console.print(f"[dim]Details:[/dim] {_cli_error_detail(exc)}")
-            console.print(
-                "A command directory migration cannot reconcile preset command "
-                "artifacts while the preset registry state is unknown. Fix or "
-                "restore [cyan].specify/presets/.registry[/cyan] and retry."
-            )
-            raise typer.Exit(1)
-        if affected_presets:
-            preset_list = ", ".join(sorted(affected_presets))
-            console.print(
-                f"[red]Error:[/red] Cannot migrate '{key}' command directory "
-                f"from [cyan]{legacy}[/cyan] to [cyan]{canonical}[/cyan] while "
-                f"preset override(s) are installed: [bold]{preset_list}[/bold]."
-            )
-            console.print(
-                "Preset command artifacts cannot yet be reconciled across this "
-                "command directory migration, so the upgrade is refused before "
-                "changing files."
-            )
-            console.print(
-                "Remove the preset(s), run the upgrade, then reinstall them:\n"
-                f"  [cyan]specify preset remove <id>[/cyan]\n"
-                f"  [cyan]specify integration upgrade {key} --script {selected_script} --force[/cyan]\n"
-                f"  [cyan]specify preset add <id>[/cyan]"
-            )
-            raise typer.Exit(1)
-
-    # Reject command↔skills layout changes while preset artifacts are tracked
-    # for the integration (review #3415). Preset rescaffolding is best-effort:
-    # an enabled preset can still have a missing/corrupt manifest or command
-    # source, or fail during a write. Phase 2 would otherwise delete the
-    # old-layout file before a replacement is known to exist. Refuse before
-    # any mutation; same-layout upgrades still rescaffold the active agent.
+    # Guard: reject a command↔skills layout change while preset overrides are
+    # installed for this agent (review #3415).  A dual-mode agent (e.g. Bob)
+    # can flip layout across an upgrade (``--skills`` / ``--legacy-commands``).
+    # Extension artifacts are reconciled after the flip (see below), but preset
+    # artifacts cannot be: there is no agent-scoped preset re-registration
+    # anywhere in the CLI, so migrating would delete a preset's old-layout
+    # files without recreating them in the new layout and leave the preset
+    # registry claiming artifacts that no longer exist.  Detect the intended
+    # layout (``is_skills_mode`` reflects the resolved flags/disk state, so a
+    # plain same-layout upgrade is unaffected) and bail out *before* any
+    # mutation with an actionable error so the project is never left in a
+    # half-migrated, inconsistent state.
    if _manifest_tracks_skill_layout(old_manifest) != integration.is_skills_mode(
        parsed_options, project_root
    ):
@@ -730,9 +524,9 @@ def integration_upgrade(
                f"preset override(s) are installed: [bold]{preset_list}[/bold]."
            )
            console.print(
-                "Preset artifacts cannot be safely reconciled across a "
-                "command↔skills layout change, so the migration is refused "
-                "before changing files."
+                "Preset artifacts cannot yet be reconciled across a command↔skills "
+                "layout change, so the migration would orphan their files and leave "
+                "the preset registry inconsistent."
            )
            console.print(
                "Remove the preset(s), run the upgrade, then reinstall them:\n"
@@ -763,9 +557,6 @@ def integration_upgrade(
            infra_integration, current, infra_key, infra_parsed,
            project_root=project_root,
        ),
-        invoke_prefix=_invoke_prefix_for_integration(
-            infra_integration, infra_key, infra_parsed, project_root
-        ),
    )
    if os.name != "nt":
        from .. import ensure_executable_scripts
@@ -775,13 +566,6 @@ def integration_upgrade(
    console.print(f"Upgrading integration: [cyan]{key}[/cyan]")
    new_manifest = IntegrationManifest(key, project_root, version=_get_speckit_version())

-    from ..events import resolve_events
-    events_map = resolve_events(
-        key,
-        integration.config,
-        project_root,
-        parsed_options,
-    )
    try:
        integration.setup(
            project_root,
@@ -789,7 +573,6 @@ def integration_upgrade(
            parsed_options=parsed_options,
            script_type=selected_script,
            raw_options=raw_options,
-            events=events_map,
        )
        settings = _with_integration_setting(
            current,
@@ -809,9 +592,6 @@ def integration_upgrade(
                        integration, {"integration_settings": settings}, key, parsed_options,
                        project_root=project_root,
                    ),
-                    invoke_prefix=_invoke_prefix_for_integration(
-                        integration, key, parsed_options, project_root
-                    ),
                    force=force,
                    refresh_managed=True,
                )
@@ -866,38 +646,66 @@ def integration_upgrade(
        if stale_removed:
            console.print(f"  Removed {len(stale_removed)} stale file(s) from previous install")

-    legacy_command_root_changed = _legacy_command_root_changed(
-        integration,
-        project_root,
-        old_manifest,
-        new_manifest,
-    )
-    if legacy_command_root_changed:
-        _unregister_enabled_extension_commands_for_agent(
+    # Re-register enabled extensions for the upgraded agent so its extension
+    # commands are (re)created — including agents installed before this
+    # back-fill existed. Mirrors switch for command registration; see #2886.
+    # Done after the upgrade has fully settled (Phase 2 included) and outside
+    # the try/except above so this best-effort step cannot affect upgrade
+    # success.
+    #
+    # Layout-change reconciliation: a dual-mode agent (e.g. Bob) can flip
+    # between the legacy commands layout and the skills layout across an
+    # upgrade (``upgrade bob --integration-options "--skills"`` / reverse
+    # ``--legacy-commands``). Phase 2 above only removes stale files tracked by
+    # the *integration* manifest (core commands); extension artifacts are
+    # tracked separately in the extension registry, so the old layout's
+    # extension command/skill files would otherwise linger as orphans. When the
+    # layout actually changed, first unregister the agent's extension artifacts
+    # (removing old-layout files and clearing per-agent registry entries) so the
+    # re-registration below recreates them in the new layout. ``upgrade``s that
+    # don't change layout skip this to avoid needless remove/re-add churn.
+    #
+    # Only the *active* integration is reconciled this way (``installed_key ==
+    # key``).  ``ExtensionManager.unregister_agent_artifacts`` treats the
+    # per-extension ``registered_skills`` list as belonging to the passed agent
+    # and, when that agent's skills directory is absent, falls back to scanning
+    # every agent's skills directory — so running it for a *secondary*
+    # (non-active) agent could delete or untrack the *active* agent's extension
+    # skills.  The subsequent re-registration cannot repair that because
+    # extension skill rendering is intentionally scoped to the active agent
+    # (#2948).  Extension skills only ever exist for the active agent, so
+    # skipping the unregister for a secondary agent orphans nothing new: a
+    # secondary agent only has extension *command* files, which the
+    # re-registration below rewrites in place regardless of layout.
+    #
+    # Known limitation: preset command/skill artifacts are NOT reconciled on a
+    # layout change. There is no agent-scoped preset re-registration mechanism
+    # anywhere in the CLI — ``use`` / ``switch`` / ``upgrade`` never reconcile
+    # presets for any agent (presets are only (un)registered at preset
+    # install/remove time). Rather than silently orphan them, the guard near
+    # the top of this function rejects a layout-changing upgrade while preset
+    # overrides are installed, so control only reaches here (with a changed
+    # layout) when no preset artifacts are at stake. Full preset reconciliation
+    # would require a new cross-cutting PresetManager subsystem affecting every
+    # dual-layout agent, which is out of scope for this Bob migration.
+    if (
+        installed_key == key
+        and _manifest_tracks_skill_layout(old_manifest)
+        != _manifest_tracks_skill_layout(new_manifest)
+    ):
+        _unregister_extensions_for_agent(
            project_root,
            key,
            continuing=(
-                "The integration command directory changed, but legacy enabled "
-                "extension artifacts may need manual cleanup."
+                "The integration layout changed, but old-layout extension "
+                "artifacts may need manual cleanup."
            ),
        )
-
-    # Re-register enabled extensions and presets only when upgrading the
-    # active integration. Inactive integrations remain untouched until
-    # `use` or `switch` activates and rescaffolds them (#2948). This runs
-    # after the core upgrade transaction, so failures remain best-effort.
-    if key == installed_key:
-        _register_extensions_for_agent(
-            project_root,
-            key,
-            force=True,
-            continuing="The integration was upgraded, but installed extensions may need re-registration.",
-        )
-        _register_presets_for_agent(
-            project_root,
-            key,
-            continuing="The integration was upgraded, but installed presets may need re-registration.",
-        )
+    _register_extensions_for_agent(
+        project_root,
+        key,
+        continuing="The integration was upgraded, but installed extensions may need re-registration.",
+    )

    name = (integration.config or {}).get("name", key)
    console.print(f"\n[green]✓[/green] Integration '{name}' upgraded successfully")
@@ -18,7 +18,6 @@ from ._commands import integration_app, integration_catalog_app
 from ._helpers import (
    _read_integration_json,
    _register_extensions_for_agent,
-    _register_presets_for_agent,
    _resolve_integration_options,
    _set_default_integration_or_exit,
 )
@@ -249,11 +248,6 @@ def integration_use(
        key,
        continuing="The integration was selected, but installed extensions may need re-registration.",
    )
-    _register_presets_for_agent(
-        project_root,
-        key,
-        continuing="The integration was selected, but installed presets may need re-registration.",
-    )
    console.print(f"[green]✓[/green] Default integration set to [bold]{key}[/bold].")


@@ -318,26 +312,22 @@ def integration_search(

    console.print(f"\n[green]Found {len(results)} integration(s):[/green]\n")
    for integ in sorted(results, key=lambda e: e.get("id", "")):
-        iid_value = str(integ.get("id", "?"))
-        iid = _rich_escape(iid_value)
-        name = _rich_escape(str(integ.get("name", iid_value)))
-        version = _rich_escape(str(integ.get("version", "?")))
+        iid = integ.get("id", "?")
+        name = integ.get("name", iid)
+        version = integ.get("version", "?")
        console.print(f"[bold]{name}[/bold] ({iid}) v{version}")
        desc = integ.get("description", "")
        if desc:
-            console.print(f"  {_rich_escape(str(desc))}")
+            console.print(f"  {desc}")

-        author_value = _rich_escape(str(integ.get("author", "Unknown")))
-        console.print(f"\n  [dim]Author:[/dim] {author_value}")
+        console.print(f"\n  [dim]Author:[/dim] {integ.get('author', 'Unknown')}")
        tags = integ.get("tags", [])
        if isinstance(tags, list) and tags:
-            safe_tags = _rich_escape(", ".join(str(t) for t in tags))
-            console.print(f"  [dim]Tags:[/dim] {safe_tags}")
+            console.print(f"  [dim]Tags:[/dim] {', '.join(str(t) for t in tags)}")

-        cat_name_value = integ.get("_catalog_name", "")
-        cat_name = _rich_escape(str(cat_name_value))
+        cat_name = integ.get("_catalog_name", "")
        install_allowed = integ.get("_install_allowed", True)
-        if cat_name_value:
+        if cat_name:
            if install_allowed:
                console.print(f"  [dim]Catalog:[/dim] {cat_name}")
            else:
@@ -346,9 +336,9 @@ def integration_search(
                    "[yellow](discovery only — not installable)[/yellow]"
                )

-        if iid_value == installed_key:
+        if iid == installed_key:
            console.print("\n  [green]✓ Installed[/green] (currently active)")
-        elif iid_value in INTEGRATION_REGISTRY:
+        elif iid in INTEGRATION_REGISTRY:
            console.print(f"\n  [cyan]Install:[/cyan] specify integration install {iid}")
        elif install_allowed:
            console.print(
@@ -378,7 +368,6 @@ def integration_info(
    project_root = _require_specify_project()
    catalog = IntegrationCatalog(project_root)
    installed_key = _default_integration_key(_read_integration_json(project_root))
-    safe_integration_id = _rich_escape(str(integration_id))

    try:
        info = catalog.get_integration_info(integration_id)
@@ -391,38 +380,29 @@ def integration_info(
        catalog_error = None

    if info:
-        name = _rich_escape(str(info.get("name", integration_id)))
-        version = _rich_escape(str(info.get("version", "?")))
-        console.print(
-            f"\n[bold cyan]{name}[/bold cyan] ({safe_integration_id}) v{version}"
-        )
+        name = info.get("name", integration_id)
+        version = info.get("version", "?")
+        console.print(f"\n[bold cyan]{name}[/bold cyan] ({integration_id}) v{version}")
        if info.get("description"):
-            console.print(f"  {_rich_escape(str(info['description']))}")
+            console.print(f"  {info['description']}")
        console.print()

-        author_value = _rich_escape(str(info.get("author", "Unknown")))
-        console.print(f"  [dim]Author:[/dim] {author_value}")
+        console.print(f"  [dim]Author:[/dim] {info.get('author', 'Unknown')}")
        if info.get("license"):
-            console.print(
-                f"  [dim]License:[/dim] {_rich_escape(str(info['license']))}"
-            )
+            console.print(f"  [dim]License:[/dim] {info['license']}")

        tags = info.get("tags", [])
        if isinstance(tags, list) and tags:
-            safe_tags = _rich_escape(", ".join(str(t) for t in tags))
-            console.print(f"  [dim]Tags:[/dim] {safe_tags}")
+            console.print(f"  [dim]Tags:[/dim] {', '.join(str(t) for t in tags)}")

-        cat_name_value = info.get("_catalog_name", "")
-        cat_name = _rich_escape(str(cat_name_value))
+        cat_name = info.get("_catalog_name", "")
        install_allowed = info.get("_install_allowed", True)
-        if cat_name_value:
+        if cat_name:
            install_note = "" if install_allowed else " [yellow](discovery only)[/yellow]"
            console.print(f"  [dim]Source catalog:[/dim] {cat_name}{install_note}")

        if info.get("repository"):
-            console.print(
-                f"  [dim]Repository:[/dim] {_rich_escape(str(info['repository']))}"
-            )
+            console.print(f"  [dim]Repository:[/dim] {info['repository']}")

        if integration_id == installed_key:
            console.print("\n  [green]✓ Installed[/green] (currently active)")
@@ -458,7 +438,7 @@ def integration_info(
        else:
            console.print("\nTry again when online, or use a built-in integration ID directly.")
    else:
-        console.print(f"[red]Error:[/red] Integration '{safe_integration_id}' not found")
+        console.print(f"[red]Error:[/red] Integration '{integration_id}' not found")
        console.print("\nTry: specify integration search")
    raise typer.Exit(1)

@@ -509,14 +489,13 @@ def integration_catalog_list():
        display_name = str(raw_name).strip() if raw_name is not None else ""
        if not display_name:
            display_name = f"catalog-{i + 1}"
-        safe_name = _rich_escape(display_name)
        if env_override or project_configs is None:
-            console.print(f"  - [bold]{safe_name}[/bold] — {install_status}")
+            console.print(f"  - [bold]{display_name}[/bold] — {install_status}")
        else:
-            console.print(f"  [{i}] [bold]{safe_name}[/bold] — {install_status}")
-        console.print(f"      {_rich_escape(str(cfg.get('url', '')))}")
+            console.print(f"  [{i}] [bold]{display_name}[/bold] — {install_status}")
+        console.print(f"      {cfg.get('url', '')}")
        if cfg.get("description"):
-            console.print(f"      [dim]{_rich_escape(str(cfg['description']))}[/dim]")
+            console.print(f"      [dim]{cfg['description']}[/dim]")
        console.print()


@@ -1,165 +0,0 @@
-"""Alquimia AI integration."""
-
-from __future__ import annotations
-
-from typing import Any
-
-from ..._utils import dump_frontmatter
-from ..base import SkillsIntegration
-
-# Mapping of command template stem → argument-hint text shown inline
-# when a user invokes the slash command in Alquimia AI.
-ARGUMENT_HINTS: dict[str, str] = {
-    "specify": "Describe the feature you want to specify",
-    "plan": "Optional guidance for the planning phase",
-    "tasks": "Optional task generation constraints",
-    "implement": "Optional implementation guidance or task filter",
-    "analyze": "Optional focus areas for analysis",
-    "clarify": "Optional areas to clarify in the spec",
-    "constitution": "Principles or values for the project constitution",
-    "checklist": "Domain or focus area for the checklist",
-    "taskstoissues": "Optional filter or label for GitHub issues",
-}
-
-
-class AlquimiaAIIntegration(SkillsIntegration):
-    """Integration for Alquimia AI skills."""
-
-    key = "alquimia"
-    config = {
-        "name": "Alquimia AI",
-        "folder": ".alquimia/",
-        "commands_subdir": "skills",
-        "install_url": "https://docs.alquimia.ai",
-        "requires_cli": True,
-    }
-    registrar_config = {
-        "dir": ".alquimia/skills",
-        "format": "markdown",
-        "args": "$ARGUMENTS",
-        "extension": "/SKILL.md",
-    }
-    multi_install_safe = True
-
-    def _render_skill(
-        self, template_name: str, frontmatter: dict[str, Any], body: str
-    ) -> str:
-        """Render a processed command template as an Alquimia skill."""
-        skill_name = f"speckit-{template_name.replace('.', '-')}"
-        description = frontmatter.get(
-            "description",
-            f"Spec-kit workflow command: {template_name}",
-        )
-        skill_frontmatter = self._build_skill_fm(
-            skill_name, description, f"templates/commands/{template_name}.md"
-        )
-        frontmatter_text = dump_frontmatter(skill_frontmatter)
-        return f"---\n{frontmatter_text}\n---\n\n{body.strip()}\n"
-
-    def _build_skill_fm(self, name: str, description: str, source: str) -> dict:
-        from specify_cli.agents import CommandRegistrar
-
-        return CommandRegistrar.build_skill_frontmatter(
-            self.key, name, description, source
-        )
-
-    @staticmethod
-    def inject_argument_hint(content: str, hint: str) -> str:
-        """Insert ``argument-hint`` after the first ``description:`` in YAML frontmatter.
-
-        Skips injection if ``argument-hint:`` already exists in the
-        frontmatter to avoid duplicate keys.
-        """
-        lines = content.splitlines(keepends=True)
-
-        # Pre-scan: bail out if argument-hint already present in frontmatter
-        dash_count = 0
-        for line in lines:
-            stripped = line.rstrip("\n\r")
-            if stripped == "---":
-                dash_count += 1
-                if dash_count == 2:
-                    break
-                continue
-            if dash_count == 1 and stripped.startswith("argument-hint:"):
-                return content  # already present
-
-        out: list[str] = []
-        in_fm = False
-        dash_count = 0
-        injected = False
-        for line in lines:
-            stripped = line.rstrip("\n\r")
-            if stripped == "---":
-                dash_count += 1
-                in_fm = dash_count == 1
-                out.append(line)
-                continue
-            if in_fm and not injected and stripped.startswith("description:"):
-                out.append(line)
-                # Preserve the exact line-ending style (\r\n vs \n)
-                if line.endswith("\r\n"):
-                    eol = "\r\n"
-                elif line.endswith("\n"):
-                    eol = "\n"
-                else:
-                    eol = ""
-                escaped = hint.replace("\\", "\\\\").replace('"', '\\"')
-                out.append(f'argument-hint: "{escaped}"{eol}')
-                injected = True
-                continue
-            out.append(line)
-        return "".join(out)
-
-    @staticmethod
-    def _inject_frontmatter_flag(content: str, key: str, value: str = "true") -> str:
-        """Insert ``key: value`` before the closing ``---`` if not already present."""
-        lines = content.splitlines(keepends=True)
-
-        # Pre-scan: bail out if already present in frontmatter
-        dash_count = 0
-        for line in lines:
-            stripped = line.rstrip("\n\r")
-            if stripped == "---":
-                dash_count += 1
-                if dash_count == 2:
-                    break
-                continue
-            if dash_count == 1 and stripped.startswith(f"{key}:"):
-                return content
-
-        # Inject before the closing --- of frontmatter
-        out: list[str] = []
-        dash_count = 0
-        injected = False
-        for line in lines:
-            stripped = line.rstrip("\n\r")
-            if stripped == "---":
-                dash_count += 1
-                if dash_count == 2 and not injected:
-                    if line.endswith("\r\n"):
-                        eol = "\r\n"
-                    elif line.endswith("\n"):
-                        eol = "\n"
-                    else:
-                        eol = ""
-                    out.append(f"{key}: {value}{eol}")
-                    injected = True
-            out.append(line)
-        return "".join(out)
-
-    def post_process_skill_content(self, content: str) -> str:
-        """Inject Alquimia-specific frontmatter flags, hints and hook notes."""
-        updated = super().post_process_skill_content(content)
-        updated = self._inject_frontmatter_flag(updated, "user-invocable")
-        updated = self._inject_frontmatter_flag(
-            updated, "disable-model-invocation", "false"
-        )
-        for line in updated.splitlines():
-            if line.startswith("name:"):
-                name = line.removeprefix("name:").strip().strip("\"'")
-                hint = ARGUMENT_HINTS.get(name.removeprefix("speckit-"))
-                if hint:
-                    updated = self.inject_argument_hint(updated, hint)
-                break
-        return updated
@@ -27,16 +27,14 @@ from typing import TYPE_CHECKING, Any

 import yaml

-from .._invocation_style import get_invocation_prefix, is_dollar_skills_agent
 from .._toml_string import escape_toml_basic as _escape_toml_basic
 from .._toml_string import has_illegal_toml_control as _has_illegal_toml_control
-from ..events import install_integration_events, remove_integration_events

 if TYPE_CHECKING:
    from .manifest import IntegrationManifest

 _HOOK_COMMAND_NOTE = (
-    "- When constructing command invocations from hook command names, "
+    "- When constructing slash commands from hook command names, "
    "replace dots (`.`) with hyphens (`-`). "
    "For example, `speckit.git.commit` → `/speckit-git-commit`.\n"
 )
@@ -160,17 +158,7 @@ class IntegrationBase(ABC):
    @classmethod
    def options(cls) -> list[IntegrationOption]:
        """Return options this integration accepts. Default: none."""
-        opts = []
-        if bool(getattr(cls, "CANONICAL_TO_NATIVE", None) and getattr(cls, "events_config_file", None)):
-            opts.append(
-                IntegrationOption(
-                    "--events",
-                    is_flag=False,
-                    default="true",
-                    help="Enable/disable runtime events (true|false, default: true)",
-                )
-            )
-        return opts
+        return []

    def effective_invoke_separator(
        self,
@@ -225,8 +213,8 @@ class IntegrationBase(ABC):
        on-disk layout to avoid silently migrating an existing project to a
        different mode.  The default ignores it.

-        The default for command-first integrations is skills mode only when
-        ``--skills`` was requested.
+        The default (command-first integrations, e.g. Copilot's default
+        layout) is skills mode only when ``--skills`` was requested.
        ``SkillsIntegration`` overrides this to return ``True`` by default;
        skills-first integrations that expose a legacy opt-out (e.g. Bob)
        override it to honor their own flag.
@@ -491,11 +479,7 @@ class IntegrationBase(ABC):
        tracking) would otherwise be deleted even though they are still
        managed.  Subclasses list such paths here to protect them.
        """
-        exclusions = set()
-        if self.supports_events():
-            from ..events import events_stale_exclusions
-            exclusions.update(events_stale_exclusions(self.key))
-        return exclusions
+        return set()

    def commands_dest(self, project_root: Path) -> Path:
        """Return the absolute path to the commands output directory.
@@ -617,9 +601,7 @@ class IntegrationBase(ABC):
        return created

    @staticmethod
-    def resolve_command_refs(
-        content: str, separator: str = ".", prefix: str = "/"
-    ) -> str:
+    def resolve_command_refs(content: str, separator: str = ".") -> str:
        """Replace ``__SPECKIT_COMMAND_<NAME>__`` placeholders with invocations.

        Each placeholder encodes a command name in upper-case with
@@ -629,16 +611,10 @@ class IntegrationBase(ABC):

        * ``separator="."`` → ``/speckit.plan``, ``/speckit.git.commit``
        * ``separator="-"`` → ``/speckit-plan``, ``/speckit-git-commit``
-
-        *prefix* defaults to ``"/"`` but may be ``"$"`` for agents whose
-        native skills invocation uses dollar-prefixed chat commands.
        """
        return re.sub(
            r"__SPECKIT_COMMAND_([A-Z][A-Z0-9_]*)__",
-            lambda m: prefix
-            + "speckit"
-            + separator
-            + m.group(1).lower().replace("_", separator),
+            lambda m: "/speckit" + separator + m.group(1).lower().replace("_", separator),
            content,
        )

@@ -862,12 +838,7 @@ class IntegrationBase(ABC):
        content = CommandRegistrar.rewrite_project_relative_paths(content)

        # 8. Replace __SPECKIT_COMMAND_<NAME>__ with invocation strings
-        invocation_prefix = get_invocation_prefix(
-            agent_name, invoke_separator == "-"
-        )
-        content = IntegrationBase.resolve_command_refs(
-            content, invoke_separator, invocation_prefix
-        )
+        content = IntegrationBase.resolve_command_refs(content, invoke_separator)

        return content

@@ -931,46 +902,8 @@ class IntegrationBase(ABC):

        Returns ``(removed, skipped)`` file lists.
        """
-        self.remove_events(project_root, manifest)
        return manifest.uninstall(project_root, force=force)

-    def emit_events(
-        self,
-        project_root: Path,
-        manifest: IntegrationManifest,
-        events: dict[str, dict[str, Any]] | None = None,
-        parsed_options: dict[str, Any] | None = None,
-        **opts: Any,
-    ) -> list[Path]:
-        """Emit native event configuration for this integration."""
-        return install_integration_events(self, project_root, manifest, events or {})
-
-    def remove_events(
-        self,
-        project_root: Path,
-        manifest: IntegrationManifest,
-    ) -> None:
-        """Remove Specify-authored event entries from native config."""
-        remove_integration_events(self, project_root, manifest)
-
-    def supports_events(self) -> bool:
-        """Return True if this integration supports agent-native events."""
-        return bool(getattr(self, "CANONICAL_TO_NATIVE", None) and getattr(self, "events_config_file", None))
-
-    # Context-injection envelope for hook stdout, keyed by canonical event
-    # (with "*" as the fallback). Not every agent injects a hook's plain-text
-    # stdout as model context: Gemini/Tabnine/Qwen/Devin are JSON-only
-    # protocols (plain text becomes user-facing noise), Copilot discards
-    # non-JSON stdout, and Cursor parses stdout as JSON. Values:
-    #   "hookSpecificOutput" → {"hookSpecificOutput": {"additionalContext": ...}}
-    #   "additionalContext"  → {"additionalContext": ...}   (top-level, Copilot)
-    #   "additional_context" → {"additional_context": ...}  (top-level, Cursor)
-    #   "suppress"           → emit nothing (strict-JSON agents on events whose
-    #                          output can't be used)
-    # Absent (no matching key and no "*") → plain stdout passthrough
-    # (Claude/Codex inject plain stdout; opencode injects via its TS plugin).
-    events_context_envelope: dict[str, str] = {}
-
    # -- Convenience helpers for subclasses -------------------------------

    def install(
@@ -1075,12 +1008,6 @@ class MarkdownIntegration(IntegrationBase):
            created.append(dst_file)


-        # Install agent runtime events
-        event_files = self.emit_events(
-            project_root, manifest, events=opts.get("events"), parsed_options=parsed_options
-        )
-        created.extend(event_files)
-
        return created


@@ -1288,12 +1215,6 @@ class TomlIntegration(IntegrationBase):
            created.append(dst_file)


-        # Install agent runtime events
-        event_files = self.emit_events(
-            project_root, manifest, events=opts.get("events"), parsed_options=parsed_options
-        )
-        created.extend(event_files)
-
        return created


@@ -1530,12 +1451,6 @@ class YamlIntegration(IntegrationBase):
            created.append(dst_file)


-        # Install agent runtime events
-        event_files = self.emit_events(
-            project_root, manifest, events=opts.get("events"), parsed_options=parsed_options
-        )
-        created.extend(event_files)
-
        return created


@@ -1605,21 +1520,18 @@ class SkillsIntegration(IntegrationBase):
        return project_root / folder / subdir

    def build_command_invocation(self, command_name: str, args: str = "") -> str:
-        """Build the agent's native invocation for a hyphenated skill name."""
+        """Skills use ``/speckit-<stem>`` (hyphenated directory name)."""
        stem = command_name
        if stem.startswith("speckit."):
            stem = stem[len("speckit."):]

-        prefix = "$" if is_dollar_skills_agent(self.key, True) else "/"
-        invocation = prefix + "speckit-" + stem.replace(".", "-")
+        invocation = "/speckit-" + stem.replace(".", "-")
        if args:
            invocation = f"{invocation} {args}"
        return invocation

    @staticmethod
-    def _inject_hook_command_note(
-        content: str, invocation_prefix: str = "/"
-    ) -> str:
+    def _inject_hook_command_note(content: str) -> str:
        """Insert a dot-to-hyphen note before each hook output instruction.

        Targets the line ``- For each executable hook, output the following``
@@ -1628,11 +1540,6 @@ class SkillsIntegration(IntegrationBase):
        above them.
        """
        note = _HOOK_COMMAND_NOTE.rstrip("\n")
-        if invocation_prefix != "/":
-            note = note.replace(
-                "`/speckit-git-commit`",
-                f"`{invocation_prefix}speckit-git-commit`",
-            )

        def repl(m: re.Match[str]) -> str:
            indent = m.group(1)
@@ -1666,13 +1573,10 @@ class SkillsIntegration(IntegrationBase):
        Called by external skill generators (presets, extensions) to let
        the integration inject agent-specific frontmatter or body
        transformations.  The base implementation injects shared skills
-        guidance for converting dotted hook command names to the agent-native
-        hyphenated command invocation (e.g. ``/speckit-git-commit`` or
-        ``$speckit-git-commit``).  Subclasses may override -- see
-        ``ClaudeIntegration``.
+        guidance for converting dotted hook command names to hyphenated
+        slash commands.  Subclasses may override — see ``ClaudeIntegration``.
        """
-        invocation_prefix = get_invocation_prefix(self.key, True)
-        return self._inject_hook_command_note(content, invocation_prefix)
+        return self._inject_hook_command_note(content)

    def setup(
        self,
@@ -1723,27 +1627,13 @@ class SkillsIntegration(IntegrationBase):
            command_name = src_file.stem  # e.g. "plan"
            skill_name = f"speckit-{command_name.replace('.', '-')}"

-            # Parse frontmatter for description. Locate the closing ``---`` on
-            # its own line rather than with ``raw.split("---", 2)`` — a bare
-            # substring split stops at the first ``---`` *anywhere*, including
-            # one inside a value such as ``description: Separate sections
-            # with ---``, which truncates the frontmatter and drops later keys.
-            # The block between the delimiters is parsed unstripped so trailing
-            # newlines in literal (``|``) block scalars survive.
+            # Parse frontmatter for description
            frontmatter: dict[str, Any] = {}
            if raw.startswith("---"):
-                fm_lines = raw.splitlines(keepends=True)
-                fm_close = next(
-                    (
-                        i
-                        for i in range(1, len(fm_lines))
-                        if fm_lines[i].rstrip() == "---"
-                    ),
-                    None,
-                )
-                if fm_close is not None:
+                parts = raw.split("---", 2)
+                if len(parts) >= 3:
                    try:
-                        fm = yaml.safe_load("".join(fm_lines[1:fm_close]))
+                        fm = yaml.safe_load(parts[1])
                        if isinstance(fm, dict):
                            frontmatter = fm
                    except yaml.YAMLError:
@@ -1758,27 +1648,11 @@ class SkillsIntegration(IntegrationBase):
            # Strip the processed frontmatter — we rebuild it for skills.
            # Preserve leading whitespace in the body to match release ZIP
            # output byte-for-byte (the template body starts with \n after
-            # the closing ---). Scan for the closing ``---`` on its own line
-            # rather than ``split("---", 2)`` so a ``---`` embedded in a value
-            # does not truncate the frontmatter and spill it into the body.
+            # the closing ---).
            if processed_body.startswith("---"):
-                body_lines = processed_body.splitlines(keepends=True)
-                close_idx = next(
-                    (
-                        i
-                        for i in range(1, len(body_lines))
-                        if body_lines[i].rstrip() == "---"
-                    ),
-                    None,
-                )
-                if close_idx is not None:
-                    # Keep whatever trails the ``---`` marker on the closing
-                    # line (normally just the newline) so the body stays
-                    # byte-for-byte identical to ``split("---", 2)[2]``. The
-                    # line-anchored check guarantees ``---`` sits at index 0.
-                    processed_body = body_lines[close_idx][3:] + "".join(
-                        body_lines[close_idx + 1 :]
-                    )
+                parts = processed_body.split("---", 2)
+                if len(parts) >= 3:
+                    processed_body = parts[2]

            # Select description — use the original template description
            # to stay byte-for-byte identical with release ZIP output.
@@ -1812,10 +1686,4 @@ class SkillsIntegration(IntegrationBase):
            created.append(dst)


-        # Install agent runtime events
-        event_files = self.emit_events(
-            project_root, manifest, events=opts.get("events"), parsed_options=parsed_options
-        )
-        created.extend(event_files)
-
        return created
@@ -21,7 +21,6 @@ from typing import Any, Dict, List, Optional, Tuple
 import yaml
 from packaging import version as pkg_version

-from .._download_security import MAX_JSON_METADATA_BYTES, read_response_limited
 from ..catalogs import CatalogEntry, CatalogStackBase


@@ -201,14 +200,7 @@ class IntegrationCatalog(CatalogStackBase):
                final_url = resp.geturl()
                if final_url != entry.url:
                    self._validate_catalog_url(final_url)
-                catalog_data = json.loads(
-                    read_response_limited(
-                        resp,
-                        max_bytes=MAX_JSON_METADATA_BYTES,
-                        error_type=IntegrationCatalogError,
-                        label=f"catalog from {entry.url}",
-                    ).decode("utf-8")
-                )
+                catalog_data = json.loads(resp.read())

            shape_error = _catalog_shape_error(catalog_data)
            if shape_error is not None:
@@ -237,15 +229,6 @@ class IntegrationCatalog(CatalogStackBase):
            raise IntegrationCatalogError(
                f"Failed to fetch catalog from {entry.url}: {exc}"
            )
-        except UnicodeDecodeError as exc:
-            # A non-UTF-8 response body fails at .decode() before json.loads()
-            # ever runs, so JSONDecodeError below does not cover it (the two are
-            # sibling ValueError subclasses, not parent/child). Without this the
-            # raw UnicodeDecodeError escapes _get_merged_integrations()'s
-            # "warn and skip this catalog" handler and kills the whole command.
-            raise IntegrationCatalogError(
-                f"Catalog from {entry.url} is not valid UTF-8: {exc}"
-            )
        except json.JSONDecodeError as exc:
            raise IntegrationCatalogError(
                f"Invalid JSON in catalog from {entry.url}: {exc}"
@@ -54,17 +54,6 @@ class ClaudeIntegration(SkillsIntegration):
    }
    multi_install_safe = True

-    CANONICAL_TO_NATIVE = {
-        "session_start": "SessionStart",
-        "pre_tool_use": "PreToolUse",
-        "post_tool_use": "PostToolUse",
-        "session_end": "SessionEnd",
-        "user_prompt_submit": "UserPromptSubmit",
-        "stop": "Stop",
-    }
-    events_config_file = ".claude/settings.json"
-    events_format = "json-nested"
-
    @staticmethod
    def inject_argument_hint(content: str, hint: str) -> str:
        """Insert ``argument-hint`` after the first ``description:`` in YAML frontmatter.
@@ -29,17 +29,6 @@ class CodexIntegration(SkillsIntegration):
    dev_no_symlink = True
    multi_install_safe = True

-    CANONICAL_TO_NATIVE = {
-        "session_start": "SessionStart",
-        "pre_tool_use": "PreToolUse",
-        "post_tool_use": "PostToolUse",
-        "session_end": "SessionEnd",
-        "user_prompt_submit": "UserPromptSubmit",
-        "stop": "Stop",
-    }
-    events_config_file = ".codex/config.toml"
-    events_format = "toml"
-
    def build_exec_args(
        self,
        prompt: str,
@@ -60,13 +49,11 @@ class CodexIntegration(SkillsIntegration):

    @classmethod
    def options(cls) -> list[IntegrationOption]:
-        opts = super().options()
-        opts.append(
+        return [
            IntegrationOption(
                "--skills",
                is_flag=True,
                default=True,
                help="Install as agent skills (default for Codex)",
-            )
-        )
-        return opts
+            ),
+        ]
@@ -1,19 +1,13 @@
 """Copilot integration — GitHub Copilot in VS Code.

-Copilot supports two layouts:
- Skills are the default and use ``speckit-<name>/SKILL.md`` directories under
-  ``.github/skills/``
- ``--commands`` uses ``.agent.md`` files, companion ``.prompt.md`` files, and
-  a VS Code settings merge
-
-The two modes are mutually exclusive. The commands layout remains supported,
-but is no longer the preferred default.
-
-The commands layout has several unique behaviors compared to standard markdown
-agents:
+Copilot has several unique behaviors compared to standard markdown agents:
 - Commands use ``.agent.md`` extension (not ``.md``)
 - Each command gets a companion ``.prompt.md`` file in ``.github/prompts/``
 - Installs ``.vscode/settings.json`` with prompt file recommendations
+
+When ``--skills`` is passed via ``--integration-options``, Copilot scaffolds
+commands as ``speckit-<name>/SKILL.md`` directories under ``.github/skills/``
+instead.  The two modes are mutually exclusive.
 """

 from __future__ import annotations
@@ -25,24 +19,9 @@ import warnings
 from pathlib import Path
 from typing import Any

-import typer
-
 from ..base import IntegrationBase, IntegrationOption, SkillsIntegration
 from ..manifest import IntegrationManifest

-_COPILOT_CORE_COMMANDS = {
-    "analyze",
-    "checklist",
-    "clarify",
-    "constitution",
-    "converge",
-    "implement",
-    "plan",
-    "specify",
-    "tasks",
-    "taskstoissues",
-}
-

 def _copilot_executable() -> str:
    """Return the executable name for Copilot CLI on this platform.
@@ -78,24 +57,22 @@ def _allow_all() -> bool:
    return True


-def _validate_mode_options(parsed_options: dict[str, Any] | None) -> None:
-    """Reject the two explicit Copilot layout selectors used together."""
-    opts = parsed_options or {}
-    if opts.get("skills") and opts.get("commands"):
-        from ..._console import console
-
-        console.print(
-            "[red]Error:[/red] --skills and --commands are mutually exclusive; "
-            "pass only one."
-        )
-        raise typer.Exit(1)
+def _warn_legacy_markdown_default() -> None:
+    """Warn that Copilot's default markdown scaffold is being phased out."""
+    warnings.warn(
+        "Copilot legacy markdown mode is deprecated and will stop being the "
+        'default in a future Spec Kit release; pass --integration-options "--skills" '
+        "to opt in to Copilot skills mode now.",
+        UserWarning,
+        stacklevel=3,
+    )


 class _CopilotSkillsHelper(SkillsIntegration):
    """Internal helper used when Copilot is scaffolded in skills mode.

-    Not registered in the integration registry — only used as the default
-    skills-layout delegate by ``CopilotIntegration``.
+    Not registered in the integration registry — only used as a delegate
+    by ``CopilotIntegration`` when ``--skills`` is passed.
    """

    key = "copilot"
@@ -117,11 +94,13 @@ class _CopilotSkillsHelper(SkillsIntegration):
 class CopilotIntegration(IntegrationBase):
    """Integration for GitHub Copilot (VS Code IDE + CLI).

-    The default IDE integration (``requires_cli: False``) installs skills under
-    ``.github/skills/``. Pass ``--commands`` via ``--integration-options`` to
-    install the supported ``.agent.md`` + ``.prompt.md`` layout instead.
-    Workflow dispatch additionally requires the ``copilot`` CLI to be installed
-    separately.
+    The IDE integration (``requires_cli: False``) installs ``.agent.md``
+    command files.  Workflow dispatch additionally requires the
+    ``copilot`` CLI to be installed separately.
+
+    When ``--skills`` is passed via ``--integration-options``, commands
+    are scaffolded as ``speckit-<name>/SKILL.md`` under ``.github/skills/``
+    instead of the default ``.agent.md`` + ``.prompt.md`` layout.
    """

    key = "copilot"
@@ -138,115 +117,40 @@ class CopilotIntegration(IntegrationBase):
        "args": "$ARGUMENTS",
        "extension": ".agent.md",
    }
-    invoke_separator = "-"
-
-    CANONICAL_TO_NATIVE = {
-        "session_start": "sessionStart",
-        "pre_tool_use": "preToolUse",
-        "post_tool_use": "postToolUse",
-        "session_end": "sessionEnd",
-        "user_prompt_submit": "userPromptSubmitted",
-        # Copilot CLI supports the canonical per-turn stop lifecycle as native
-        # agentStop (U3); mapping it so an extension's stop handler fires.
-        "stop": "agentStop",
-    }
-    events_config_file = ".github/hooks/speckit.json"
-    events_format = "copilot-json"
-    # Copilot sessionStart and userPromptSubmitted inject a top-level
-    # additionalContext field into the model-facing prompt (C13). Non-JSON
-    # stdout is discarded harmlessly by Copilot on other events, so no other
-    # event needs an envelope.
-    events_context_envelope = {
-        "session_start": "additionalContext",
-        "user_prompt_submit": "additionalContext",
-    }

    # Mutable flag set by setup() — indicates the active scaffolding mode.
-    _skills_mode: bool = True
+    _skills_mode: bool = False

    def effective_invoke_separator(
        self,
        parsed_options: dict[str, Any] | None = None,
        project_root: Path | None = None,
    ) -> str:
-        """Return the separator for the resolved Copilot layout."""
-        return "-" if self.is_skills_mode(parsed_options, project_root) else "."
+        """Return ``"-"`` when skills mode is requested, ``"."`` otherwise."""
+        if parsed_options and parsed_options.get("skills"):
+            return "-"
+        if self._skills_mode:
+            return "-"
+        return self.invoke_separator

    def is_skills_mode(
        self,
        parsed_options: dict[str, Any] | None = None,
        project_root: Path | None = None,
    ) -> bool:
-        """Copilot defaults to skills; ``--commands`` opts into commands mode.
+        """Copilot is skills mode when ``--skills`` was requested.

-        Explicit flags override on-disk detection. Without a flag, existing
-        projects retain their managed Spec Kit layout while fresh projects use
-        skills. This prevents ``use`` and ``upgrade`` from silently migrating
-        projects created before skills became the default.
+        On the init path ``setup()`` has already recorded the choice in
+        ``self._skills_mode``; on the ``use``/``install`` path (where no
+        ``setup()`` runs) the signal comes from *parsed_options* (#3550), which
+        round-trips because ``--skills`` is persisted in the stored options.
        """
-        opts = parsed_options or {}
-        _validate_mode_options(opts)
-        if opts.get("skills"):
+        if parsed_options and parsed_options.get("skills"):
            return True
-        if opts.get("commands"):
-            return False
-        if project_root is not None:
-            project_root = Path(project_root)
-            manifest_path = (
-                project_root
-                / ".specify"
-                / "integrations"
-                / "copilot.manifest.json"
-            )
-            if manifest_path.is_file():
-                try:
-                    manifest_files = IntegrationManifest.load(
-                        self.key, Path(project_root)
-                    ).files
-                except (OSError, ValueError):
-                    manifest_files = None
-                if manifest_files is not None and any(
-                    path.startswith(".github/skills/speckit-")
-                    and path.endswith("/SKILL.md")
-                    for path in manifest_files
-                ):
-                    return True
-                if manifest_files is not None and any(
-                    path.startswith(".github/agents/speckit.")
-                    and path.endswith(".agent.md")
-                    for path in manifest_files
-                ):
-                    return False
-
-            github_dir = project_root / ".github"
-            has_managed_skills = any(
-                (
-                    github_dir
-                    / "skills"
-                    / f"speckit-{command}"
-                    / "SKILL.md"
-                ).is_file()
-                for command in _COPILOT_CORE_COMMANDS
-            )
-            has_managed_commands = any(
-                (
-                    github_dir
-                    / "agents"
-                    / f"speckit.{command}.agent.md"
-                ).is_file()
-                or (
-                    github_dir
-                    / "prompts"
-                    / f"speckit.{command}.prompt.md"
-                ).is_file()
-                for command in _COPILOT_CORE_COMMANDS
-            )
-            if has_managed_commands and not has_managed_skills:
-                return False
-        return True
+        return self._skills_mode

    def invoke_separator_for_mode(self, skills_enabled: bool) -> str:
-        """Skills projects render ``/speckit-<cmd>``; commands use ``.``.
+        """Skills projects render ``/speckit-<cmd>``; default markdown ``.``.

        Copilot is dual-layout, so — like Bob — the command-reference
        separator depends on the persisted ``ai_skills`` state rather than a
@@ -254,38 +158,18 @@ class CopilotIntegration(IntegrationBase):
        Copilot skills project consistent with ``build_command_invocation``
        (which emits ``/speckit-<stem>``).
        """
-        return "-" if skills_enabled else "."
+        return "-" if skills_enabled else self.invoke_separator

    @classmethod
    def options(cls) -> list[IntegrationOption]:
-        # Compose with super() so the base class declares --events for this
-        # event-capable integration; otherwise --integration-options
-        # "--events false" is rejected as unknown (#9).
-        opts = super().options()
-        opts.append(
+        return [
            IntegrationOption(
                "--skills",
                is_flag=True,
                default=False,
-                help=(
-                    "Force the default skills layout (.github/skills/), "
-                    "overriding on-disk auto-detection"
-                ),
+                help="Scaffold commands as agent skills (speckit-<name>/SKILL.md) instead of .agent.md files",
            ),
-        )
-        opts.append(
-            IntegrationOption(
-                "--commands",
-                is_flag=True,
-                default=False,
-                help=(
-                    "Scaffold .github/agents/*.agent.md commands with companion "
-                    ".github/prompts/*.prompt.md files instead of the default "
-                    "skills layout"
-                ),
-            ),
-        )
-        return opts
+        ]

    def _resolve_executable(self) -> str:
        """Return the Copilot CLI executable, respecting the env-var override.
@@ -326,8 +210,8 @@ class CopilotIntegration(IntegrationBase):
    def build_command_invocation(self, command_name: str, args: str = "") -> str:
        """Build the native invocation for a Copilot command.

-        Commands mode: agents are not slash-commands — return args as prompt.
-        Skills mode (default): ``/speckit-<stem>`` slash-command dispatch.
+        Default mode: agents are not slash-commands — return args as prompt.
+        Skills mode: ``/speckit-<stem>`` slash-command dispatch.
        """
        if self._skills_mode:
            stem = command_name
@@ -364,11 +248,15 @@ class CopilotIntegration(IntegrationBase):
        if stem.startswith("speckit."):
            stem = stem[len("speckit."):]

-        skills_mode = (
-            self.is_skills_mode(project_root=project_root)
-            if project_root
-            else self._skills_mode
-        )
+        # Detect skills mode from project layout when not set via setup()
+        skills_mode = self._skills_mode
+        if not skills_mode and project_root:
+            skills_dir = project_root / ".github" / "skills"
+            if skills_dir.is_dir():
+                skills_mode = any(
+                    d.is_dir() and (d / "SKILL.md").is_file()
+                    for d in skills_dir.glob("speckit-*")
+                )

        if skills_mode:
            prompt = "/speckit-" + stem.replace(".", "-")
@@ -440,9 +328,7 @@ class CopilotIntegration(IntegrationBase):
        be flagged stale and deleted, destroying user settings (and the file
        the integration still manages).
        """
-        exclusions = super().stale_cleanup_exclusions()
-        exclusions.add(".vscode/settings.json")
-        return exclusions
+        return {".vscode/settings.json"}

    def post_process_skill_content(self, content: str) -> str:
        """Inject shared hook guidance into Copilot skill content.
@@ -460,34 +346,28 @@ class CopilotIntegration(IntegrationBase):
        parsed_options: dict[str, Any] | None = None,
        **opts: Any,
    ) -> list[Path]:
-        """Install Copilot skills or the opt-in commands layout.
+        """Install copilot commands, companion prompts, and VS Code settings.

-        Skills are the default. ``parsed_options["commands"]`` selects
-        ``.agent.md`` files, companion prompts, and the VS Code settings merge.
-        Existing managed command layouts are preserved when no mode is explicit.
+        When ``parsed_options["skills"]`` is truthy, delegates to skills
+        scaffolding (``speckit-<name>/SKILL.md`` under ``.github/skills/``).
+        Otherwise uses the default ``.agent.md`` + ``.prompt.md`` layout.
        """
        parsed_options = parsed_options or {}
-        self._skills_mode = self.is_skills_mode(parsed_options, project_root)
+        self._skills_mode = bool(parsed_options.get("skills"))
        if self._skills_mode:
-            created = self._setup_skills(project_root, manifest, parsed_options, **opts)
-        else:
-            created = self._setup_commands(project_root, manifest, parsed_options, **opts)
+            return self._setup_skills(project_root, manifest, parsed_options, **opts)
+        if "skills" not in parsed_options:
+            _warn_legacy_markdown_default()
+        return self._setup_default(project_root, manifest, parsed_options, **opts)

-        # Install agent runtime events
-        event_files = self.emit_events(
-            project_root, manifest, events=opts.get("events"), parsed_options=parsed_options
-        )
-        created.extend(event_files)
-        return created
-
-    def _setup_commands(
+    def _setup_default(
        self,
        project_root: Path,
        manifest: IntegrationManifest,
        parsed_options: dict[str, Any] | None = None,
        **opts: Any,
    ) -> list[Path]:
-        """Commands mode: .agent.md + .prompt.md + VS Code settings merge."""
+        """Default mode: .agent.md + .prompt.md + VS Code settings merge."""
        project_root_resolved = project_root.resolve()
        if manifest.project_root != project_root_resolved:
            raise ValueError(
@@ -499,10 +379,6 @@ class CopilotIntegration(IntegrationBase):
        if not templates:
            return []

-        from ...presets import PresetResolver
-
-        preset_resolver = PresetResolver(project_root_resolved)
-
        dest = self.commands_dest(project_root)
        dest_resolved = dest.resolve()
        try:
@@ -520,11 +396,7 @@ class CopilotIntegration(IntegrationBase):

        # 1. Process and write command files as .agent.md
        for src_file in templates:
-            resolved_template = preset_resolver.resolve(
-                f"speckit.{src_file.stem}", template_type="command"
-            )
-            source_path = resolved_template or src_file
-            raw = source_path.read_text(encoding="utf-8")
+            raw = src_file.read_text(encoding="utf-8")
            processed = self.process_template(
                raw, self.key, script_type, arg_placeholder,
                project_root=project_root,
@@ -617,7 +489,7 @@ class CopilotIntegration(IntegrationBase):
        """
        try:
            existing = json.loads(dst.read_text(encoding="utf-8"))
-        except (json.JSONDecodeError, UnicodeDecodeError, OSError):
+        except (json.JSONDecodeError, OSError):
            # Cannot parse existing file (likely JSONC with comments).
            # Skip merge to preserve the user's settings, but show
            # what they should add manually.
@@ -38,25 +38,6 @@ class CursorAgentIntegration(SkillsIntegration):

    multi_install_safe = True

-    CANONICAL_TO_NATIVE = {
-        "session_start": "sessionStart",
-        "pre_tool_use": "preToolUse",
-        "post_tool_use": "postToolUse",
-        "session_end": "sessionEnd",
-        "user_prompt_submit": "beforeSubmitPrompt",
-        "stop": "stop",
-    }
-    events_config_file = ".cursor/hooks.json"
-    events_format = "json-flat"
-    # Cursor sessionStart injects a top-level additional_context (snake_case)
-    # field (C13). beforeSubmitPrompt has no context output field (block/allow
-    # only), and plain text on any hook fails Cursor's JSON parse — suppress
-    # everything else.
-    events_context_envelope = {
-        "*": "suppress",
-        "session_start": "additional_context",
-    }
-
    def build_exec_args(
        self,
        prompt: str,
@@ -111,13 +92,11 @@ class CursorAgentIntegration(SkillsIntegration):

    @classmethod
    def options(cls) -> list[IntegrationOption]:
-        opts = super().options()
-        opts.append(
+        return [
            IntegrationOption(
                "--skills",
                is_flag=True,
                default=True,
                help="Install as agent skills (recommended for Cursor)",
-            )
-        )
-        return opts
+            ),
+        ]
@@ -31,27 +31,6 @@ class DevinIntegration(SkillsIntegration):
        "extension": "/SKILL.md",
    }

-    CANONICAL_TO_NATIVE = {
-        "session_start": "SessionStart",
-        "pre_tool_use": "PreToolUse",
-        "post_tool_use": "PostToolUse",
-        "session_end": "SessionEnd",
-        "user_prompt_submit": "UserPromptSubmit",
-        "stop": "Stop",
-    }
-    events_config_file = ".devin/hooks.v1.json"
-    # Devin's hooks.v1.json is a root event map ({"PreToolUse": [...]}) with no
-    # top-level "hooks" wrapper (U2), unlike the settings.json formats. The
-    # json-root-nested writer/remover operate directly on the root event keys.
-    events_format = "json-root-nested"
-    # Devin's hooks protocol is JSON-stdout; additionalContext is the
-    # documented injection field for SessionStart/UserPromptSubmit (C13).
-    events_context_envelope = {
-        "*": "suppress",
-        "session_start": "hookSpecificOutput",
-        "user_prompt_submit": "hookSpecificOutput",
-    }
-
    def build_exec_args(
        self,
        prompt: str,
@@ -76,16 +55,11 @@ class DevinIntegration(SkillsIntegration):

    @classmethod
    def options(cls) -> list[IntegrationOption]:
-        # Compose with super() so the base class declares --events for this
-        # event-capable integration; otherwise --integration-options
-        # "--events false" is rejected as unknown (#8).
-        opts = super().options()
-        opts.append(
+        return [
            IntegrationOption(
                "--skills",
                is_flag=True,
                default=True,
                help="Install as agent skills (default for Devin)",
            ),
-        )
-        return opts
+        ]
@@ -19,31 +19,3 @@ class GeminiIntegration(TomlIntegration):
        "extension": ".toml",
    }
    multi_install_safe = True
-
-    CANONICAL_TO_NATIVE = {
-        "session_start": "SessionStart",
-        "pre_tool_use": "BeforeTool",
-        "post_tool_use": "AfterTool",
-        "session_end": "SessionEnd",
-        # Gemini exposes BeforeAgent for the per-turn prompt-submit lifecycle
-        # point (S6); its own Claude-hook migration maps UserPromptSubmit to
-        # BeforeAgent. Mapping it so extension handlers fire.
-        "user_prompt_submit": "BeforeAgent",
-        "stop": "AfterAgent",
-    }
-    events_config_file = ".gemini/settings.json"
-    events_format = "json-nested"
-    # Gemini mandates JSON-only hook stdout ("silence is mandatory"): plain
-    # text becomes a user-facing systemMessage, never context. Inject via
-    # hookSpecificOutput.additionalContext on the two context events and
-    # suppress stdout everywhere else (C13).
-    events_context_envelope = {
-        "*": "suppress",
-        "session_start": "hookSpecificOutput",
-        "user_prompt_submit": "hookSpecificOutput",
-    }
-    # Gemini measures hook timeouts in milliseconds, unlike Claude/Cursor/Codex
-    # which use seconds. The shared formatter converts via _native_timeout (#7)
-    # so the default 60s becomes 60000ms instead of terminating the dispatcher
-    # after 60ms.
-    events_timeout_unit = "ms"
@@ -53,16 +53,8 @@ class GenericIntegration(MarkdownIntegration):
        """
        parsed_options = parsed_options or {}

-        # Accept a value only when it is non-BLANK. An empty value resolves to
-        # the project root (``project_root / ""``) and a whitespace-only one to
-        # a directory literally named " ", so either would silently scatter
-        # command files instead of failing with the documented "required"
-        # error. ``strip()`` is used ONLY to decide blankness -- the value
-        # itself is returned verbatim, so a deliberate (if unusual) padded
-        # directory name still targets exactly what the user asked for. Both
-        # branches below apply the same rule so they cannot drift apart.
        commands_dir = parsed_options.get("commands_dir")
-        if commands_dir and (not isinstance(commands_dir, str) or commands_dir.strip()):
+        if commands_dir:
            return commands_dir

        # Fall back to raw_options (--integration-options="--commands-dir ...")
@@ -72,13 +64,9 @@ class GenericIntegration(MarkdownIntegration):
            tokens = shlex.split(raw)
            for i, token in enumerate(tokens):
                if token == "--commands-dir" and i + 1 < len(tokens):
-                    candidate = tokens[i + 1]
-                    if candidate.strip():
-                        return candidate
+                    return tokens[i + 1]
                if token.startswith("--commands-dir="):
-                    candidate = token.split("=", 1)[1]
-                    if candidate.strip():
-                        return candidate
+                    return token.split("=", 1)[1]

        raise ValueError(
            "--commands-dir is required for the generic integration"
@@ -121,27 +121,13 @@ class HermesIntegration(SkillsIntegration):
            command_name = src_file.stem  # e.g. "plan"
            skill_name = f"speckit-{command_name.replace('.', '-')}"

-            # Parse frontmatter for description. Locate the closing ``---`` on
-            # its own line rather than with ``raw.split("---", 2)`` — a bare
-            # substring split stops at the first ``---`` *anywhere*, including
-            # one inside a value such as ``description: Separate sections
-            # with ---``, which truncates the frontmatter and drops later keys.
-            # The block between the delimiters is parsed unstripped so trailing
-            # newlines in literal (``|``) block scalars survive.
+            # Parse frontmatter for description
            frontmatter: dict[str, Any] = {}
            if raw.startswith("---"):
-                fm_lines = raw.splitlines(keepends=True)
-                fm_close = next(
-                    (
-                        i
-                        for i in range(1, len(fm_lines))
-                        if fm_lines[i].rstrip() == "---"
-                    ),
-                    None,
-                )
-                if fm_close is not None:
+                parts = raw.split("---", 2)
+                if len(parts) >= 3:
                    try:
-                        fm = yaml.safe_load("".join(fm_lines[1:fm_close]))
+                        fm = yaml.safe_load(parts[1])
                        if isinstance(fm, dict):
                            frontmatter = fm
                    except yaml.YAMLError:
@@ -157,26 +143,10 @@ class HermesIntegration(SkillsIntegration):
                project_root=project_root,
            )
            # Strip the processed frontmatter — we rebuild it for skills.
-            # Scan for the closing ``---`` on its own line rather than
-            # ``split("---", 2)`` so a ``---`` embedded in a value does not
-            # truncate the frontmatter and spill it into the body.
            if processed_body.startswith("---"):
-                body_lines = processed_body.splitlines(keepends=True)
-                close_idx = next(
-                    (
-                        i
-                        for i in range(1, len(body_lines))
-                        if body_lines[i].rstrip() == "---"
-                    ),
-                    None,
-                )
-                if close_idx is not None:
-                    # Keep whatever trails the ``---`` marker on the closing
-                    # line so the body stays byte-for-byte identical to
-                    # ``split("---", 2)[2]`` for well-formed templates.
-                    processed_body = body_lines[close_idx][3:] + "".join(
-                        body_lines[close_idx + 1 :]
-                    )
+                parts = processed_body.split("---", 2)
+                if len(parts) >= 3:
+                    processed_body = parts[2]

            # Select description
            description = frontmatter.get("description", "")
@@ -7,14 +7,13 @@ class KilocodeIntegration(MarkdownIntegration):
    key = "kilocode"
    config = {
        "name": "Kilo Code",
-        "folder": ".kilo/",
-        "commands_subdir": "commands",
+        "folder": ".kilocode/",
+        "commands_subdir": "workflows",
        "install_url": None,
        "requires_cli": False,
    }
    registrar_config = {
-        "dir": ".kilo/commands",
-        "legacy_dir": ".kilocode/workflows",
+        "dir": ".kilocode/workflows",
        "format": "markdown",
        "args": "$ARGUMENTS",
        "extension": ".md",
@@ -59,7 +59,8 @@ class KimiIntegration(SkillsIntegration):

    def post_process_skill_content(self, content: str) -> str:
        """Ensure in-skill cross-command references use Kimi's `/skill:` syntax."""
-        return super().post_process_skill_content(content)
+        content = super().post_process_skill_content(content)
+        return content.replace("/speckit-", "/skill:speckit-")

    @classmethod
    def options(cls) -> list[IntegrationOption]:
@@ -317,30 +318,20 @@ def _is_speckit_generated_skill(skill_dir: Path) -> bool:

    try:
        content = skill_file.read_text(encoding="utf-8")
-    except (OSError, UnicodeError):
+    except OSError:
        return False

    if not content.startswith("---"):
        return False

-    # Locate the closing ``---`` on its own line rather than with
-    # ``content.split("---", 2)`` — a bare substring split stops at the first
-    # ``---`` *anywhere*, including one inside a value such as
-    # ``description: Separate sections with ---``, which truncates the parsed
-    # frontmatter and can drop the metadata block this check relies on (so a
-    # Speckit-generated skill would not be recognized on teardown).
-    lines = content.splitlines(keepends=True)
-    close_idx = next(
-        (i for i in range(1, len(lines)) if lines[i].rstrip() == "---"),
-        None,
-    )
-    if close_idx is None:
+    parts = content.split("---", 2)
+    if len(parts) < 3:
        return False

    try:
        import yaml

-        frontmatter = yaml.safe_load("".join(lines[1:close_idx]))
+        frontmatter = yaml.safe_load(parts[1])
    except Exception:
        return False

--- a/Show More
+++ b/Show More