For: the bare <ul class="list"> §5's rows sit in, and its category heading is one documented component, not page-local classes waiting in docs/DESIGN.md §5d. Area files under docs/design/areas/ are vocabulary to scripts/design-lint.ts, and parallel pulls never edit the same lines (#4063).
Done:
[ ] docs/design/areas/lists.md (new) names the component and what it is for. For each class, in a code span, it gives the function or page that writes it (find it with grep -rn 'class="[^"]*\b<name>\b' src/web) and the stylesheet that styles it: .list, .cat. Follow docs/design/areas/README.md.
[ ] Each of those classes' own lines leaves §5d in docs/DESIGN.md. Delete only those lines.
[ ] No markup and no stylesheet rule changes; every page looks the same.
[ ] bun scripts/design-lint.ts passes, and so does the test that checks every defined class is documented.
Files: docs/design/areas/lists.md, docs/DESIGN.md (deleting lines in §5d only).
Risk: none; documentation only. A class found with no rule or no markup is named in the pull and left for a retirement issue.
For: the bare
<ul class="list">§5's rows sit in, and its category heading is one documented component, not page-local classes waiting in docs/DESIGN.md §5d. Area files under docs/design/areas/ are vocabulary toscripts/design-lint.ts, and parallel pulls never edit the same lines (#4063).Done:
grep -rn 'class="[^"]*\b<name>\b' src/web) and the stylesheet that styles it:.list,.cat. Follow docs/design/areas/README.md.bun scripts/design-lint.tspasses, and so does the test that checks every defined class is documented.Files: docs/design/areas/lists.md, docs/DESIGN.md (deleting lines in §5d only). Risk: none; documentation only. A class found with no rule or no markup is named in the pull and left for a retirement issue.