[jeffarnim]

Summary

The nesting lint rule warns that pages more than 3 levels deep under a category won't render in the sidebar, even though ReadMe has supported up to 5 levels of nesting since June 2026. Customers running npx @readme/cli lint on their PRs see warnings for level 4 and 5 pages that do render in their sidebar. For the same reason, readme dev leaves those pages out of the local preview.

This raises the cap for docs and reference from 3 to 5 in both places.

Changes

• src/validators/nesting.js: MAX_DEPTH for docs and reference goes from 3 to 5.
• src/dev/lib/docs.js: the same 3 → 5 change to the preview's copy of the cap, so readme dev renders levels 4 and 5.
• test/validators/nesting.test.js (new): the rule had no tests. They cover:
  • 5 levels under a category, in both docs and reference, are not flagged
  • a 6th level is flagged once per folder, with the new "only 5 will render" message
  • folders under flat directories like recipes/ are still rejected

Notes

• The rule is a warning, so it never failed lint (exit code 1 is for errors only). This fixes noisy PR annotations, not broken CI.
• These caps now have to stay in step with gitto by hand. If the sidebar limit changes again, both files need updating.

Testing

• npx vitest run: 22 files, 286 tests passing
• npx oxfmt --check on the changed files: clean

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable bugs were found.

_{Reviews (1) · Last reviewed commit: "Merge branch 'fix/nesting-cap-5-levels' ..." · Reviewed by Greptile}

Dismissed because a newer commit was pushed; Greptile will re-review the current head.