From 7bcf6dad2b1078994346b61531bce281a75519f9 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Mon, 15 Jun 2026 11:15:58 -0500 Subject: docs: move the two docs-root specs into docs/specs/ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Finish the reorg: theme-studio-palette-generator (doing — core planner, UI, and generatortest gate shipped, one refinement open) and theme-studio-semantic-theme-architecture (not-started) lived in docs/ root. Moved both into docs/specs/ with status filenames, ID and STATUS drawers, and id-linked references. Fixed their Related links from ../todo.org to ../../todo.org for the deeper path. --- todo.org | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'todo.org') diff --git a/todo.org b/todo.org index a52011226..140740266 100644 --- a/todo.org +++ b/todo.org @@ -220,7 +220,7 @@ Design import handling for unstructured color sources such as Emacs themes, CSS :PROPERTIES: :LAST_REVIEWED: 2026-06-13 :END: -Spec draft: [[file:docs/theme-studio-palette-generator-spec.org][theme-studio-palette-generator-spec.org]]. +Spec draft: [[id:2df157b8-c7c1-47a9-b080-d9586c6f424c][theme-studio-palette-generator-spec-doing.org]]. Build a constraint-first palette generator for Theme Studio: start from bg/fg, generate editable palette columns in OKLCH, preview candidate columns before applying them, and apply proposals by append/replace/regenerate modes while preserving stable column ids and existing assignments where possible. V1 is palette-only, not automatic face assignment; generator output becomes normal editable columns after apply. @@ -228,7 +228,7 @@ Build a constraint-first palette generator for Theme Studio: start from bg/fg, g :PROPERTIES: :LAST_REVIEWED: 2026-06-14 :END: -Spec draft: [[file:docs/theme-studio-semantic-theme-architecture-spec.org][theme-studio-semantic-theme-architecture-spec.org]]. +Spec draft: [[id:fe980b12-451a-4d8b-a550-d99f9ec49f45][theme-studio-semantic-theme-architecture-spec.org]]. Design a Modus-inspired layered Theme Studio output path: palette data, semantic role mappings, face templates, and a generated theme wrapper. Keep the current flat JSON-to-theme converter as the compatibility/default path while proving a layered, self-contained generated theme. Include advisory semantic rules as a possible validation layer, not v1 enforcement. -- cgit v1.2.3