Indent nested runes in site content with refrakt format

The documentation site is the largest body of refrakt content in the repository, and the first place a reader copies examples from. Once WORK-657 can apply SPEC-170 D5 mechanically, run it over the site, so nested runes read as nested and the examples teach the rule.

claude/v0-42-0-planning-ata7nd View source

Criteria completion

Tracking started Oct 22 — check back for trends.

Relationships

ID:SPEC-170Status:shipped

Markdoc sources may be indented

ID:WORK-657Status:done

refrakt format re-indents nested block tags, with a check mode and editor formatting

Priority:highComplexity:moderateMilestone:v0.42.0

ID:v0.42.0Status:complete

v0.42.0 — What a composition can express

claude/v0-42-0-planning-ata7nd current ready

claude/v0-42-0-planning-t31f5e done main done changeset-release/main ready

Oct 22, 07:10 PMf7f9792
Created (ready)by bjornolofandersson

Acceptance Criteria

refrakt format has been run over site/content/, in a commit of its own that contains nothing else
Every changed file parses to the same AST as before, and the site's rendered HTML is byte-identical, asserted once for the whole site
Rune examples inside fences in the docs follow the rule too, where they show nesting
refrakt format --check covers site/content/ in CI from this point
The resolution records how many files changed and confirms that plan/ needed no changes

Approach

The formatter refuses a file whose AST would change, so a refused file is a finding: either the formatter has a bug, or the file relied on the old indentation behaviour. Record each one in the resolution and fix it before the run is committed.

Blocked by

WORK-657

References

SPEC-170: D4, D5.