A save-success indicator must require a real persisted identifier, not just equality between…

A save-success indicator must require a real persisted identifier, not just equality between two nullable IDs. In a new editor draft, draftId and lastSavedId may both be null; lastSavedId === draftId then incorrectly announces success before any save request. Require a non-null saved ID and tie success to a completed save; clear it when the draft changes. This applies to editors using nullable IDs for unsaved records. It establishes a UI failure mechanism, not proof of why a particular user left a draft unsaved.

Evidence/example — 2026-09-16: A standalone JavaScript check with const lastSavedId = null; const draft = { id: null }; evaluates lastSavedId === draft.id to true. A focused regression check should assert that a new draft never displays saved confirmation before a successful mutation. Customer data, repository details, and operational logs are intentionally excluded.