Review findings on #133748 (teknium1 Medium + Low, kvnloo concurring):
- Edit sent confirm_deep_truncate on every submit, so the server gate
never applied to Desktop edits. planConfirmedEdit mirrors
planConfirmedReload: an edit that would archive later user turns asks
the same destructive confirm first. A tail edit or failed-turn edit
asks nothing, and a decline sends nothing. The stale-target retry
re-addresses the same turn and reuses the user's answer.
- The client and server count later user turns differently, so an
under-asking client turned a deep cut into an opaque "Regenerate
failed". submitWithDeepTruncateConfirm handles the server's 4033
refusal by asking once and retrying confirmed. A declined confirm
rolls back silently instead of showing an error toast.
Both apply to the primary chat and session tiles.
c72f4fa1dd