Skip to content

Update arch extension to v3.0.1 - #76

Merged
bigsmartben merged 3 commits into
mainfrom
community/73-update-arch-v3
Jul 26, 2026
Merged

Update arch extension to v3.0.1#76
bigsmartben merged 3 commits into
mainfrom
community/73-update-arch-v3

Conversation

@bigsmartben

@bigsmartben bigsmartben commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Submitted on behalf of @bigsmartben by Codex (GPT-5, autonomous).

Submission route: pr-template
Source repository: https://github.com/bigsmartben/spec-kit-arch
Source version: 3.0.1
Source commit: 841bc9b7343ea7f2a1389d26a6c0f566b8d86f70
Download URL: https://github.com/bigsmartben/spec-kit-arch/archive/refs/tags/v3.0.1.zip
Catalog type: extension

This direct PR is an explicit maintainer-approved reroute of the issue-template submission in #73 after the Copilot catalog agent could not authenticate.

Verified release

What changed

  • Replace the bundled v2 generation package with the v3.0.1 write-free migration package.
  • Remove retired Schema, validators, setup scripts, templates, PoC/generation documentation, and obsolete setup tests.
  • Keep the two compatibility commands, now using cross-platform Spec Kit command placeholders.
  • Update bundled and community catalog metadata.
  • Add focused component and snapshot contract coverage.
  • Preserve arch as opt-in rather than restoring it to default initialization.

Validation evidence

  • Component standard: PASS, 0 errors.
  • Community integration validation: PASS.
  • pytest extensions/arch/tests/test_extension_contract.py tests/test_arch_templates.py tests/test_extensions.py -q: 331 passed.
  • git diff --check origin/main...HEAD: passed.

Closes #73

Assisted-by: Codex (GPT-5, autonomous)
@bigsmartben
bigsmartben marked this pull request as ready for review July 26, 2026 09:44
Assisted-by: Codex (GPT-5, autonomous)

@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: c99aab5fbe

ℹ️ 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".

"name": "Architecture Command Migration",
"id": "arch",
"description": "Generate or reverse a planning-focused architecture contract that guides downstream Spec Kit plans",
"description": "Redirect retired architecture commands to the Constitution-managed project Architecture lifecycle",

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 Mark the retired commands as read-only

The v3 commands explicitly prohibit inspecting or writing project files (extensions/arch/commands/speckit.arch.generate.md:15 and speckit.arch.reverse.md:15), but this catalog entry still declares effect: read-write. Since docs/community/extensions.md:18-24 defines this field for tooling and specify extension info, users will be shown permissions the extension no longer exercises; change the effect to read-only.

Useful? React with 👍 / 👎.

Comment on lines +222 to +224
"name": "Architecture Command Migration",
"id": "arch",
"description": "Generate or reverse a planning-focused architecture contract that guides downstream Spec Kit plans",
"description": "Redirect retired architecture commands to the Constitution-managed project Architecture lifecycle",

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 Refresh the community documentation row for v3

After changing the catalog name and purpose, docs/community/extensions.md:33 still lists “Architecture Planning Contract” and says the commands generate or reverse an architecture contract. Anyone browsing the documented catalog therefore receives the retired v2 behavior instead of this migration-only behavior; update that row as required by the community update workflow in .github/workflows/add-community-extension.md:206-232.

Useful? React with 👍 / 👎.

"stars": 0,
"created_at": "2026-05-14T00:00:00Z",
"updated_at": "2026-07-06T00:00:00Z"
"updated_at": "2026-07-26T00:00:00Z"

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 Refresh the catalog-level update timestamp

This entry is now dated 2026-07-26, while the catalog-level updated_at at line 3 remains 2026-07-06. That makes the public catalog freshness metadata inaccurate for this release and violates the catalog update procedure in .github/workflows/add-community-extension.md:193-196; refresh the top-level timestamp alongside the entry.

Useful? React with 👍 / 👎.

Assisted-by: Codex (GPT-5, autonomous)
@bigsmartben
bigsmartben merged commit 4564aa9 into main Jul 26, 2026
15 checks passed
@bigsmartben bigsmartben mentioned this pull request Jul 26, 2026
11 tasks
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.

[Extension]: Update arch to v3.0.0

1 participant