max / goingson

Swap the document: the described screens are the app `a0617c03`, ruled (c) by Max 2026-08-21: describe every screen, then swap the document in one commit, and never write a transitional mechanism. This is that commit. The window opens on quasi://localhost/tasks, index.html and every hand-written file under frontend/js/ are gone, and the `quasi` feature is gone with them because there is no longer a second frontend for a feature to choose between. 30,690 lines deleted, 87 files. What survives under frontend/js/ is two scripts build.rs writes out of quasi-webview's own consts. SIX FEATURES WENT OUT WITH IT, and that is the ruling rather than an oversight. Max on `da48cb6d`: "we aren't releasing a build until everything is flipped." Compose, Settings > Sync, Settings > Sharing, Settings > About, Create Backup, the search box and the blocking graph are not described and are not on screen. No build ships in that interval, so the interval is one nobody is in. Each comes back when the reason it was refused is removed; the two that are refused permanently are named in quasi/mod.rs. THE WINDOW IS BUILT IN SETUP, not declared in tauri.conf.json, because a window declared there loads frontendDist and the app is served from a scheme this process registers. `windows` is `[]` now. /tasks is where it opens, which is navigation.js's TAB_DEFAULTS["work"] and where the shipped app opened. TWO BUILD CHECKS LOST THEIR SUBJECT, and they are not the same. check_touch_density is dropped on the instruction the check itself prints for this case: no script here asks a density question any more. check_vocabulary_use is a real hole, and it is left uncalled rather than silenced. It asks which generated classes no markup emits; the markup is quasi-webview's emitter now, in another crate, so it answered "63 of 73 classes are dead" about a stylesheet that is working fine. Raising its high water from 42 to 73 was one line and would have made it report clean about 9,800 lines nobody is reading. Filed as `43a682b0`, with the stylesheet itself as `daac5cc7`. Seven of the ten frontend lint rules go the same way, and the reasoning is in the script: they banned confirm()/alert() in our own JS, counted inline handlers in our own markup, and ran the CHRONIC-XSS escaping gate. That gate existed because screens were built by concatenating strings and every one had to remember esc(). Escaping is typed in Rust at the renderer now, which is what the port was for. commands::notifs deletes here too, on the schedule its own header set: it was the one place the notification registry crossed the IPC boundary, and the described settings screen reads the registry in process. docs/frontend_architecture.md is deleted rather than corrected, because every part of it described the SPA. design-system.md and styleguide.md are bannered and filed as `3c5dae72`; they are half true, and which half is the work. Android has no frontend as of this commit. Its webview cannot read a request body, so a POST arrives with its form dropped and build_mobile_app registers the scheme everywhere else. Not a regression this introduces so much as one it makes visible. 768 tests, no feature flag. Closes goingson `a0617c03`, `7bf95b31`, `da48cb6d`.