Last Updated: 5/6/2026
Edge Cases — Manifest
Every link below is a test case. Click each one. If a click 404s, the build crashes, content renders weirdly, or copy-paste from a code sample is corrupted — that’s a finding.
Links
/links—mailto:,tel:, fragment-only, broken link, cross-doc relative, trailing slash- Email link in body text — should pass through unrewritten
- Phone link in body text — same
- Fragment-only — should anchor-scroll, no navigation
Content tree shape
- 4-deep folder — sidebar should still link this
- Folder with only an index, no siblings
- Folder with weird filenames — see the dots variant and the spaces variant
- Compatible MDX —
<Callout>should render
Path mappings
- Path-mapped page — was at
/from-legacy/movedin source. The/from-legacyURL should 404.
Sidebar overrides
- The sidebar lists a
phantom-pageentry that doesn’t exist on disk. Clicking it should 404 (it’s a known limitation of “declared keys are kept verbatim”).
Content patterns
- Images — relative, absolute, mapped, missing
- Tables / HTML / code blocks
- Long page — ~5 kB single file, stress test for Pagefind + Shiki
OpenAPI
/api-happy— minimal valid spec, sanity check/api-multi-line-summary— regression test for theescapeYamlfix; if the build dies, the fix regressed/api-special-chars—<,>,&,|,\in summary text
Site config edges
- Primary hue is
355(red, near the wrap-around point) — if the theme palette breaks, you’ll see it - Path mapping rewrites
from-legacy/→modern/ - Footer mixes regular URLs with
mailto:andtel:— verify they pass through
See TEST_CHECKLIST.md for the full per-test verification list.