WORK-658
ID:WORK-658Status:done

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.

Priority:mediumComplexity:simpleMilestone:v0.42.0Source:SPEC-170
claude/v0-42-0-planning-t31f5e View source

Criteria completion

Criteria completion: 5 of 5 (100%) checked; tracking started on Oct 25, no incremental history yet0%25%50%75%100%Oct 25Oct 28

Tracking started Oct 25 — check back for trends.

Relationships

Implements 1
Related 2
Branches 3
claude/v0-42-0-planning-t31f5e current done
main donechangeset-release/main readyclaude/v0-42-0-planning-ata7nd ready
History 3
  1. 5e8aff1
    Content editedby bjornolofandersson
  2. cd2e73b
    Created (done)by bjornolofandersson
  3. f7f9792
    Content editedby Claude
    plan: SPEC-170 D5 indentation rule, WORK-657 refrakt format, WORK-658 si

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.

Resolution

Completed: 2026-10-25

Branch: claude/v0-42-0-planning-t31f5e

What was done

  • 9f7af02: the formatter run alone. 104 of 326 files under site/content re-indented, none refused.
  • 34472fc re-indents runes/surfaces.md. The first run misread it, because a fence there holding {% card %} tags was not escaped (see notes).
  • 803cc1d: rune examples in markdoc/md fences that show nesting were re-indented with formatIndentation and reviewed: 44 fences in 21 files. Nothing outside fence contents changed.
  • refrakt format --check covers site/content in CI (npm run format:md:check, in validate.yml).

Verification

  • AST: every changed file parses to the same AST as before, with the shared parse and as the pipeline parses (escapeFenceTags).
  • Rendered site (vite build, 316 pages, build hashes and the build date normalised): 294 pages byte-identical. The other 22 differ only by tab characters, all inside page source displayed by {% preview source=true %}; that is the formatted source being shown.
  • plan/: not run (see WORK-657).

Notes

The migration exposed three bugs, each fixed in its own commit:

  • 1fc1214: tab-indented markdoc lost its highlighting (@refrakt-md/highlight and the VS Code grammar). preview's source trim()med before dedent.
  • a9bb611: escapeFenceTags did not recognise an indented fence, so its tags were parsed as real tags (caught by validate --deep).
  • 6df4c97: whitespace-only lines inside fences now move with the fence.