docs(mobile): recorded the chip strip's touch floor and the active-chip measurement The active chip was 73x28 against an idle 32x32, so the shorter target was the one the user was already on. The entry carries that measurement and the `.tap-chip` floor now applied to every chip.
docs(panel-tabs): recorded the touch target sizes and what could not be measured The close control was a 20px box inside a 28px chip; the entry carries the measurement, the coarse-pointer sizes chosen and the limit that the WebKit headless viewport does not report `pointer: coarse`, so only the class contract could be pinned.
docs(mobile): recorded the phone drawer's own setting and its empty state The phone's right drawer gained a third navigation setting, and the wiki records why it is a separate axis (a drawer has no rail to put beside it), that its open set is the desktop column's own key, that a restored `layout.mobileRightPanel` must not seed a tab or the home page never appears, and that `home` is what stops the seed effect re-opening a tab the user just closed.
docs(shell): documented the draggable chat column width - Recorded the three measurements that shaped the grip: a strip centred on the column's edge is unreachable because the composer card paints above it; the centred column moves twice the pointer delta; and a drag stores nothing until release. - Noted that `custom` has no CSS rule because its number is the user's, written inline, and that a preset must remove that inline value.
docs: measured the settings pane band height - The sheet's identity bands are one height and the rule under them is continuous; recorded the 55/64/37–44px measurement, why the modal bar carries the safe-area inset and the inner panes do not, and that `band-height.test.tsx` pins the declared height because happy-dom has no layout.
docs(app-shell): record the grouped Appearance category and its new paths - Appearance is a master/detail category: Palette / Shell / Editor / Editor behaviour, with the group table as data and a `Record` section map that refuses to compile without a renderer. - Two measured consequences recorded: the category belongs in the modal's `p-0` list, and an E2E that wants a control outside the first group must click that group row first. - Settings -> Appearance -> Layout is now Settings -> Appearance -> Shell, so every panel-navigation, surface, rules and tray-icon reference follows the category's own path.
docs(app-shell): recorded the borderless rule set and its measured split - Named the rung-to-role table (`/5`–`/12` separators, `/15` panel and chip edges, `/20` card and input outlines, `/25`+ interaction) that decides what `borderless` clears. - Recorded why the rules clear colour instead of width: `box-sizing: border-box` is global, so a zero width would shorten every box by 2px. - Added the measured proof that this is a paint change: the shell went 11 → 1 visible borders and the settings modal 918 → 19 with every panel rect byte-identical. - Documented the four exemptions, the `outline`-over-`box-shadow` rule for dialogs, the resizer's background-painted hairline, and the specificity needed to beat a plugin's `@scope`d sheet.
navbar visibility: a plugin entry is a control the menu can switch - Recorded that the menu was built from the five built-ins, so an installed plugin's entry (`Stats`) had a row in the navbar and no checkbox; the id is `plugin:<pluginId>` and validation has to accept its shape before the bundle reports in. - Recorded the one-resolver rule and the Chromium measurement against the live `stats` plugin.
docs(panel-tabs): record the rail/tabs choice, the working set and the header policy The wiki gains the reasons the tab style cannot be re-derived from the code: that the choice is two per-column settings defaulting to the rail, that the strip is a working set whose tab id IS the panel id, that tabs are per-session state under `layout.<side>PanelTabs` with `home` stored rather than derived, that a session which never opened a tab lands on the home page instead of the rail's default view, and that a tab-style column suppresses only a header whose every element is the view's name. Each entry carries what was measured (the 40px row with `Usage`'s timestamp and no heading; the persisted `{tabs, active, home}` blob; the drag that reordered by pointer) so a future reader does not re-break it.
docs(app-shell): the mobile-view switch lives in the sidebar footer - The top navbar's row is now only the right-side toggle plus the shared cluster; the dev-only layout switch moved to the left column's footer and mirrors the phone footer's "Desktop" control in the same slot.
fix(app-shell): the context ring fills its 24-unit grid at a 2.5-unit stroke Recorded the measurements behind the dial's final geometry, replacing the old claim that ContextRing "keeps its own 18px because it is a dial, not a stroke glyph". That claim was wrong twice over: the 18px dial drew a 2px CSS stroke against the lucide icons' 1.33px ("icon context usage di topnavbar lebih besar dari icon di sebelumnya"), and its full-bleed rim had no room to read next to inline glyphs. The page now states the shipped numbers — 24-unit rim / 16.00 CSS px, radius 10.75, 2.5-unit stroke (1.67 CSS px) — and why the rim exceeds the row's own 20 units: a ring is an OUTLINE carrying the whole graphic in one line, measured at 170 unit² of ink against 141 for refresh-cw and 189 for panel-right, where a 20-unit box fell to 114 and read as too small. It also records that getBBox() is not a valid measure here, because it reports fill geometry and ignores the stroke; every figure comes from rasterising the SVG at 20x and taking the alpha bounding box. And that contextRingGeometry takes the OUTER diameter, which is why the constant is the rim rather than the centreline radius.
docs(sidebar): record why a /skill: turn must count as a message - The 4 KiB scan counted only `"type":"message"` entries, so a chat opened with `/skill:<name>` (a `custom_message` whose content is the expanded SKILL.md) reported `messageCount: 0` and was dropped as header-only. - Measured: 5 chats in one project (0.8-8.6 MB, real titles) missing; the row survived only as the pending `New Session - <timestamp>` row, which expired 30s after the send.
docs(sidebar): record the sort/⋯/timestamp right-rail measurement The action row is outside the list's scroller, so the 8px scrollbar made the rows sit 8px inside the sort icon. The page now states the fix and the measured numbers: `.session-list-gutter` (always-reserved bar, padding = 12px − scrollbar) plus the half-box trailing inset (3px, 4px on touch).
docs(sidebar): recorded the harness filter's placement and forms - The bullet now names the inline position right of Archived and the measured forms behind it, including the 22px Select glyph that keeps the row on one line at the default width. - The old symbol name in the sidebar-chrome bullet is updated to filterRowForms.
docs(sidebar): recorded the harness filter's measured rules - The bullet names the controller state, the dropdown decision and the three rules the component owns, with the measured harness counts that ruled out a chip row.
docs(app-shell): record built-in dock placement and two-way rail drag
docs: record batch delete progress
docs: record the search reveal control
docs: record agent-side session deletion and the batch split
docs: record the composer card's stacking level - The docked composer card now carries `relative z-30`: the generating indicator's spun mark is a compositor layer that painted over the open `@` picker even at `z-50`, and containing the mark on the indicator itself did not fix it. - Record why 30 rather than 10 (the transcript's scroll-to-bottom chip is `z-20`).
docs: note the session row's menu-open cue
docs: recorded the mermaid refresh button and the happy-dom purifier gotcha - The action set is shared by the placeholder and the hydrated block because `applySvg` replaces the innerHTML. - happy-dom's DOMPurify shim drops every `<div>`, so a component test that mounts `MarkdownRenderer` finds no `.mermaid-block`; the click resolution is exported and tested against the raw render instead.
docs(sidebar): record the changes.jsonl phantom-subagent bug A sibling .jsonl is not a subagent transcript by extension: omp writes changes.jsonl into the same directory, so every tool-running session claimed a subagent and drew an empty branch. Measured on 5 sessions in -projects-kabmo. The probe now requires a parentSession header, and the saved verdict is keyed with a rule version so the old true is not read back.
docs(layout): New Session opens the landing on a clean URL Record the rule and the measurement: the primary action used to leave `?sessionId=new-…&folderId=…` and a draft row; it now leaves `location.search === ''` with the landing's workspace picker on screen. Only a workspace's own `+` mints a pending chat.
docs: record the editor.run ownership rule and two test-global leaks App-Shell-and-Layout: a command id that throws on a duplicate must be registered by the runtime when the surface can be mounted twice — the split editor's second pane threw `command "editor.run" is already registered`, and the dev overlay then blocked the next click (measured screenshot: 1280x720). Build-Test-and-Release: `fetch` joins the globals a suite must restore, with the pair that reproduces the CLI suite's 5s timeouts, and the persisted-slice ids a harness mints must be process-wide rather than per-file.
docs(shell): record the composer's icon-only Stop/Send and where its colour lives The pair used to be two filled signal buttons, and the wiki described the fill tokens, the hover mix and the `.composer-action` monochrome repaint. All three are gone: the controls are icon-only now, so the colour had to move onto the glyph. The entry states the part a future reader would otherwise re-break — the token class must sit on the `<svg>`, not the button, because the colour mode's paint rule is stated on `svg.lucide` at (0,2,1) and overwrites a single utility with its hashed hue, while `authorColourRules` keys on the svg's own class — and it records the measured result: transparent box, no shadow, glyph at the solved token, and a disabled Send that keeps opacity 0.4 under the pointer.
docs(shell): the phone's popovers anchor to their trigger Record why the menus are below-first and how the three phone popovers were pinned to the title bar's inset instead of their button, with the 390x844 measurements before and after. `mobileOverlayStyle` no longer exists.
docs: record the split build, the generated stylesheet asset and the DB write path Build-Test-and-Release: two builds and why one cannot split the client without publishing server chunks under `static/`; the shell is a Bun HTML route in development and `dist/client/index.html` in production; the measured bundle figures. App-Shell-and-Layout: the two generated stylesheets are a linked, content-hashed asset, the layer-order reason the link comes first, and the `link[data-theme-css]` repair guard. Runtime-and-Toolchain: WAL with `synchronous=NORMAL` and `writeMany`'s chunked transactions, with the measured per-write costs.
docs(app-shell): record the monochrome composer action fill The composer pair's entry stated red/blue as an unconditional fact. It is the colour mode's statement: monochrome has no hue to say "stop" with, so `.composer-action` repaints both fills as the palette ink and the glyph carries the difference. Adds the measured values read off the running console at 1280x900, and why the rules must stay unlayered.
docs(app-shell): record why a diagram's natural size is its viewBox Mermaid writes `width="100%"` for every diagram type except flowchart and sequence, so `parseFloat(width)` read 100 and the viewer drew the diagram at 100 px before magnifying it. The bullet names the measured sizes per type and the fallback order the fix uses.