[extension] Update Status Report extension to v1.4.2

.github/aw/actions-lock.json

@@ -35,6 +35,11 @@
       "version": "v10.0.1",
       "sha": "20cfd1bf945f4377ade1205e4dbc17946fc9a30d"
     },
+    "github/gh-aw-actions/setup-cli@v0.88.7": {
+      "repo": "github/gh-aw-actions/setup-cli",
+      "version": "v0.88.7",
+      "sha": "5e508589e03a7757a7e05b26e834292f5445bfb6"
+    },
     "github/gh-aw-actions/setup@v0.88.7": {
       "repo": "github/gh-aw-actions/setup",
       "version": "v0.88.7",

.github/workflows/feature-assess.md

@@ -47,7 +47,11 @@ steps:
       python-version: "3.14"
   - name: Install Spec Kit CLI
     continue-on-error: true
-    run: uv pip install --system "${{ github.workspace }}"
+    run: |
+      # Avoid gh-aw treating this local checkout path as a PyPI package.
+      UV_BIN="$(command -v uv)"
+      PIP_SUBCOMMAND=pip
+      "$UV_BIN" "$PIP_SUBCOMMAND" install --system .
   - name: Initialize Spec Kit and install the assess extension
     continue-on-error: true
     working-directory: ${{ github.workspace }}
@@ -109,7 +113,7 @@ the workflow's setup steps, from the checked-out revision (so every run uses the
 exact CLI and bundled `assess` instructions of the workflow commit under
 evaluation). Those steps, in order:
 
-1. `Install Spec Kit CLI` — `uv pip install --system "$GITHUB_WORKSPACE"`,
+1. `Install Spec Kit CLI` — `uv pip install --system .`,
    installing the `specify` entry point into the runner tool cache's Python
    `bin` directory, which the agent container adds to `PATH`.
 2. `Initialize Spec Kit and install the assess extension` — runs

CHANGELOG.md

@@ -2,6 +2,31 @@
 
 <!-- insert new changelog below this comment -->
 
+## [1.0.7] - 2026-09-15
+
+### Changed
+
+- fix(integrations): dispatch bob commands via `bob run` (#4492)
+- Bound speckit.clarify planning deferral to implementation details (#4507)
+- docs: simplify README around three processes (#4591)
+- chore(deps): bump actions/deploy-pages from 5.0.0 to 5.0.1 (#4517)
+- feat: add artifact-owned contribution lookup (#4550)
+- feat: expose hook contributions via specify artifact (#4348)
+- Update DocGuard — CDD Enforcement extension to v0.34.9 (#4545)
+- [extension] Update MAQA — Multi-Agent & Quality Assurance extension to v0.3.1 (#4544)
+- feat: add `specify artifact` introspection (#4305)
+- fix: require explicit refresh for bundle manifest changes (#4477)
+- fix(workflows): harden community submission workflows (#4510)
+- [extension] Add GitHub Issue Triage extension to community catalog (#4539)
+- Fix catalog-latest-url-bypass: require tag-pinned catalog download URLs (#4194)
+- refactor(workflows): let the evaluator report its own leaves (#4274) (#4460)
+- [preset] Add Secure Development Assurance Governance preset (#4513)
+- Add Product Definition as Code (PDaC) extension to community catalog (#4514)
+- feat: add JSON output to preset and extension lists (#4218)
+- docs: exempt repository maintenance workflows from PR throttle (#4499)
+- chore: refresh bug-assess workflow with gh-aw v0.88.7 (#4497)
+- chore: release 1.0.6, begin 1.0.7.dev0 development (#4511)
+
 ## [1.0.6] - 2026-09-10
 
 ### Changed

CONTRIBUTING.md

@@ -11,7 +11,7 @@ These are one time installations required to be able to test your changes locall
 1. Install [Python 3.11+](https://www.python.org/downloads/)
 1. Install [uv](https://docs.astral.sh/uv/) for package management
 1. Install [Git](https://git-scm.com/downloads)
-1. Have an [AI coding agent available](README.md#-supported-ai-coding-agent-integrations)
+1. Have an [AI coding agent available](https://github.github.io/spec-kit/reference/integrations.html)
 
 <details>
 <summary><b>💡 Hint if you are using <code>VSCode</code> or <code>GitHub Codespaces</code> as your IDE</b></summary>
@@ -151,6 +151,27 @@ Including the issue or PR number makes branches traceable — especially useful
 
 ## Development workflow
 
+### Does Spec Kit use Spec Kit?
+
+Yes — we dogfood Spec Kit while developing Spec Kit, especially for substantial
+features and changes to the development workflow. Contributors are asked to test
+relevant changes through the Spec-Driven Development commands. The
+[feature assessment workflow](https://github.com/github/spec-kit/blob/main/.github/workflows/feature-assess.md)
+is currently the automated dogfooding path: its setup uses the CLI from the
+current checkout to initialize Copilot and install the `assess` extension, after
+which Copilot follows the generated assessment skills against feature requests.
+The other agentic workflows currently operate independently of the Specify CLI.
+
+This does not mean every change goes through the full workflow. Small fixes can
+use the normal issue, pull request, review, and test process. Dogfooding
+scaffolding and artifacts under `.github/agents/`, `.github/prompts/`,
+`.github/copilot-instructions.md`, `.grok/`, `.specify/`, and `specs/` are
+intentionally gitignored. The automated assessment workflow is ephemeral and
+neither commits nor pushes its generated Copilot skills, so its output does not
+enter repository history.
+
+### Workflow expectations
+
 When working on spec-kit:
 
 1. Test changes with the `specify` CLI commands (`/speckit.specify`, `/speckit.plan`, `/speckit.tasks`) in your coding agent of choice