docs(upgrade): document integration upgrade / extension update as the project-files upgrade path#3326
Conversation
51f9b1c to
34f1774
Compare
34f1774 to
29f29a8
Compare
There was a problem hiding this comment.
Pull request overview
Updates the upgrade guide to prioritize the manifest-aware project refresh workflow (integrations + extensions) over full re-init, aligning documentation with the current integration/extension management model in Spec Kit.
Changes:
- Reframes project updates around
specify integration status+specify integration upgrade <key>as the primary upgrade path. - Adds
specify extension updateto the documented project upgrade flow. - Updates constitution guidance to reflect current behavior (preserve existing; only create from template when missing), keeping
specify init --here --force --integration …as a fallback.
Show a summary per file
| File | Description |
|---|---|
| docs/upgrade.md | Rewrites the project upgrade instructions to use integration manifests and extension updates, with updated safety/warnings and scenarios. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Low
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback. If not applicable, please explain why
Assisted-by: OpenAI Codex (model: GPT-5, autonomous)
Assisted-by: OpenAI Codex (model: GPT-5, autonomous)
29f29a8 to
5db8065
Compare
Copilot review follow-upChanges
Validation
Head commit: 5db8065 The two review threads were intentionally left open for the reviewer or PR author to resolve. Posted on behalf of @PascalThuet by OpenAI Codex (model: GPT-5, autonomous). |
|
Please address Copilot feedback |
Assisted-by: Codex (model: GPT-5, autonomous)
|
Addressed the latest Copilot review round. The upgrade guide now points Claude users to Validation: Commit: The review thread remains open for the reviewer or PR author to resolve. Posted on behalf of @PascalThuet by OpenAI Codex (model: GPT-5, autonomous). |
Summary
specify integration upgrade <key>flow.specify integration statusandspecify extension updateto the documented upgrade path.specify init --here --force --integration <your-agent>documented as a fallback recovery path..specify/memory/constitution.mdis preserved, while missing constitution files are created from the template.Why
The upgrade guide currently sends existing projects through
specify init --here --force, even though installed integrations now have manifests that can detect modified managed files and block unsafe overwrites unless--forceis explicit. Projects with multiple integrations or installed extensions also need guidance to refresh each installed integration and then update extensions.Validation
git diff --checknpx markdownlint-cli2 docs/upgrade.mdAI Disclosure
This PR was prepared by OpenAI Codex (model: GPT-5) acting as an AI coding agent on behalf of @PascalThuet.