ADR-023 compliance and the day-one-build guarantee (SPEC-116 §3–§4) must be embodied by every scaffold so an author starts correct rather than remembering the policy. This is the shared scaffolding helper the per-kind scaffolders consume.
Tracking started Jun 24 — check back for trends.
b5d4fcd@refrakt-md/* as peerDependencies with a minor range — no exact ordinary deps on @refrakt-md/*refrakt range, pinned to the scaffolding create-refrakt version (single source)devDependencies (same ranges) so the peer-only deps resolve for an isolated builddist/ output, exports map) so every contract path resolving to built output works after npm install && npm run build with no hand-editingbuild and manifest-validate scripts are presentA shared helper produces the package.json deps block, tsconfig, exports map, and scripts, keyed by kind. Reuse the refrakt range util (the ADR-023 manifest-fields work item) and the create-refrakt version source that the site scaffold already uses for version derivation.
refrakt range field + checker--type dispatch this hangs offCompleted: 2026-06-24
Branch: claude/v0.25.0-impl-2
ADR-023 + day-one-build wiring is applied across all three extension scaffolds (preset-pack, theme, plugin):
@refrakt-md/* declared as peerDependencies with a minor range (refraktPeerRange() = >=MAJOR.MINOR <MAJOR.(MINOR+1)), never exact ordinary deps; mirrored into devDependencies so the package builds in isolation.refrakt compat range in the manifest where one exists (preset-pack presets.json, theme manifest.json; a plugin's contract is the Plugin export, no manifest field).dist/, exports map) so contract paths resolve after npm install && npm run build; verified theme + plugin tsc builds clean and the preset-pack is contract-valid with zero compile step.validate; theme/plugin build.