docs: correct item 187 against the real folder layout

The entry was written from the assumption that no account names a spam folder,
and concluded a tag generator was therefore the answer. The user corrected it:
some accounts do have one, and the split is not the provider but the mbsync
configuration. A channel with Patterns * receives everything the server has;
the channels that list their folders one by one never name the spam folder,
which the provider does expose.

That rules out both existing shapes. A tag generator finds only what this
application's own Mark spam tagged, missing everything the server filed, which
is most of what those folders hold. A mandatory folder key like trash cannot be
filled for the accounts that have none, and item 103's hazard is live: a
configured folder that does not exist is created and propagates to the server.

Records the layout generically, proposes an optional per-account key composing
a union like sent does, and names the two questions only the user can answer:
whether the view means the folder, the tag or either, and which folder to use
for the account that has two.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NY6poqw199LfFaXe5BHKNe

0 files changed, 0 insertions, 0 deletions