My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-06-19T01:42:29+00:00 2026-06-19T01:42:29+00:00 Craig Jennings c@cjennings.net 2026-06-19T01:42:29+00:00 urn:sha1:cac380cf2a2960c97274c6ce3cc8b4ae3feb62d8 A newly-loaded package (or a new built-in face) used to fall into emacs-core because grouping is by name-prefix and an unknown prefix matched nothing. Now the fallback routes by where the defface lives: an elpa face becomes its own package bucket, a built-in face a new emacs-general child. So loading a package and running make face-coverage surfaces it as a fresh TODO bucket instead of an orphan in core. Recognized faces still match their family first, and faces.el/frame.el faces stay in emacs-core. 2026-06-19T01:35:55+00:00 Craig Jennings c@cjennings.net 2026-06-19T01:35:55+00:00 urn:sha1:8f56aced97f128b6b4d4dcf19fe5c1ba43447e6b face-coverage.org was rebuilt by a throwaway /tmp script each time. This makes it reproducible: face-coverage-dump.el dumps every face's name, docstring, and defface file from the live daemon (plus all group docs and package summaries), and face_coverage.py turns that into the tiered worklist (emacs-core / emacs-general / per-package), classifying each face by where its defface lives. make face-coverage regenerates the file; make face-coverage-diff reports the coverage delta against the committed copy. The dump binds coding-system-for-write so writing the docstring JSON never drops into the interactive coding-system prompt. I validated the builder by regenerating and diffing against the hand-built worklist: headings identical, only the intro and one sharper description differ.