server: wait on the real condition instead of a guessed delay, four sites
Each of the four waited a fixed interval for something it could observe
directly, and the intervals differed by a factor of five for the same
kind of pause.
- dashboard-user's reactivate form guessed 500ms for an in-flight POST.
It is data-after="reload" now, which runs on htmx:after:request and
already refuses a >=400 response. window.reactivateReload goes with it.
- tab-project-settings reloaded 300ms after the response landed, from
inside the r.ok branch that had already proven the write.
- tab-user-media clicked #tab-media 1000ms after remaining.length === 0,
which is itself the settled condition.
- item-upload clicked #tab-files 1500ms after the last entry uploaded.
Closes mnw-server e7a6056b. The fifth site it recorded,
actions-dashboards.js:21, was taken by its screen's conversion.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-28 20:00 UTC