Brooklyn Nicholson d55a17bd82 refactor(tui): statusbar as 4-mode position (on|off|bottom|top) ... Default is back to 'on' (inline, above the input) — bottom was too far from the input and felt disconnected. Users who want it pinned can opt in explicitly. - UiState.statusBar: boolean → 'on' | 'off' | 'bottom' | 'top' - /statusbar [on|off|bottom|top|toggle]; no-arg still binary-toggles between off and on (preserves muscle memory) - appLayout renders StatusRulePane in three slots (inline inside ComposerPane for 'on', above transcript row for 'top', after ComposerPane for 'bottom'); only the slot matching ui.statusBar actually mounts - drop the input's marginBottom when 'bottom' so the rule sits tight against the input instead of floating a row below - useConfigSync.normalizeStatusBar coerces legacy bool (true→on, false→off) and unknown shapes to 'on' for forward-compat reads - tui_gateway: split compact from statusbar config handlers; persist string enum with _coerce_statusbar helper for legacy bool configs		2026-04-22 15:27:54 -05:00
..
__init__.py	feat: new tui based on ink	2026-04-02 19:07:53 -05:00
entry.py	fix(tui-gateway): dispatch slow RPC handlers on a thread pool (#12546)	2026-04-19 07:47:15 -05:00
render.py	tui: inherit Python-side rendering via gateway bridge	2026-04-05 18:50:41 -05:00
server.py	refactor(tui): statusbar as 4-mode position (on|off|bottom|top)	2026-04-22 15:27:54 -05:00
slash_worker.py	feat: personality	2026-04-08 00:15:15 -04:00