fix: address third round of Copilot review feedback on community_catalog_docs

- Parameterize list_community_extensions(path=) and render_community_extensions_table(path=)
  so callers can supply a custom catalog path without monkeypatching module globals;
  update tests to use explicit path= args instead of unittest.mock.patch (r3244776065)
- Escape raw field values (name, description) with _render_cell() BEFORE composing
  Markdown link syntax [name](url) so a pipe inside a name/description cannot break
  a link target; render_row() no longer re-escapes already-escaped values (r3244829318)
- Fix _format_tags() filter order: clean (replace+strip) first, then filter on the
  cleaned value — a tag like '  |  ' previously passed the filter but produced an
  empty backtick span after pipe removal (r3244829330)
- Update test_tags_containing_pipe: assert row is well-formed (6 pipe separators for
  5-column table), assert id falls back to ext_id when 'id' field is absent (r3244829343)
- Change pytest.raises(Exception) to pytest.raises(json.JSONDecodeError) for the
  malformed JSON test — the broad Exception catch masks unrelated failures (r3244829358)
- render_community_extensions_table() now returns a trailing newline so Markdown
  renderers see a blank line between the last table row and subsequent paragraphs;
  restore footer paragraph in extensions.md that was previously crammed onto same
  line as last table row (r3244829373)
- Update --markdown help text to make 'ignores filters' behavior explicit rather than
  relying on the runtime warning alone (r3244829452)

Author: DyanGalih

.gitattributes

@@ -1,3 +1 @@
 * text=auto eol=lf
-
-.github/workflows/*.lock.yml linguist-generated=true merge=ours -whitespace

.github/dependabot.yml

@@ -1,12 +1,11 @@
-updates:
-- directory: /
-  package-ecosystem: pip
-  schedule:
-    interval: weekly
-- directory: /
-  ignore:
-  - dependency-name: "github/gh-aw-actions/**" # Managed by gh aw compile. Version-locked to the gh-aw compiler; do not bump.
-  package-ecosystem: github-actions
-  schedule:
-    interval: weekly
 version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/codeql.yml

@@ -22,11 +22,11 @@ jobs:
         uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@9e0d7b8d25671d64c341c19c0152d693099fb5ba # v4
+        uses: github/codeql-action/init@68bde559dea0fdcac2102bfdf6230c5f70eb485e # v4
         with:
           languages: ${{ matrix.language }}
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@9e0d7b8d25671d64c341c19c0152d693099fb5ba # v4
+        uses: github/codeql-action/analyze@68bde559dea0fdcac2102bfdf6230c5f70eb485e # v4
         with:
           category: "/language:${{ matrix.language }}"

.github/workflows/lint.yml

@@ -13,28 +13,6 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
-        with:
-          fetch-depth: 1
-
-      - name: Run git diff --check
-        shell: bash
-        env:
-          EVENT_NAME: ${{ github.event_name }}
-          PR_BASE_SHA: ${{ github.event.pull_request.base.sha }}
-          PUSH_BEFORE_SHA: ${{ github.event.before }}
-          GITHUB_SHA: ${{ github.sha }}
-        run: |
-          set -euo pipefail
-
-          if [ "$EVENT_NAME" = "pull_request" ]; then
-            git fetch --no-tags --depth=1 origin "+${PR_BASE_SHA}:refs/checks/pr-base"
-            git diff --check refs/checks/pr-base HEAD
-          elif [ "$PUSH_BEFORE_SHA" = "0000000000000000000000000000000000000000" ]; then
-            git diff-tree --check --no-commit-id --root -r "$GITHUB_SHA"
-          else
-            git fetch --no-tags --depth=1 origin "+${PUSH_BEFORE_SHA}:refs/checks/push-before"
-            git diff --check refs/checks/push-before HEAD
-          fi
 
       - name: Run markdownlint-cli2
         uses: DavidAnson/markdownlint-cli2-action@ded1f9488f68a970bc66ea5619e13e9b52e601cd # v23

.github/workflows/stale.yml

@@ -14,7 +14,7 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10
         with:
           # Days of inactivity before an issue or PR becomes stale
           days-before-stale: 150

AGENTS.md

@@ -379,32 +379,6 @@ Implementation: Extends `YamlIntegration` (parallel to `TomlIntegration`):
 4. Uses `yaml.safe_dump()` for header fields to ensure proper escaping
 5. Sets `context_file = "AGENTS.md"` so the base setup manages the Spec Kit context section there
 
-## Branch Naming Convention
-
-All branches **must** follow this pattern:
-
-```
-<type>/<number>-<short-slug>
-```
-
-Where `<number>` is either an issue number or a PR number — whichever is created first.
-
-| Prefix | When to use | Example |
-|---|---|---|
-| `feat/` | New features | `feat/2342-workflow-cli-alignment` |
-| `fix/` | Bug fixes | `fix/2653-paths-only-validation` |
-| `docs/` | Documentation changes | `docs/2677-branch-naming-convention` |
-| `community/` | Community catalog additions | `community/2492-add-mde-extension` |
-| `chore/` | Maintenance, tooling, CI | `chore/2366-editorconfig` |
-
-**Rules:**
-
-1. Always include the issue or PR number immediately after the prefix — this is what makes branches traceable
-2. Use kebab-case for the slug
-3. Keep the slug short — enough to identify the work without looking up the issue
-
----
-
 ## Common Pitfalls
 
 1. **Using shorthand keys for CLI-based integrations**: For CLI-based integrations (`requires_cli: True`), the `key` must match the executable name (e.g., `"cursor-agent"` not `"cursor"`). `shutil.which(key)` is used for CLI tool checks — mismatches require special-case mappings. IDE-based integrations (`requires_cli: False`) are not subject to this constraint.

CHANGELOG.md

@@ -2,51 +2,6 @@
 
 <!-- insert new changelog below this comment -->
 
-## [0.8.13] - 2026-05-21
-
-### Changed
-
-- fix: while/do-while loop condition reads stale iteration-0 step output (#2662)
-- docs: fix directory hierarchy in README examples (#2639)
-- fix(catalogs): reject boolean priority in extension and preset catalog readers (#2589)
-- Update Agent Governance extension to v1.2.0 (#2659)
-- Add agentic workflows for community catalog submissions (#2655)
-- feat: add self-check tip to check output (#2574)
-- fix(cli): clarify exception diagnostics (#2602)
-- ci: add diff whitespace check (#2572)
-- chore: release 0.8.12, begin 0.8.13.dev0 development (#2648)
-
-## [0.8.12] - 2026-05-20
-
-### Changed
-
-- fix(codex): inject dot-to-hyphen hook command note in Codex skills (#2503)
-- Update Squad Bridge extension to v1.3.0 (#2645)
-- Update Superpowers Implementation Bridge extension to v0.5.0 (#2644)
-- Add Team Assign extension to community catalog (#2642)
-- refactor: migrate extension catalog stack parsing to shared base (#2576)
-- Update Architecture Workflow extension to v1.1.0 (#2588)
--  fix(workflow): support integration: auto to follow project's initialized AI (#2421)
-- Add Superpowers Implementation Bridge extension to community catalog (#2586)
-- Add Interactive HTML Preview extension to community catalog (#2585)
-- chore: release 0.8.11, begin 0.8.12.dev0 development (#2584)
-- Update Agent Governance extension to v1.1.0 (#2583)
-
-## [0.8.11] - 2026-05-15
-
-### Changed
-
-- refactor: extract _version.py from __init__.py (PR-3/8) (#2550)
-- Add Time Machine extension to community catalog (#2580)
-- fix(powershell): ensure UTF-8 templates are written without BOM (#2280)
-- docs: document high-assurance spec workflow (#2518)
-- docs: fix script name in directory tree examples (#2555)
-- Fix preset skill description precedence (#2538)
-- fix(integration): clarify multi-install guidance (#2549)
-- feat: add version feature reporting (#2548)
-- Add Architecture Workflow extension to community catalog (#2565)
-- chore: release 0.8.10, begin 0.8.11.dev0 development (#2562)
-
 ## [0.8.10] - 2026-05-14
 
 ### Changed

CONTRIBUTING.md

@@ -38,7 +38,7 @@ On [GitHub Codespaces](https://github.com/features/codespaces) it's even simpler
 1. Fork and clone the repository
 1. Configure and install the dependencies: `uv sync --extra test`
 1. Make sure the CLI works on your machine: `uv run specify --help`
-1. Create a new branch: `git checkout -b <type>/<number>-<short-slug>` (see [Branch naming](#branch-naming) below)
+1. Create a new branch: `git checkout -b my-branch-name`
 1. Make your change, add tests, and make sure everything still works
 1. Test the CLI functionality with a sample project if relevant
 1. Push to your fork and submit a pull request
@@ -55,20 +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.
 
-### 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:
-
-| Prefix | When to use | Example |
-|---|---|---|
-| `feat/` | New features | `feat/2342-workflow-cli-alignment` |
-| `fix/` | Bug fixes | `fix/2653-paths-only-validation` |
-| `docs/` | Documentation changes | `docs/2677-branch-naming-convention` |
-| `community/` | Community catalog additions | `community/2492-add-mde-extension` |
-| `chore/` | Maintenance, tooling, CI | `chore/2366-editorconfig` |
-
-Including the issue or PR number makes branches traceable — especially useful since the project uses squash merges and `git branch --merged` won't detect merged branches. If you start with a PR (no issue), use the PR number once it's assigned.
-
 ## Development workflow
 
 When working on spec-kit:

README.md

@@ -400,24 +400,23 @@ The produced specification should contain a set of user stories and functional r
 At this stage, your project folder contents should resemble the following:
 
 ```text
-.
-├── .specify
-│   ├── memory
-│   │   └── constitution.md
-│   ├── scripts
-│   │   └── bash
-│   │       ├── check-prerequisites.sh
-│   │       ├── common.sh
-│   │       ├── create-new-feature.sh
-│   │       ├── setup-plan.sh
-│   │       └── setup-tasks.sh
-│   └── templates
-│       ├── plan-template.md
-│       ├── spec-template.md
-│       └── tasks-template.md
-└── specs
-    └── 001-create-taskify
-        └── spec.md
+└── .specify
+    ├── memory
+    │  └── constitution.md
+    ├── scripts
+    │  └── bash
+    │      ├── check-prerequisites.sh
+    │      ├── common.sh
+    │      ├── create-new-feature.sh
+    │      ├── setup-plan.sh
+    │      └── setup-tasks.sh
+    ├── specs
+    │  └── 001-create-taskify
+    │      └── spec.md
+    └── templates
+        ├── plan-template.md
+        ├── spec-template.md
+        └── tasks-template.md
 ```
 
 ### **STEP 3:** Functional specification clarification (required before planning)
@@ -464,31 +463,30 @@ The output of this step will include a number of implementation detail documents
 ```text
 .
 ├── CLAUDE.md
-├── .specify
-│   ├── memory
-│   │   └── constitution.md
-│   ├── scripts
-│   │   └── bash
-│   │       ├── check-prerequisites.sh
-│   │       ├── common.sh
-│   │       ├── create-new-feature.sh
-│   │       ├── setup-plan.sh
-│   │       └── setup-tasks.sh
-│   └── templates
-│       ├── CLAUDE-template.md
-│       ├── plan-template.md
-│       ├── spec-template.md
-│       └── tasks-template.md
-└── specs
-    └── 001-create-taskify
-        ├── contracts
-        │   ├── api-spec.json
-        │   └── signalr-spec.md
-        ├── data-model.md
-        ├── plan.md
-        ├── quickstart.md
-        ├── research.md
-        └── spec.md
+├── memory
+│  └── constitution.md
+├── scripts
+│  └── bash
+│      ├── check-prerequisites.sh
+│      ├── common.sh
+│      ├── create-new-feature.sh
+│      ├── setup-plan.sh
+│      └── setup-tasks.sh
+├── specs
+│  └── 001-create-taskify
+│      ├── contracts
+│      │  ├── api-spec.json
+│      │  └── signalr-spec.md
+│      ├── data-model.md
+│      ├── plan.md
+│      ├── quickstart.md
+│      ├── research.md
+│      └── spec.md
+└── templates
+    ├── CLAUDE-template.md
+    ├── plan-template.md
+    ├── spec-template.md
+    └── tasks-template.md
 ```
 
 Check the `research.md` document to ensure that the right tech stack is used, based on your instructions. You can ask Claude Code to refine it if any of the components stand out, or even have it check the locally-installed version of the platform/framework you want to use (e.g., .NET).