Five `create-refrakt` starters link a nav item to a page that does not exist

Found by WORK-634 (#695), which scaffolds a project in its tests.

The starters ship content/docs/getting-started.md, but five of the six _layout.md files list the nav item as getting-started instead of docs/getting-started:

main View source

Relationships

ID:SPEC-109Status:accepted

Site template packages, manifest, and scaffolding

ID:WORK-634Status:done

A project defines its own composed runes in runes.dir

Priority:highComplexity:complexMilestone:v0.41.0

ID:v0.41.3Status:active

v0.41.3 — A fresh scaffold works

main current fixed

changeset-release/main fixed claude/milestone-v0-41-3-1mzttp fixed main fixed claude/v0-42-0-planning-ata7nd confirmed claude/v041-plan-runes-keep-content confirmed claude/post-v0.38-roadmap-jb7pie confirmed

Steps to Reproduce

npx create-refrakt my-site with the default (SvelteKit) template.
Start the dev server and open any page.

Expected

The nav resolves, and a fresh scaffold builds with no errors or warnings.

Actual

getting-started resolves to no page, and every page reports it.

Fix

Change the nav item to docs/getting-started in the five templates. Also add a scaffold test that builds each template and asserts zero errors, so a template-only drift like this one is caught.

Resolution

Completed: 2026-10-24

Branch: claude/milestone-v0-41-3-1mzttp

What was done

packages/create-refrakt/template{,-astro,-eleventy,-next,-nuxt}/content/_layout.md: nav item getting-started → docs/getting-started.
packages/create-refrakt/test/scaffold-builds.test.ts (new): scaffolds each of the six targets, loads it with createRefraktLoader, and asserts both pages exist, no error-severity diagnostics, and the nav links /docs/getting-started. Fails on main for the SvelteKit starter.
scaffold-project-runes.test.ts: dropped the comment excusing the nav error.

Notes

Changeset: .changeset/scaffold-nav-and-html-plugins.md.