Sync scaffold to cli@0.2.0/core@0.3.0 via aipm init --refresh - #10
Merged
Merged
Conversation
… sidecar Bumps the @ai-plugin-marketplace toolkit to the release carrying `aipm init --refresh`, then runs that command to adopt the toolkit-owned scaffold tracking. - aipm init --refresh seeds .aipm/scaffold.json, recording the CI workflow (which is already in sync with the toolkit's canonical render). - .gitignore is intentionally left as-is: the repo's comprehensive .gitignore protects secrets (.env / .env.*), logs, coverage, caches, and scratch/ — none of which the toolkit's current lean render covers. refresh reports it as a conflict and does not touch it. (Follow-up: the toolkit should stop refresh-managing .gitignore and seed a comprehensive default instead, so this stops reporting as a conflict.) - build + validate pass with no artifact drift from the dependency bump.
mike-north
force-pushed
the
refresh-scaffold
branch
from
June 4, 2026 17:58
c817a01 to
187d699
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades the template to the toolkit release carrying
aipm init --refresh(cli@0.2.0,core@0.3.0) and adopts the scaffold sidecar — demonstrating the "re-run codegen to update therepo" loop on the real template.
What I ran
aipm init --refreshoutput:.github/workflows/ci.yml→ unchanged: already matches the toolkit's canonical render; thesidecar (
.aipm/scaffold.json) now records it..gitignore→ conflict, left untouched (intentionally). The repo's comprehensive.gitignoreprotects secrets (
.env/.env.*), logs, coverage, caches, andscratch/. The toolkit'scurrent lean canonical render covers none of those, so overwriting it would be a regression (a
forker could commit a
.env). Refresh's safety guard correctly flags it and does not touchit; the sidecar does not track it.
Verification
aipm build→Built 1 plugin(s), 31 artifact(s).— no artifact drift from the dependency bump.aipm validate→OK — no findings.Follow-up (toolkit)
.gitignoreshouldn't be refresh-managed as a whole file — it's user-extensible, and the leancanonical drops important protections. The toolkit should (a) seed a comprehensive
.gitignoreonaipm initand (b) drop.gitignorefrom the refresh-managed set, so it stops reporting as aconflict here. Tracked separately.