max / goingson

Describe the shell: where you can go, and the tab that stays lit The last thing between the port and the document swap. Every screen has been described since 2026-08-21 and nothing on the described side drew a tab bar, so `a0617c03`'s one-commit swap had nowhere to land. `quasi::shell` is the app's furniture. Its nav is `navigation.js`'s TAB_GROUPS and TAB_DEFAULTS transcribed rather than reinvented: Work over Tasks, Projects and Problems; Time over Day, Week, Month, Timer and Events; Messages over Email and Contacts; Settings beside them with nothing inside it. A tab's own action is the view it opens in the shipped app, because a group with nowhere to go would be a control that does nothing. Three of the eleven views in TAB_GROUPS are not places, each for its own reason and each written down. The dashboards and the task drawer are details reached from a row, and TAB_GROUPS only listed them to know which tab stays lit, which is what Screen::at_place says here instead. task-graph is bespoke and stays JavaScript, so it is left out rather than pointed at a route that does not exist and would be a NotFound the first time it was pressed. The board is not a view at all: index.html draws it behind a data-mode toggle inside Tasks, so it marks Tasks while it is showing. Sixteen screens name their place. The coherence check is the test worth reading: it walks every route that answers a screen and demands the nav hold the key it named. A key misspelled at either end is a tab that quietly never lights, the screen still renders and the nav still draws, and nothing else in this tree would see it. Two pieces of the header are unsaid and both are recorded on the module rather than dropped. The sync indicator is exactly a Role::Status panel and has nothing describable to put in one, because its content is settings-sync.js and every sync command awaits a network client. The `?` overlay needs a container quasi-webview emits only alongside a chrome binding, quasicoherent 858be2a6, and binding a key to a route that does not exist to obtain one is the trick that module already refuses. time_tracking::chrome takes the chrome and gives it back now, the way routes takes the router, since the band is no longer the whole of the furniture. The stylesheet draws the two levels the way the shipped header draws them, a tab row then an underline strip, per the 2026-07-28 call against two competing tab rows; it needs no positioning because the renderer emits the nav before the content. navigation.js is paired with the module in the drift table, at zero esc sites. It is the one file in the shell remainder a description replaces rather than makes redundant, and pairing it puts a tab added to the JS and not to the description in front of the check. Closes goingson 24aa5833 and quasicoherent 71aa29b4.