dotemacs/docs/design/theme-selector-package-faces.org, branch main My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-06-07T23:28:47+00:00 docs(theme-selector): incorporate Codex review into the package-faces spec 2026-06-07T23:28:47+00:00 Craig Jennings c@cjennings.net 2026-06-07T23:28:47+00:00 urn:sha1:ce9844423e0c7bf6e212b7d912a69b68e1704497 I ran spec-response against Codex's review. Added implementation phases, acceptance criteria, the package-face inventory source, and state/export semantics with a source field that distinguishes seeded defaults from user edits from deliberate clears. The inventory is hybrid and split: the generated all-package path is its own phase after org, magit, and elfeed, so the three bespoke apps don't wait on it and the scope-explosion risk Codex flagged stays contained. Two findings I modified with reasons in the dispositions section, the rest accepted. Renamed the spec to -spec.org for the workflow precondition. The rubric is now Ready with caveats, and three decisions stay open for me: the inheritance representation, hybrid-vs-curated-only inventory, and the custom picker timing. docs(theme-selector): fold first-round answers into the package-faces spec 2026-06-07T23:17:57+00:00 Craig Jennings c@cjennings.net 2026-06-07T23:17:57+00:00 urn:sha1:94f1660e2f00d14e9b9e7a1221f6eee8d43b03ca I folded the first-round answers into the tier-3 spec. org now carries its complete defface set instead of an 18-face sample, v1 apps are org, magit, and elfeed, and the generic fallback is a fully editable table so any package can be themed. I answered the inheritance question with an optional inherit field (absolute default, opt-in cascade) and added a custom-color-picker proposal. Two decisions stay open: confirming the inheritance representation and when to build the picker. docs(theme-selector): spec the tier-3 package-faces section 2026-06-07T22:45:54+00:00 Craig Jennings c@cjennings.net 2026-06-07T22:45:54+00:00 urn:sha1:275604c35df1410e5fae28e13507d332370d0756 I spec'd a third tier for the tool: package-specific faces, edited one application at a time, org-mode first. It covers the app dropdown, a per-app face table, a bespoke org-document preview, the theme.json packages schema, and how the build step consumes it. It's awaiting review and ends with five open questions.