Quick self-check

Before treating site work as complete, confirm:

• top-level content/ still contains only .gitkeep,
• export/manifest.yaml still has entries: [],
• actual pages were added under site/content/,
• npm run build-local-components regenerates every ignored local component dist/ directory,
• the Quartz build and its post-build content-tree check succeed,
• every site/content/ folder has a meaningful index.md, and every folder route mirrors that source tree,
• the common reader-header Search remains functional; an ordinary build gives Briefings and Reviews the exact empty states No briefings have been published yet. and No reviews have been published yet. when no approved entries exist; npm run preview:drafts instead shows unlisted review material with an explicit Draft label rendered in a muted, achromatic style (not the accent color); real entries render as a 2-column card grid (1 column below 640px) with format and publication date in the top row, title and optional summary in the body, and field labels below a rule; Briefings accepts only Briefing, Reviews accepts Paper Review|Topic Review, and Concepts retains its functional central Search and honest empty state,
• a field-grouped summary renders each field label as a working link into that field’s ## section on the item’s own page (not swallowed by the card’s whole-card click target), caps each group at three items with a linked “+N more” when a field has more, and a field label absent from FIELD_ANCHORS still renders as plain text rather than breaking the build,
• About, Briefings, Reviews, and Concepts descendants use the reader frame while Operations and Maintenance retain Explorer,
• the About overview omits the updated-date line and secondary section row; its Project, Collections, and Practice groups remain flat ruled rows rather than cards, and each About descendant exposes only its current contextual group,
• a client-side field/date filter (shipped 2026-08-10) sits above the Briefings/Reviews card grid once an index has more than one entry and more than one distinct field; its zero-result view keeps the filters visible and provides a functional reset control,
• homepage Updates show title then secondary date without type, while /about/updates shows title, optional summary, then date · type; both remain ruled lists without cards, badges, or fixed columns,
• public copy does not promise a fixed publication cadence, and reader-visible modifications appear in /about/updates without changing a document’s initial-publication ordering,
• navigation links resolve, and
• the reader header, active project and section states, eyebrows, side/inline Table of Contents, light/dark modes, and narrow/wide layouts remain readable.

See Site maintenance for the rest of the maintenance self-check.