docs: the shell rules, each with the number that proves it
UI-SPEC gains the three rules the first installed build established, and each is written with what was measured rather than what was intended. Single instance: five launches, **one process, one window** — checked against the installed build after rebuilding, because a plugin registered in the wrong order fails silently by simply not being reached. Maximize: the window style no longer carries `WS_MAXIMIZEBOX` and still carries `WS_THICKFRAME`, so it is bounded without being frozen — read off the real `HWND` rather than inferred from the config that asked for it. Sidebar-disabled-during-a-plan is recorded beside §8's existing `Ctrl+1..8` rule, since they are the same rule for two input devices and a reader who finds only one will assume the other was an oversight. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
2abfef6a7c
commit
be0f8caa18
1 file changed
+17
@@ -138,6 +138,23 @@ app lands. Counted by hand in the running app, never inferred from the markup.
|
||||
| Fix ruff findings | **3** | ruff tab → *Fix N…* → *Fix* (from a report already on screen; **5** from the landing screen with a folder remembered, which is the owner's ceiling). Cancel holds default focus, so `Enter` without `Tab` cancels. |
|
||||
| Upgrade pip | **2** | *Upgrade pip* → *Upgrade* (Environments is the landing screen, so no tab click). The button appears only when pip is below the 22.2 planner floor — the case the ordinary Updates path cannot fix, because the planner it needs will not run. |
|
||||
|
||||
### Shell rules established by the first installed build (2026-08-13)
|
||||
|
||||
**One window, always.** `tauri-plugin-single-instance` is registered before every other plugin; a
|
||||
second launch unminimizes and focuses the window that exists. Five launches used to give five
|
||||
windows, which is five `AppState`s over one machine — five `Sessions` slots each certain it owned
|
||||
the mutation in flight, and five `PD-RES-003` guards that cannot see each other. Verified: five
|
||||
launches, one process, one window.
|
||||
|
||||
**The sidebar is disabled while `PANEL_PHASES` owns the content area.** Navigating away left the
|
||||
plan parked in Rust with nothing driving it, and the next Update answered `PD-RES-003` about a plan
|
||||
the user could no longer see. §8's `Ctrl+1..8` already refuses while the guard dialog is open; this
|
||||
is the same rule for the panel and for the mouse.
|
||||
|
||||
**The window is bounded at 1600×1100 and cannot be maximized or go fullscreen.** The layout is a
|
||||
fixed sidebar plus one scrolling column; stretched across a 4K panel it is a column of text beside
|
||||
a metre of empty surface. Still resizable, and `minWidth`/`minHeight` are unchanged.
|
||||
|
||||
## 6. Component inventory (prefix `Pd`)
|
||||
|
||||
`PdSidebar`, `PdStatusLine`, `PdEnvSwitcher`, `PdPackageTable` (virtualized), `PdPackageRow`, `PdBadge`, `PdPreviewDiff`, `PdConflictRow` (segmented 3-way), `PdDockBay` (queue), `PdConsoleDrawer`, `PdSummarySheet`, `PdSnapshotTimeline`, `PdHealthReport`, `PdLegalGate`, `PdEmptyState`, `PdOfflineBanner`.
|
||||
|
||||
Reference in new issue
Block a user