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:

claude/v041-plan-runes-keep-content 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

claude/v041-plan-runes-keep-content current confirmed

claude/post-v0.38-roadmap-jb7pie confirmed main confirmed

Oct 9, 02:52 PM33aa1ad
Created (confirmed)by bjornolofandersson
Oct 9, 05:55 AMc14f915
Content editedby Claude
plan: file BUG-035..037 from WORK-634's findings

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.