chore(todo): close shipped theme-studio widget tasks

Mark the reduce-width, custom weight/slant dropdown, language-dropdown, and lock-to-leftmost tasks done as dated log entries. Refresh the org-lint follow-up list (current line numbers, plus the broken signel-todo link).

1 files changed, 11 insertions, 2 deletions

diff --git a/todo.org b/todo.org
index 4d25d482e..a0f8950be 100644
--- a/todo.org
+++ b/todo.org
@@ -56,9 +56,10 @@ Tags are additive. For example, a small wrong-behavior fix can be
 =:feature:refactor:=.
 * Emacs Open Work
 ** TODO [#C] todo.org org-lint follow-ups :refactor:
-From the 2026-06-15 lint-org sweep. Each needs a human read — these are judgment items, not mechanical fixes, and the line numbers will drift as todo.org changes.
+From the lint-org sweeps (2026-06-15, refreshed 2026-06-20). Each needs a human read — these are judgment items, not mechanical fixes, and the line numbers drift as todo.org changes.
 - obsolete-properties-drawer — incorrect PROPERTIES drawer contents (lines 8392, 4201, 4023, 65, 55).
-- misplaced-heading — possibly misplaced heading (line 8116).
+- misplaced-heading — possibly misplaced heading (line 8186; was 8116 on the 2026-06-15 sweep).
+- link-to-local-file — link to a non-existent local file "~/code/signel/todo.org" (line 8151). Fix or drop the link.
 
 ** TODO [#B] Un-pin ghostel from 0.33.0 once upstream fixes #422/#423 :bug:
 ghostel is held at 0.33.0 (=ghostel-20260604.2049=, commit 5779a2adceb2) in =modules/term-config.el= to dodge the 0.35.x native-PTY crash. When dakra/ghostel ships a fix for #422 (Linux malloc/signal reentrancy) and #423 (macOS recursive lock), restore =:ensure t= (drop the pin comment) and =package-upgrade ghostel=, then re-run the open-ghostel-in-a-GUI-frame survival check. Watch the two issues for the fixing commit.
@@ -346,6 +347,14 @@ Config modules hardcode colors that should come from the theme (audit 2026-06-16
 The view-assignment dropdown is a plain HTML menu. Make it a custom menu colored like the other custom menus, and have it indicate which assignment views have all their elements locked, so the user knows when a view's assignments are done. From the roam inbox 2026-06-16.
 *** TODO [#C] theme-studio: move the "clear palette" button :feature:studio:next:
 The clear-palette button is too easy to hit by accident (then re-import the JSON to recover). It currently rides with the update-color and palette-generation controls, not with the palette columns. Move it to be left-aligned at the same vertical level as the color-column names. Layout/CSS change in the palette area (app.js / styles.css); visual, so verify by eye. From the roam inbox 2026-06-16.
+*** 2026-06-20 Sat @ 05:53:39 -0400 Tightened the elements-table horizontal layout
+Reduced per-cell padding 12px to 8px across all three tables and shortened the redundant "mode-line-highlight (mode-line hover)" label to "(hover)". The weight/slant narrowing landed with the custom-widget task below. Commit 792e09b5.
+*** 2026-06-20 Sat @ 05:53:39 -0400 Custom weight/slant dropdowns with previews
+Replaced the native weight/slant selects with mkEnumDropdown, themed like the color dropdown. Values are spelled out (semibold not "semi"; unset reads "weight"/"slant"), each popup option previews its own weight or slant, and lock + popup behavior mirrors the color dropdown. Commit 055e0992.
+*** 2026-06-20 Sat @ 05:53:39 -0400 Language dropdown sorted with nav arrows
+Alphabetized the language list with Elisp pinned as the default, and added the ‹ › arrows that step the selection (clamped) reusing stepViewIndex. #langtest gate. Commit be62ae5b.
+*** 2026-06-20 Sat @ 05:53:39 -0400 Moved the lock column to the leftmost position
+Lock cell now sits first in all three tables, ahead of the element/face name; the name sort moved to column 1. From the roam inbox 2026-06-20. Commit 4f869aa1.
 *** VERIFY [#A] theme-studio: deploy-wip button on the browser page :feature:studio:next:
 Needs from Craig: a mechanism choice before I build it. The page is served from file://, so a button can't run make directly. Two options: (a) a tiny localhost helper the page POSTs to (it runs make deploy-wip), or (b) the page writes a watched trigger file that a small daemon/timer picks up. Pick (a) or (b) and I'll implement + test it.
 Add a button on the theme-studio page that runs the make deploy-wip target locally (build WIP.json into the theme, live-reload the daemon). The page is served from file://, so the browser can't run make directly. Needs a local bridge: a tiny localhost helper the button POSTs to, or a watched trigger file the page writes. Pick the mechanism before building. From the roam inbox 2026-06-15.