Template apply as add-a-site: copy content, derive dirs, pin deps

SPEC-109 §2–§3 + SPEC-110 §4 (kind: "site") — installing a full-site template adds a site: write the manifest's site SiteConfig, derive the content/sandbox destinations, scaffold-copy the package's trees, and pin the derived deps. This is the heart of the template mechanism.

claude/v0.25.0-workitems View source

Criteria completion

Tracking started Jun 23 — check back for trends.

Relationships

ID:SPEC-109Status:accepted

Site template packages, manifest, and scaffolding

ID:SPEC-110Status:accepted

Theme and template install robustness

ID:SPEC-115Status:accepted

Project asset resolution — the asset: scheme

ID:WORK-446Status:done

Multi-site --site targeting and config read/write helpers

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-445Status:done

Shared install resolver: tarball name, registry passthrough, source-type detection

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-451Status:done

Template package format and template.json manifest type

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-454Status:done

Template asset seeding and bundled sandboxes

Priority:mediumComplexity:moderateMilestone:v0.25.0

ID:WORK-455Status:done

Reference template fixture and scaffold-build CI

Priority:mediumComplexity:moderateMilestone:v0.25.0

claude/v0.25.0-workitems current ready

main done changeset-release/main done claude/v0.25.0-impl-3 done

Jun 23, 07:22 PMa6bdcba
Created (ready)by bjornolofandersson

Acceptance Criteria

Template apply writes the manifest's site SiteConfig into sites.<key> (sites.default/singular for a new project, sites.<name> for a multi-site add), deep-merged per SPEC-115
Content/sandbox destinations are derived from (framework starter layout) × (target site key); the package's content//sandboxes/ are copied in; the resolved contentDir/sandbox.dir are written into the SiteConfig
Deps are derived from site.plugins + site.theme.package and pinned as live dependencies; content is scaffold-copied (author-owned)
Full-site templates seed a new project or new site only (no overlay onto an existing site — the deferred section case)
--site names a new site; collision with an existing site errors (WORK-446)

Approach

Implement the kind: "site" apply branch over the shared resolver (WORK-445) and the multi-site helpers (WORK-446), using the template.json type (WORK-451). Greenfield runs through create-refrakt; add-a-site runs through the install surface — both share this apply.

Dependencies

WORK-451 — template.json type
WORK-445 — shared resolver
WORK-446 — multi-site --site + config helpers

References

SPEC-109 §2, §3; SPEC-110 §4