1 files changed, 1 insertions, 60 deletions
diff --git a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
index c376f6e..14a242a 100644
--- a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
+++ b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
@@ -153,7 +153,7 @@ taking that too literally.
 | 84 | A config problem blocks `test_mainwindow` on a modal nobody can dismiss | testing | S | **done** 2026-08-14, unreleased. `showWarnings()` split: the status label stays in the constructor, `main.cpp` raises the modal after `show()` |
 | 85 | Nothing on screen can be searched for by right-clicking it | workflow | M | **done** 2026-08-14, unreleased; see `specs/2026-08-14-search-from-message-design.md`. Split from 78; rebuilt the details dialog as rows |
 | 86 | A right-click search can replace or narrow, but never exclude | workflow | S | **done** 2026-08-14, unreleased; see `specs/2026-08-14-exclude-from-search-design.md`. Follows 85. The `extend` bool became a `SearchMode` enum across four signatures |
-| 89 | A sync moves the list under the user's hands, and the auto-sync skips rather than retries | workflow | M | open; from the 2026-08-15 notes pass. Two faults under one complaint, and the larger half is a design question |
+| 89 | A sync moves the list under the user's hands, and the auto-sync skips rather than retries | workflow | XS | **done** 2026-08-15, unreleased. The timer half only: a skipped auto-sync re-arms instead of giving up. The list-churn half is **dropped**, not built: the user resolved it as a mental-model question, an Unread view is SUPPOSED to be volatile |
 | 90 | A saved-query button clears the account selection | workflow | S | **folded into 93** 2026-08-15. Not fixed in place: the button that misbehaves stops being a saved query at all. See `specs/2026-08-15-builtin-filters-design.md` |
 | 91 | Double-clicking a thread could open it in its own window | workflow | ? | open, unspecified; the user marked it "(?) UX not sure" |
 | 92 | Nothing distinguishes a tag written by a rule from one the user applied | information | ? | open, unspecified; the user asked it as a question, and the answer decides whether it is a display item or a format change across two repos |
@@ -447,65 +447,6 @@ in CLAUDE.md.
 **Size: S**, down from M now that item 85 has built the menus and item 81 the
 seeded dialog.
 
-## 89. A sync moves the list under the user's hands, and the auto-sync skips rather than retries
-
-**Observed (user, notes):** "the auto sync after a delay needs to be reviewed,
-its behavior is not exactly right." Then, more broadly: "the sync in general is
-worth rethinking, as it is now is not polished and shows too many moving parts.
-messages disappearing from views, lists changing while the user is
-interacting." And the workaround the user already found: "setting Inbox as the
-default view mitigates the problem as messages are not removed from the list
-after being read for 2s."
-
-**Two separate faults sit under one complaint**, and only the first is small.
-
-**Cause, the concrete half.** `MainWindow::runAutoSync()`
-(`src/mainwindow.cpp:3213`) returns without rescheduling when a sync is already
-in flight:
-
-```cpp
-if (m_externalSyncBusy || (m_sync && m_sync->isRunning()))
-    return;
-```
-
-The comment beside it argues the edits are not lost, because they reached the
-mail store at edit time and the running sync is "very likely" to carry them.
-Very likely is not always: an edit made after the running mbsync has already
-passed that account's mailbox is not carried, the timer has fired and is not
-re-armed, and nothing arms it again until the next edit. The pending count then
-sits non-zero until a manual sync or the cron job. That is exactly "not exactly
-right", and it is a missing `m_autoSyncTimer->start(delay)` on the skip path
-rather than a redesign. `scheduleAutoSync()` (`:3184`) already re-checks
-everything on the way in, so restarting the timer there is safe by its own
-argument.
-
-**Cause, the larger half.** Nothing to do with the auto-sync: it is what a
-refresh does to the list. The refresh after a sync replaces the result set, and
-a query like `tag:unread` no longer matches a thread the user has just read, so
-rows vanish from under the pointer. Item 35 built the refresh to keep the user's
-place, and it does, but keeping the selection is not the same as keeping the
-row: a thread that has left the result set has nowhere to be kept. The user's
-own mitigation, using an `tag:inbox` view where reading does not change
-membership, is the real diagnosis.
-
-**Approach.** Ship the timer restart on its own, as an XS fix with a test that
-arms the timer while a sync is running and asserts it is still active. Then
-treat the list-churn half as a design question and put it to the user before
-building: the plausible answers (defer a refresh while the pointer is over the
-list, keep a read thread visible until the next explicit query, refresh only
-rows rather than the result set) differ enough in feel that guessing wastes the
-work.
-
-**Constraints.**
-
-- The skip itself must stay. Item 71 requires it and mbsync fails on a second
-  concurrent run; this item restarts the timer, it does not queue a sync.
-- A restart must not turn into a spin against a long external sync. The delay is
-  the debounce interval, and `SyncMonitor` polls `/proc/locks`, so an
-  `m_externalSyncBusy` that never clears would re-arm indefinitely at that
-  interval. Cheap, but say so in the test.
-- Do not restore the pre-0.16.0 behaviour by making the delay negative for the
-  user. `auto_sync_delay_ms` is theirs to set.
 
 ## 94. `pinned` has nothing left to decide once the buttons are built-in