Skip to content

fix: reconcile extension runtime scope for v1.0.1 - #1

Merged
jiezeng2004-design merged 4 commits into
mainfrom
fix/reconcile-runtime-scope-v1.0.1
Jul 14, 2026
Merged

jiezeng2004-design merged 4 commits into
mainfrom
fix/reconcile-runtime-scope-v1.0.1

Conversation

@jiezeng2004-design

Copy link
Copy Markdown
Owner

Summary

  • limit the prepare command to create_goal and import_speckit_tasks
  • state explicitly that preparation writes Goal/Subgoal metadata only and does not execute implementation work or create a lineage
  • keep evidence export limited to get_task_lineage and export_task_evidence_pack
  • bump the extension and installation documentation to v1.0.1

Why

The Spec Kit catalog review on github/spec-kit#3488 correctly identified that the v1.0.0 submission text claimed both commands used only the two export tools, while prepare-evidence.md also invoked Spec Kit task import and an unspecified normal workflow. This change removes the vague workflow step and documents the exact per-command tool boundaries.

Validation

  • changed files are limited to extension.yml, commands/prepare-evidence.md, README.md, and CHANGELOG.md
  • manifest version and install URL are both v1.0.1
  • prepare command names only create_goal and import_speckit_tasks
  • export command remains limited to get_task_lineage and export_task_evidence_pack
  • prepare command explicitly disclaims implementation, lineage creation, and verification

Copilot AI review requested due to automatic review settings July 14, 2026 00:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@jiezeng2004-design
jiezeng2004-design merged commit fd761fd into main Jul 14, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 40ff1921ea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

- `repo_path`: the current project path inside `workspaceRoot`;
- `title`: a concise title derived from the approved specification;
- `goal_description`: a bounded summary of the approved scope and acceptance criteria.
4. Record the returned `goal_id`. Call `import_speckit_tasks` with that `goal_id` and a minimal `spec_kit_json` object containing only:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Pass spec_kit_json as JSON text

When an agent follows this prompt literally, it will pass a nested spec_kit_json object, but PatchWarden v1.5.1 declares that argument as a string and the handler does String(args?.spec_kit_json) before JSON.parse; an object therefore becomes [object Object] and import_speckit_tasks fails instead of importing the Spec Kit tasks. Please instruct the command to serialize the minimal object as JSON text for spec_kit_json.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants