chore(todo): park clear-palette (no target) and Slack (defer to Messenger unification)

1 files changed, 5 insertions, 5 deletions

diff --git a/todo.org b/todo.org
index c64ada672..add8b9c39 100644
--- a/todo.org
+++ b/todo.org
@@ -430,8 +430,8 @@ Config modules hardcode colors that should come from the theme (audit 2026-06-16
 - =org-faces-config.el:38-103= defface defaults (~36 hex) — the themeable org-faces theme-studio already overrides; decide whether the defaults should derive from the palette too.
 *** TODO [#C] theme-studio: custom view-assignment dropdown with lock indicators :feature:studio:next:
 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.
+*** TODO [#D] theme-studio: move the "clear palette" button :feature:studio:
+Craig dislikes the current placement (it rides with the update-color and palette-generation controls and is too easy to hit by accident, then re-import the JSON to recover) but has no target placement in mind yet (2026-06-25). Parked until a placement idea lands — the earlier "left-align at the color-column level" was a guess, not a decision. When a target exists: layout/CSS change in the palette area (app.js / styles.css), visual, 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
@@ -3772,11 +3772,11 @@ These may override useful defaults - review and pick better bindings:
 - M-S-y yank-media (was overriding yank-pop)
 - M-S-z undo-kill-buffer (was overriding zap-to-char)
 
-** TODO [#C] Slack message buffers in a reused popup window :quick:
+** TODO [#D] Slack message buffers in a reused popup window :quick:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-21
+:LAST_REVIEWED: 2026-06-25
 :END:
-Display slack.el message and thread buffers in a dedicated popup window (side or bottom) and reuse that one window instead of spawning a new window per buffer. Likely a =display-buffer-alist= rule (or popper integration) in =modules/slack-config.el=.
+Display slack.el message and thread buffers in a dedicated popup window (side or bottom) and reuse that one window instead of spawning a new window per buffer. Likely a =display-buffer-alist= rule (or popper integration) in =modules/slack-config.el=. Status (2026-06-25): =cj/slack--display-buffer= already reuses one non-selected window; the remaining piece is a *dedicated* side/bottom window. Craig's call — keep the current reuse behavior for now and fold the dedicated-window placement into the "Unified popup and messenger UX" work (same window-placement decision should cover Slack, not be solved piecemeal here).
 
 ** DOING [#C] google-keep in-editor integration — build, module-to-package :feature:
 v1 (read-only) implemented and tested (Phases 1-3): the gkeepapi Python bridge (=scripts/google-keep/keep-bridge.py=, 12 tests), the elisp core + =cj/keep-refresh= renderer with atomic writes and async make-process (=modules/google-keep-config.el=, 15 ERT tests), un-orphaned under a =C-c k= prefix, graceful warning when gkeepapi/token/auth is missing. The pure JSON-to-org core is kept extractable per the spec. Live fetch needs the one-time gkeepapi + master-token setup — see "Google Keep v1 live setup and first fetch" under Manual testing and validation.