Skip to content

[extension] Update Status Report extension to v1.4.2 - #4585

Open
github-actions[bot] wants to merge 11 commits into
mainfrom
update-status-report-extension-c10bcaf92239533c
Open

github-actions[bot] wants to merge 11 commits into
mainfrom
update-status-report-extension-c10bcaf92239533c

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Updates the existing status-report community extension catalog entry to version 1.4.2.

Changes:

  • Updates the pinned download URL and version in extensions/catalog.community.json.
  • Corrects the effect from read-only to read-write and raises the required Spec Kit version to >=1.0.0.
  • Preserves the existing created_at, downloads, and stars values.
  • Refreshes the catalog timestamp and updates the documentation table effect to Read+Write.

Validation results:

  • Issue title uses the required [Extension]: prefix.
  • Extension ID and version formats are valid.
  • The public repository contains extension.yml, README.md, and LICENSE.
  • The pinned archive URL belongs to the submitted repository and uses the v1.4.2 tag; the v1.4.2 GitHub release exists.
  • All required issue checklist items are checked.
  • Catalog JSON parses successfully.

Closes #4519

cc @jwesleye

Generated by 🧩 Add Community Extension from Issue Submission for issue #4519 · 96.4 AIC · ⌖ 37.3 AIC · ⊞ 29.5K ·

Update status-report extension submitted by @jwesleye:
- extensions/catalog.community.json (version, download_url, effect, requires, etc.)
- docs/community/extensions.md community extensions table

Closes #4519

Assisted-by: GitHub Copilot (model: gpt-5.2-codex, autonomous)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mnriem mnriem added the triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review label Sep 15, 2026
mnriem and others added 9 commits September 15, 2026 07:54
* docs: simplify README around three processes

Use one shared setup and independent SDD, bug-fixing, and idea-assessment quickstarts. Consolidate detailed content into the docs and contributor guide, add missing process guides, align Chinese documentation, and preserve navigation without widening the site header.

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

* docs: distinguish agent skills from terminal setup

Explicitly describe workflow steps as skills invoked in the agent chat, while reserving terminal instructions for CLI installation and project or extension setup.

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

---------

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

* Gate speckit.clarify so spec-taxonomy items are not deferred to plan

The command treated "better deferred to planning" as a catch-all, so
agents skipped NFRs, acceptance criteria, and edge cases. Spec hits
must stay question candidates. Defer only implementation method,
tech-stack comparison, or task breakdown.

Fixes #1717

* Bound clarify planning deferral to implementation and tech-stack

The unbounded "better deferred to planning" catch-all is gone. Spec
taxonomy still lives in the command. Stage-gate procedure and defer-ratio
audit belong in an opt-in wrap preset, not core.

* Bound the clarify completion-report Deferred status too.

The candidate-question skip was already limited to implementation method, tech-stack, or task breakdown. The coverage table still called anything "better suited for planning" Deferred. That leftover catch-all is gone, and the test now covers the report.
* fix(integrations): dispatch bob commands via `bob run`

`BobIntegration` never overrode `build_exec_args()`, so it inherited the
`IntegrationBase` no-op returning `None`. Callers read `None` as "this CLI is
unavailable", so every workflow command/prompt step targeting Bob reported
`CLI not found or not installed` even with `bob` on PATH.

`build_command_invocation()` was inherited too, rendering `/speckit.specify`
where skills-mode projects install `.bob/skills/speckit-specify/`.

* fix(integrations): resolve the command layout from the project being dispatched into

`build_command_invocation()` called `effective_invoke_separator()` with no
arguments, so `is_skills_mode()` never reached its disk-detection branch
(bob/__init__.py:223-228) and always returned the fresh-project default.
`dispatch_command()` does receive the workflow project root, but the shared
two-argument `build_command_invocation(command_name, args)` contract -- which
eight integrations implement -- had nowhere to put it.

Two consequences, measured against a real `.bob/commands/speckit.specify.md`
project:

  legacy project, speckit.specify     -> /speckit-specify        (want /speckit.specify)
  skills project, speckit.git.commit  -> /speckit-git.commit     (want /speckit-git-commit)

(a) Every existing Bob 1.x install is dispatched a skills-mode invocation
naming a command it does not have, so the run fails exactly as it did before
dispatch was implemented.

(b) Only the `speckit.` prefix was converted, leaving inner dots. The
installed skill directory is `speckit-git-commit` -- `SkillsIntegration`
derives it with `stem.replace(".", "-")` (base.py:1759) and renders the
invocation the same way (base.py:1649) -- so a dotted extension command names
a skill that does not exist. The two layouts differ in both the separator and
the dot handling: skills flatten every dot, legacy commands keep them.

`_build_dispatch_prompt()` carries the project root from `dispatch_command()`
into invocation building. The base implementation is the call it replaces, so
the other integrations are unaffected; Bob overrides it to resolve the layout
from disk, falling back to the working directory, which is where
`dispatch_command` runs `bob` when no root is given.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TqDT4qTj3sFBeg9tMRiXqZ

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* chore: bump version to 1.0.7

* chore: begin 1.0.8.dev0 development

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* chore: upgrade feature-assess to gh-aw v0.88.7

Regenerate the feature assessment workflow on the current upstream baseline and add positive and negative compatibility checks.

Assisted-by: GitHub Copilot (model: GPT-5.6 Sol, autonomous)

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

* test: assert feature-assess safe output permissions

Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous)

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

* test: enforce feature-assess trigger guards

Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous)

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

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update adrkit extension submitted by @mbeacom:
- extensions/catalog.community.json (version, download_url, compatibility range)
- docs/community/extensions.md community extensions table (no row changes required)

Closes #4571

Assisted-by: GitHub Copilot (model: gpt-5.2-codex, autonomous)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update cosmosdb extension submitted by @TheovanKraay:\n- extensions/catalog.community.json (version, download_url, and timestamps)\n- docs/community/extensions.md community extensions table (already current)\n\nCloses #4579\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>\nAssisted-by: GitHub Copilot (model: gpt-5.2-codex, autonomous)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add openup extension submitted by @anvigo12 to the community catalog and documentation. Closes #4567. Assisted-by: GitHub Copilot (model: gpt-5.2-codex, autonomous)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add openup-governance preset submitted by @anvigo12 to the community catalog and documentation table.

Closes #4568

Assisted-by: GitHub Copilot (model: gpt-5.2-codex, autonomous)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mnriem
mnriem requested a balanced review from Copilot September 15, 2026 22:42
@mnriem
mnriem marked this pull request as ready for review September 15, 2026 22:42
@mnriem
mnriem self-requested a review as a code owner September 15, 2026 22:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes match the validated submission and tagged manifest, preserve existing metrics, and produce valid JSON.

Pull request overview

Updates the Status Report community extension metadata to match its v1.4.2 release.

Changes:

  • Pins v1.4.2 and raises the Spec Kit requirement.
  • Corrects the effect to read-write.
  • Refreshes catalog timestamps and documentation.
File summaries
File Description
extensions/catalog.community.json Updates release metadata, compatibility, effect, and timestamps.
docs/community/extensions.md Updates the displayed effect to Read+Write.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 0
  • Review effort level: Balanced

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Integrate the latest upstream main while preserving the Status Report v1.4.2 update and the newer catalog timestamp.

Assisted-by: GitHub Copilot (model: gpt-6-astra, autonomous)

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

mnriem commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

Resolved the catalog timestamp conflict with current main in f58d40f. Kept the newer catalog timestamp and all intervening catalog additions, while preserving the Status Report v1.4.2 update, read-write effect, Spec Kit >=1.0.0 requirement, and documentation correction.

Posted on behalf of @mnriem by GitHub Copilot (model: gpt-6-astra, autonomous).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated extension-submission triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Extension]: Update Status Report to v1.4.2

5 participants