Reference template fixture and scaffold-build CI

SPEC-109 §6,§3 — ship exactly one in-repo reference template as a fixture/worked example, and scaffold-build it in CI so rune-syntax drift can't silently rot a template.

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-094Status:accepted

Theme system foundations for multi-theme development

ID:WORK-451Status:done

Template package format and template.json manifest type

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-452Status:done

create-refrakt framework x purpose axis (--framework and --template)

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-453Status:done

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

Priority:highComplexity:complexMilestone: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

Exactly one in-repo reference template exists, framed as a fixture/worked example (a generic multi-section starter), not a catalog
CI scaffolds it, builds it, and asserts no errors; extended with the SPEC-094 visual-regression harness where applicable
It dogfoods the template.json manifest and is the canonical example third-party authors copy
It stays content-only/generic (sandbox-bearing templates are downstream artifacts, not shipped in-repo)

Approach

Add the template under a fixtures path, authored against the format (WORK-451) and installable via the axis (WORK-452) + apply (WORK-453). Add a CI job that scaffolds + builds it; hook into the existing gallery/regression harness if practical.

Dependencies

WORK-451 — template.json type
WORK-452 — framework × purpose axis
WORK-453 — template apply

References

SPEC-109 §6, §3; SPEC-094