Maintain the redesigned system

Update sequence

• Record both repository revisions and dirty state before each refresh.
• Re-audit the complete effective CSS cascade; later root declarations can supersede earlier values.
• Review changed component interfaces, state ownership, and breakpoints.
• Regenerate only affected fictional specimens, then visually inspect all replacements.
• Preserve stable topic routes and update related links, source references, and the manifest together.
• Keep historical asset mappings for existing URLs, but reference only the current reviewed images in TeachKit pages.
• Run the design-system verifier and inspect phone navigation, theme/viewport filters, palette tabs, and the image overlay.
• Compare source hashes and Git status, stop task-owned previews, and remove disposable source copies.

Acceptance criteria

No fallback fonts, unintended focused skip links, cropped menus, stretched images, unbalanced blank framing, or customer records. Light/dark examples must use their actual palettes. Screenshots remain featured portions with useful context. Every source limitation stays visible until a verified source change resolves it.

Legacy tooling

The old owner-data preparation and old capture entry points are retired. Use the isolated system preparation and capture scripts documented here; do not query live course or student records to refresh this reference.