max / makenotwork

Describe the project Content panel, closing N12's round-trip filter B4's centrepiece and the close condition makeover-layout N12 had been waiting on: the ticks are a payload the renderer assembles, and the three filter controls are a server round trip rather than a client-side pass over rendered rows. src/quasi/project_content.rs holds the whole panel. A View is the address - search, status, type, sort, direction, open bundles, select-all - so every narrowing tab-project-content.js kept in a closure and re-applied after each swap is a query param that survives one. The bulk bar is the shipped five verbs through Act::over, with Set Price and Add Tag using Act::asking, which is the member that was grown off this exact bar. Inline rename becomes the same shape. Nothing was added to quasi or makeover-layout. Not mounted by quasi: the address carries the project slug and a nest strips its prefix, so the existing axum route serves both renderings and reads QUASI_SCREENS per request. The described writes are registered only under the switch and each answers the panel it happened in. A narrowed panel answers without an ETag: the tag is the project's cache generation and does not move when a filter does. build.rs now writes quasi-selection.js and quasi-clock.js from the renderer's own constants. The shell has named both addresses since S1 and neither file existed, so every page linked scripts that 404ed and the first described bulk bar would have shipped without its count. 23 unit tests, 16 pressed-control integration tests. Parity does not apply to this one and the module says why.