docs: record items 28-35 from the user's notes, and how to keep them in sync

The backlog is downstream of the user's own notes, which they add to while
using the app. Comparing the two turned up nine entries with no item here,
two of them defects rather than enhancements:

  - Re-adding `unread` after the automatic mark-read counts 2 unsynced
    changes when the mail store is back where it started. The counter
    counts writes and never decrements, so any add-then-remove of the
    same tag inflates it (item 28).
  - The Sync button stays enabled while a background sync holds the lock.
    That was a written constraint of item 27 and shipped unbuilt, which
    is the strongest argument for doing this comparison at all (item 29).

The rest are enhancements: a useful blank right pane, for which the user
has produced the two logo images added here; a default button on the quit
prompt, recorded as needing a repro because the code does set one; Esc to
blank the pane; expiring status messages; a Maildir overview; and an
automatic refresh after a sync.

Item 35 is the one 0.8.0 deliberately did not build. A background sync
reports rather than refreshes, because runCurrentQuery() clears the undo
stack, the selection and the message pane. A non-destructive refresh is
real work, so it is an item rather than a flag.

Item 27 gains its outcome, including that its own proposed approach was
the wrong one: flock -n acquires in order to test, so polling with it
would have caused the exact skips the sync script reports.

CLAUDE.md now carries the reconciliation step, since a note saying "X is
broken" is a bug report that will sit in a personal file indefinitely
unless someone goes looking.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions