Observed on v3.18.0: opening /compose/edit/<slug> shows the warning status immediately. Suggests the autosave endpoint is rejecting requests — possibly the same CSRF rotation issue as #101, or a separate auth/probe failure. Didn't deep-dive.
Functionally the form still saves via Save Draft / Update buttons, but the warning makes the form feel broken at first glance. Worth either fixing the autosave path or hiding the warning until autosave has actually failed (rather than rendering it pre-emptively).
Observed on v3.18.0: opening
/compose/edit/<slug>shows the warning status immediately. Suggests the autosave endpoint is rejecting requests — possibly the same CSRF rotation issue as #101, or a separate auth/probe failure. Didn't deep-dive.Functionally the form still saves via Save Draft / Update buttons, but the warning makes the form feel broken at first glance. Worth either fixing the autosave path or hiding the warning until autosave has actually failed (rather than rendering it pre-emptively).