…ith ui_kit

- composer DockCard: dark mode uses surface-raised + drop shadow to match ui_kit floating feel; light mode keeps ring + shadow-raised
- shell dark tokens: switch from cold gray (#212121/#181818) to warm coffee (#221f1c/#1a1714) so halo blends with composer surface
- titlebar macOS: right half transparent so page halo shows through both titlebar and main continuously
- main content: drop opaque bg-bg-base layers so page-level halo reaches composer surface
- composer width: home and session both 720px / 2xl:920px (was home 720, session 720→920)
- delete cold-gray-era 1px border-t divider in layout.tsx

Move PromptStore/HistoryStore types to prompt-input/store-types.ts and
DOM <-> Parts bidirectional serialization (createPill, isNormalizedEditor,
renderPartsToEditor, parseEditorToParts) to prompt-input/editor-serialize.ts.

Pure functions, no Solid reactivity. Pairs with editor-dom (cursor primitives).
First step of splitting prompt-input.tsx (1602 lines) into business-domain modules.

…ratives.ts

Move 10 imperative side-effect helpers (scrollCursorIntoView, queueScroll,
clearEditor, setEditorText, focusEditorEnd, currentCursor, restoreFocus,
renderEditorWithCursor, getCaretState, escBlur) into a single factory.

All operate via editorRef/scrollRef getters; no Solid reactivity introduced.
PromptInput now destructures the helpers it needs from createEditorImperatives.

Move activeFileTab, recent, and openComment (with its commentInReview helper)
into prompt-input/comment-routing.ts. The factory consumes useSessionLayout/
useFile/useComments/useSync internally, exposing only what PromptInput needs.

This logic was inside the composer historically but routes clicks into the
review side panel — it's not composer-internal.

Move two persisted history stores, historyComments, applyHistoryComments,
applyHistoryPrompt, addToHistory, and navigateHistory into
prompt-input/history-navigation.ts.

History is a self-contained subsystem: persisted entries (normal + shell),
apply logic with comment synchronization, and navigation. setCursorPosition
imports directly from editor-dom (no detour through editor-imperatives).

Adopt PromptStore type from store-types in the main createStore call.

…nput.ts

Move composing/IME signal, handleBlur, composition handlers, reconcile,
the prompt -> DOM reconcile effect, the carry-over effect, handleInput,
and addPart into createEditorInput factory.

For now atOnInput/slashOnInput/closePopover/resetHistoryNavigation are
passed in as direct closures from PromptInput. The next commit extracts
popover-controllers and converts these to a popovers() ref forward to
break the addPart <-> popover-handlers cycle.

Pure functions (parseEditorToParts, isNormalizedEditor, createPill,
createTextFragment, setRangeEdge) are imported directly from editor-
serialize/editor-dom rather than threaded through deps.

Move @ file popover, / command popover (with their useFilteredList instances),
slash auto-scroll effect, the promptProbe testing hook (with its
promptEnabled() guard preserved), and selectPopoverActive into
createPopoverControllers.

Resolve the addPart <-> popover-handlers cycle with a mutable popoversRef:
PromptInput creates editorInput first (passing popoversAccess that throws if
not yet initialized), then creates popovers with editorInput.addPart, then
assigns popoversRef. editorInput's handleInput now calls deps.popovers()
.atOnInput / .slashOnInput.

The throw is intentional — silent fallback would drop @/slash input events
if the assembly order ever regressed. slashPopoverRef typed nullable
(assigned by PromptPopover on mount).

Move handleKeyDown (the 169-line key dispatch switch) into
createPromptKeydownHandler factory. The handler routes events to popover,
history, shell-mode, file-pick, and submit/abort subsystems based on the
key combination.

PromptInput passes 17 deps to the factory, all of which were already
local closures in the handler — preserves behavior verbatim.

Move renderModelControl and renderVariantControl into PromptModelControl
and PromptVariantControl components in prompt-input/model-controls.tsx.
The variants memo moves into PromptVariantControl since it's only consumed
there.

variantOpen state stays in PromptInput (paired with the close-on-disable
effect) and is passed as open/onOpenChange props — splitting that effect
across files would double the disable subscription. PromptVariantControl
exposes onOpenChange (no separate onClose prop, since the underlying
Select doesn't have one); PromptInput's onOpenChange handler calls
restoreFocus when the popover closes.

- prompt-input.tsx: drop ContentPart, useLayout, Popover imports and the
  layout/tabs/view destructured locals — all moved into split modules
- prompt-input.tsx: drop historyComments from createHistoryNavigation
  destructure (only addToHistory and navigateHistory are consumed)
- comment-routing.ts: stop returning activeFileTab from createCommentRouting
  (only used internally by the recent memo, was never consumed externally
  in the original file either)

#440)

Home composer wrapper used max-w-[720px] 2xl:max-w-[920px] inside an outer
max-w-200 (= 800px) cap. The cap shadowed the 2xl branch — at 2xl the popover
was held to 800px even though the inner intent was 920px. Drop the outer cap
and tighten the inner wrapper to max-w-[640px] (matches the skill chips
max-width directly below). Home composer now sits in a 640px column that
visually rhymes with the chip group, while session-internal composer keeps
the existing 720 / 2xl 920 responsive width — narrower home is the design
intent (hero stage vs working strip).

Trim the picker popover to the design intent for slice 10:
- Width 340 → 280 (covers ~95% of popular provider model names without
  truncation; verified empirically across 256 models, see brainstorm width
  calculator).
- Drop the autofocus search bar inside the menu — the ⌘K full-screen picker
  already covers high-frequency search; the popover stays for low-frequency
  quick-switch within ≤ 5 visible models per group.
- Drop the "+ add provider" / sliders icon-button action and the unpaid
  "add more provider" footer CTA. Provider management is a low-frequency
  one-shot action and belongs in settings (⌘,), not in the high-frequency
  quick-switch surface.
- Add provider icon to each model row (left of name) — design preview shows
  it, ModelTooltip alone is not enough at-a-glance.
- Remove now-unused imports (useDialog, useProviders, IconButton, Button,
  Show) and the dialog-bound dismiss kinds ("manage" / "provider"); keep
  popularProviders for sortGroupsBy and Tooltip for the per-row
  ModelTooltip wrapper.

Group/row spacing (group-gap 12, row-gap 2, header 12px / 400) is unchanged
because the underlying List component already aligns with dev's contract;
no overrides needed.

…#440)

Append a thinking-level section to the bottom of the model picker popover,
separated from provider groups by a 1px border-weaker divider + pt-3 to
visually mark the conceptual jump (gap = same layer; line = cross layer).

The section is data-driven against model.variant: it renders only when the
current model exposes at least one variant. The trigger row shows the
section label "思考档位" / "Thinking" and the current variant translated
via translateVariant (default → "默认" / "Default"). Clicking the trigger
opens a nested Kobalte popover to the right (placement="right-start"),
listing ["default", ...variant.list()] as a single-select. Selecting
"default" calls model.variant.set(undefined); selecting any other value
calls .set(rawName), so SDK-side reasoningEffort plumbing is unchanged.

Why nested Kobalte popover (vs inline segmented or absolute div):
- Inline segmented bunches a low-frequency adjustment ("调档") into the
  high-frequency main path ("换模型"); ⌘K already covers high-frequency
  search, so the picker stays for ≤5 quick-switch — the bottom section
  shouldn't compete with model rows for visual budget.
- The flyout placement makes it easy to keep the trigger row visible
  alongside the option being selected, and Kobalte handles the focus /
  outside-click contract correctly when nested inside the outer popover.
- Manual absolute-positioned div would be clipped by the outer
  Kobalte.Content overflow-hidden; nested popover routes through portal.

i18n: add "dialog.model.variant" key in en.ts ("Thinking") and zh.ts
("思考档位"). Variant labels reuse the existing variant-label.ts mapping
(none/minimal/low/medium/high/xhigh/max + default), no new translations
needed.

The ⌘. variant cycle command keybind is unchanged — keyboard users keep
quick cycling without opening the menu.

…(slice 10, issue #440)

The variant (thinking level) selection moved into the model picker popover
in the previous commit. This commit removes the now-redundant standalone
PromptVariantControl button next to the model trigger, and folds the
current variant into the model trigger as an inline indicator
("· {variant i18n}"), so the bottom bar shows one combined picker instead
of two adjacent dropdowns.

model-controls.tsx
- Delete PromptVariantControl entirely (Select-based standalone control)
- PromptModelControl trigger: render "· {translateVariant(current)}" after
  the model name when model.variant.current() is truthy. Default (undefined)
  hides the inline tag — matches the picker popover trigger contract:
  no tag when off, raw-translated label when on.
- Drop unused createMemo, Select imports
- Update file header comment

prompt-input.tsx
- Remove PromptVariantControl from the named import
- Delete the [variantOpen, setVariantOpen] signal — Select component owned
  its own open state from inside model-controls; the parent signal was the
  controlled-mode escape hatch that no longer has a control to drive
- The actionReady close-on-disable createEffect keeps closePopover() and
  setStore("draggingType", null), drops setVariantOpen(false)
- Delete the <PromptVariantControl> JSX block

The ⌘. variant cycle command (model.variant.cycle keybind) is unchanged
in command.tsx; users keep keyboard cycling without a button to click.

Render permission inside the composer DockCard instead of a separate dock
above it, so the permission and input states visually share the same shell.
SessionPermissionDock becomes SessionPermissionContent (no DockPrompt
wrapper); the existing data-component="dock-prompt"[data-kind=permission]
attribute is preserved so the slot CSS still applies.

Adds min-h-[140px] to the composer DockCard for the empty-input minimum.

…#440)

The composer drifted from STANDARDS.md and picker.css contract on a few
details. Rather than tuning each magic number, plug the composer into the
existing contracts so the values come from one place.

- attach: Button + size-7 override → IconButton (L23: ghost icon button is
  one fixed 24×24 token; using IconButton retires five className overrides
  and the unused Button import)
- model picker content: add data-picker-content="" and drop inline radius +
  shadow + bg (L34 / picker.css: surface-base + radius-md + ring-base +
  shadow-floating + padding 4 come from the contract)
- model picker trigger: drop px-1.5 (let Button default 0/8 padding stand;
  the previous 6px override pinched the icon + name + chev row)
- provider icon in trigger: drop opacity-40 + group-hover:opacity-100 +
  will-change/translateZ hacks (preview spec is rest fg-base, not faded)
- composer-bar gap: gap-3 → gap-2 (L33 explicitly locks composer-bar gap
  to 8)
- composer-bar left gap: gap-2 → gap-1 (preview composer-left gap is 4)

Collapse the prior 24/28/32 mixed control system into one tier at 30px
with a 26px dense sub-layer. Industry alignment per shadcn/Material 3/
Carbon/Radix/Primer: icon-only buttons match text-button height as a
square version (30x30), icon SVG remains independent on 16/20/24.

- L23 icon-button: 30x30 square (titlebar-icon 32x30 non-square retained)
- L25 button / L26 input / L34 picker / L35 sidebar row: 30
- Send button: 30 round
- L42 sub-tab pill, L34 chip, filetree row, collapsible arrow,
  diff-hunk line-number icon, file-search inner buttons,
  titlebar-internal pills (worktree badge, project dir): 26
- session-turn-changes-action: rewritten with flex centering, drops the
  line-height: 24 vertical-center hack
- DockCard: drop min-h-[140px] so the empty composer card no longer
  stretches on the home screen
- IconButton call sites: drop redundant size-6 / w-8 h-7 overrides so
  the default 30x30 takes effect

session-row 三点 / sort trigger / workspace 三点 / workspace 新建会话 四个
trailing icon button 从默认 30 降到密集层 26,贴齐 DESIGN.md 新增的
Nesting rule:30 高行内的 trailing 操作降到 26,宿主行保持 30,给
按钮留可见呼吸,避免 sort 跟首条会话粘连、菜单按钮跟行边缘贴死。

… width

- picker.css: clear nested List 0/12 wrapper inside picker context
  (DESIGN.md L30 popover spec is container 4 + item 0/8; List was adding
  a third 12px layer making the highlight float 24px from the edge)
- picker.css: drop sticky group labels in picker (groups are short, sticky
  caused mouse-wheel-scrolled items to be overlapped by the label)
- picker.css: add 4px gap between header and first item now that sticky
  no longer floats the label
- model-picker.tsx: 280 -> 240 width, freed by the padding fix
- model-picker.tsx: thinking-level row stays visible even when the model
  has no variants (trigger disabled, label "default") so the section
  doesn't disappear depending on model

The send/stop button uses theme-aware tokens (--fg-strong / --bg-base)
which mirror across light and dark, breaking the muscle-memory contract
for the primary action button. Lock the colors so light and dark look
visually identical:

- idle/ready: brand orange + white (was: brand orange + bg-base, which
  in dark theme rendered an unreadable dark-page-color icon on orange)
- stopping:   ink #1A1613 + white (was: --fg-strong + --bg-base, which
  in dark theme inverted to bone-white bg + dark icon, mirroring light)

Also enlarge stop-square SVG from 8x8 (21% of button) to 15x15 (40% of
button) to match Claude.ai / ChatGPT proportions; the prior glyph was
hard to read against a 30px circular button.

Theme-locked raw color values are an intentional call-site exception
for affordance buttons and will be added to DESIGN.md deviations.

Manual buttons in the thinking-level secondary popover painted the
browser default :focus ring on mouse open because they bypassed the
picker contract that scopes the ring to :focus-visible. Tagging Content
with data-picker-content and items with data-picker-item / data-selected
routes them through picker.css so mouse-click no longer shows the ring,
keyboard tab still does, and selected/hover states match the rest of
the picker family.

Collapsed widget height is 36 per DESIGN.md (Composer · dock · model menu):
30 chev IconButton centered in a 36 row gives 3px breathing top/bottom and
distinguishes a widget header from a plain control row. Pre-L34 the dock was
a standalone rounded card and 78 over-padded it.

Three coupled fixes:
- Min height 78 -> 36 (two callsites: full() memo and DockSegment max-height
  floor) so the collapsed header matches the spec.
- Progress span and TextReveal: leading-none + items-center. text-13-regular
  inherits line-height-large (150% = 19.5px line-box); CJK glyphs sit in the
  upper portion of the em-box, so flex items-center on the line-box centered
  the box but not the glyphs. Collapsing the line-box to the em-box lets the
  glyphs land on the optical centerline.
- TodoList bottom padding pb-11 -> pb-3. The 44px tail was scaffolding for
  the scroll-stuck gradient overlay (now removed); 12px is enough breathing
  for the last item without leaving a visible empty band on full lists.

text-fg-on-brand is locked to #ffffff for use on the brand-orange surface
and does not invert in dark mode. The context-usage tooltip uses the
default tooltip surface (background: var(--fg-strong); color:
var(--bg-cream)), both tokens auto-invert by scheme. Forcing white text on
top of that produced white-on-light in dark mode (tooltip bg becomes light
cream). Drop the override so spans inherit the tooltip's natural color.

PawWork wants submit-during-busy to land in the followup dock first, then
auto-send when the current turn ends; "send now" steers mid-stream as an
opt-in confirmation. The upstream "steer" mode (immediate submit-during-
busy with no queue UI) was the default, and a sticky migration kept
flipping any stored "queue" value back to "steer", so the followup dock
never appeared when a session was busy.

Flip the default to "queue", drop the queue->steer migration, and replace
it with a one-shot steer->queue pass to clear stored "steer" values from
prior installs (no settings UI ever surfaced this choice, so a stored
"steer" is always a migration artifact, not an explicit user preference).
The followup setting getter and setter no longer rewrite the value.

The "send now" button on the followup dock already calls the same prompt
endpoint that steer mode uses; sendFollowup's actionReady guard checks
status-known, not idle, so manual confirmation can fire mid-stream and
the backend handles the insert.

Followup and Revert duplicated their collapse spring + height observer
+ turn/off/value derivations. Extract them into useDockCollapse so both
docks share one animation contract. Todo keeps its own wiring because
it layers a dockProgress fade on top of the base collapse value.

Also pin DockWidgetHeader at h-[36px] (was h-9). This app sets root
font-size to 13px via `html { font: var(--type-body) }` in theme.css,
so Tailwind's rem-based h-9 resolves to 2.25rem * 13 = 29.25px - short
of the 30px IconButton, which made the chev overflow and clip against
the segment's overflow-y: hidden. DESIGN.md L305 commits to absolute
36px, so absolute-pixel utilities are the honest mapping.

Wrapper around the chev keeps `flex items-center` as a defensive null:
the inline-flex IconButton in a block parent could in theory pull a
line-box descender into the wrapper height; flex eliminates that path.

Commit 81aa587 (joined-card dock refactor) hardcoded dockProgress={1}
on SessionTodoDock and removed the parent-side spring that drove it,
so the dock popped in the moment props.state.dock() flipped true
instead of sliding/fading in from 0.

Restore the mount animation:
- session-composer-region: re-introduce a useSpring tracking dockOpen,
  keep the segment mounted while it animates out (dockMounted memo),
  pass the spring value through as dockProgress.
- session-todo-dock: multiply dock() into the max-height expression
  so the segment slides 0 → collapsed-height (or 0 → full when
  mounting in expanded state), in addition to the existing opacity
  drive that was already wired.

Composer-dock spring options now appear in three places (Todo
collapse, useDockCollapse for Followup/Revert, and segment mount).
Extract them into a single DOCK_MOTION constant in composer/motion.ts
so the contract is referenceable, not scattered. Pinning the value
(0.3s, bounce:0) is the de facto standard across composer springs;
hoisting to a global SPRING_TOKENS tier ladder and wiring spring
through prefers-reduced-motion are tracked in #34.

…e2e assertion

CI typecheck failure: createPopoverControllers returns at.active /
at.setActive / slash.active / slash.setActive verbatim from
useFilteredList, which exposes solid-list's createList signals as
Accessor<string | null> / Setter<string | null>. The factory return
interface declared them as string | undefined, which is not assignable.
Consumer (prompt-input.tsx) already wraps reads with ?? undefined,
confirming the null was always there and the interface was overstated.
Pin the interface to string | null so the types match runtime.

E2E failure: session.spec.ts asserted [data-component="prompt-variant-
control"] is visible, but variant selection has been folded into the
model picker popover (see prompt-input/model-controls.tsx top-of-file
note). The separate variant trigger no longer renders. Drop the stale
assertion.

Critical:
- dock-card: stop concatenating split.class into a single classList key.
  "foo bar" was becoming a literal token and tripping
  Element.classList.toggle (DOMException). Solid merges class+classList
  natively when both are passed; restored to that idiom for DockCard,
  DockSegment, and DockSegmentForm.

Major:
- editor-serialize: skip the block-separator newline when visit() has
  already contributed one (e.g. an empty <div><br></div>). Fixes
  multiline draft round-trips that were inflating "foo\n\nbar" into
  "foo\n\n\nbar".
- model-picker: nested ThinkingLevel popover renders into Kobalte.Portal,
  so its content sits outside the outer Content's DOM subtree. The
  outer popover's onPointerDownOutside fired on every inner-popover
  click and dismissed the model picker. Both popovers carry
  data-picker-content; outer now ignores the dismiss when
  event.target.closest("[data-picker-content]") matches a nested
  picker.
- session-composer-region: permission requests can arrive while
  prompt.ready() is still false (e.g. switching into a session whose
  prompt is hydrating). The hydrate fallback used to show only the
  loading card, leaving the user no way to approve or deny. The
  fallback now renders SessionPermissionContent when a request is
  pending and falls through to the loading card otherwise.
- send-button: SendButtonProps declared style?: JSX.CSSProperties |
  string but the merge silently dropped the string branch. No caller
  passes a string today, so narrow the prop type to JSX.CSSProperties
  to match actual behavior instead of inventing a string-merge code
  path.

Minor:
- keydown: the Enter-without-Shift branch had if (stopping())
  handleSubmit / else handleSubmit — both arms identical, so the
  conditional was dead. Inlined to a single handleSubmit call. The
  stopping accessor stays in scope for the keydown probe.
- popover-controllers: include cmd.source in the custom slash command
  id so workspace + user configs sharing a command name don't collapse
  into one entry under useFilteredList.

Medium (gemini):
- use-dock-collapse: contentRef is now a signal driven by the JSX ref
  callback, and createResizeObserver consumes that signal directly
  rather than running inside a createEffect. Idiomatic and tracks
  ref re-assignment correctly.

Push back:
- model-picker module-level externalOpen / openModelPicker(): the
  signal is a deliberate imperative API consumed by use-session-commands
  and the prompt-input keybind; multi-composer support would require
  reshaping the call surface, not just the state. YAGNI for the single
  composer this app has today; tracked under #34.
- editor-input draft carryover preserves text only: pre-existing
  intentional design from PR #185 (commit ea01514 "carry plain-text
  draft across directory switch"). Cross-workspace pill resolution
  needs workspace-aware path semantics — out of slice 10 scope.

The trigger span used max-w-[7rem] (= 91px in this 13px-rem app), which
truncated common longer names like "DeepSeek V4 Pro" or "Claude Sonnet
4.6" while leaving no min, so neighbor controls (workspace chip, +
button) jumped by the full content-width swing whenever the active
model changed.

Switch to absolute pixels with both bounds: min-w-[80px] gives a
stable floor that swallows the 38-65px range covering common names
like "GPT-5.5", "Kimi K2.6", "GLM-5.1" with a small natural gutter,
without inflating them visibly. max-w-[180px] cleanly fits all
17-character display names with truncate as the safety net beyond.
The neighbor-shift budget tightens from ~140px to ~100px while
short names stop looking padded.

The @max-[28rem]/composer:max-w-0 collapse rule (icon-only mode in
narrow composers) is preserved.

The composer-slice-10 spec asserted boundingBox 32px but the actual
SendButton renders h-[30px] w-[30px] and DESIGN.md commits to the 30
dense tier. The assertion slipped through CI because it lacks the
@smoke tag the smoke job filters on; it would have failed the moment
someone ran the full e2e shard. Caught in external code review.

Push back deferred: openModelPicker() module-level externalOpen as
P3 follow-up — same reasoning as the prior round. The single-composer
path cleans externalOpen on onOpenChange(false), and a multi-composer
fix needs a mounted registry / focus-aware dispatch redesign rather
than a state shape tweak. Tracked under issue #34.