max / makenotwork

server: describe three tier-1 dashboard panels payout_summary, user_projects and user_support, the first batch off the S4 tab inventory measured today (wiki mnw-server-conversion-plan). Each deletes its template; the Askama half goes where it can. Not every tab converts the same way, and the test is the ETag. payout_summary becomes a mounted screen because its route does nothing but render. user_projects cannot: dashboard_tab_projects answers a conditional GET keyed on the user's cache generation, and quasi::mount has no way to say "304 if the generation has not moved". So it follows project_content instead, which stayed on its Askama handler for the same reason and never wrote down why: the handler and route survive, the template dies, and the panel is fill() inline plus fragment() addressed. user_support takes that shape for the other reason, being one of the four panels the page renders inline. A fill panel keeps screen: None in user_tabs::TABS, since Some(..) means a quasi route owns the address and the strip should leave the region alone. user_projects asserts quasi::PATHS lacks its address so the two cannot drift. Closes three of 736f45a5's 122 spinner-spelling sites: user_support's htmx-indicator, hx-indicator and id="support-spinner" are all Action::awaiting() now. Three things the descriptions say that the templates did not: a failed balance is Readiness::Failed rather than a hand-copied second card; an empty project list and its guide are alternatives rather than an empty role="list" above a box; and a disabled value="" option is not a choice, so the category select offers six rather than seven. Also deletes types::PayoutSummary, six orphaned CSS rules, and the four user-projects-* classes that had no rule anywhere to begin with. 179 lib tests green, fmt and clippy clean. The integration suite belongs on astra and was not run here.