feat(sent): add a Sent view, flat and by recipient

Adds a `sent` key to [account.*] naming that account's sent folder, and a
Sent button beside the saved queries that composes its query from every
account carrying one. An account without the key is omitted silently, as a
real account may keep no sent mail locally. With no account selected the
button spans all of them; selecting one narrows it through the existing
scope wrap rather than a second path.

Composed at run time rather than shipped as a [queries] entry. A saved query
is one fixed string: it cannot narrow to the selected account, and it goes
stale the moment an account is added or a provider renames a folder.

The design and the measurements behind it are in
docs/superpowers/specs/2026-08-11-sent-mail-design.md. Three things there are
worth repeating here.

The composed path is QUOTED, and that is load-bearing. A real provider nests
its sent folder under a bracketed parent, and "[" and "]" are Xapian syntax:
unquoted, the query parses rather than matches and returns nothing while
looking entirely plausible. Composition happens in one place so there is one
chance to get it right, and a bracketed path is pinned in a test.

Recipients are opt-in per query, which is a performance contract rather than
a preference. notmuch_message_get_header(m, "To") is not served from the
index, it reads the message file: folding every thread of a 4411-thread
inbox took 38.2 seconds against 251 ms for the 601-thread sent view. The
worker skips the walk entirely unless asked, and the refresh path carries the
same flag so a background sync cannot blank the column mid-read. Always
folding is mutation-tested: the data would be right and only the cost wrong,
which nothing else here would notice.

The messages reached through the thread are owned by it and freed with it, so
recipientsOf() holds them raw and finishes while the thread is alive, exactly
as walkReplies does. An NmMessage wrapper there is a double-free.

Sent mail is presented flat, and the pane follows. A message you sent
otherwise drags in the replies you received, so a view labelled Sent shows
conversations rather than what you sent. ThreadListModel::setFlatMode() makes
hasChildren() and ReplyCountRole answer differently and changes nothing else;
runQuery() sets it on EVERY run, so any other query restores the tree on its
way through and the flag cannot outlive the button that set it. The pane
needed its own fix for the same reason: the single-message path depends on a
field only filled when a thread is expanded, which never happens in a flat
list, so loadThread() gained matchedOnly and drops the messages that did not
match instead of rendering them as stubs.

Recipients replace the sender through the existing SendersRole rather than a
new one, so the delegate needs no branch and cannot disagree with the model
about which name a row shows. It falls back to the sender when a To header is
absent or unparseable, since a blank where a name belongs reads as a
rendering fault.

Address parsing uses GMime: a display name may contain a comma, so
"Rossi, Mario" <m@example.org>, info@example.net is two addresses and
splitting reports three. internet_address_list_parse returns NULL for an
empty string, which is a crash if unguarded.

Backlog item 63.

1 files changed, 37 insertions, 0 deletions

diff --git a/src/config.cpp b/src/config.cpp
index 9e223f8..47fadec 100644
--- a/src/config.cpp
+++ b/src/config.cpp
@@ -47,6 +47,37 @@ QString Account::scopedQuery(const QString &query) const
     return QStringLiteral("%1 and (%2)").arg(prefix, query);
 }
 
+QString Account::sentQuery() const
+{
+    if (sent.isEmpty())
+        return QString();
+
+    // The QUOTES are load-bearing, not decoration. A real provider nests its
+    // sent folder under a bracketed parent, "[Provider]/Posta inviata", and
+    // "[" and "]" are Xapian syntax: unquoted, the term is parsed rather than
+    // matched and the query silently returns nothing while looking correct.
+    //
+    // The path is user config and is interpolated into a query, so this is the
+    // only place that composition happens; a caller building it by hand would
+    // be a second chance to forget the quotes.
+    return QStringLiteral("path:\"%1/%2/**\"").arg(maildir, sent);
+}
+
+QString Config::allSentQuery() const
+{
+    // Collect first, join after. Appending "or" per account and trimming the
+    // result is the version that produced the defect this guards: an account
+    // with no sent key contributes an empty term, notmuch accepts the bare
+    // "or" without complaint, and the query quietly means something else.
+    QStringList parts;
+    for (const Account &account : m_accounts) {
+        const QString query = account.sentQuery();
+        if (!query.isEmpty())
+            parts.append(query);
+    }
+    return parts.join(QStringLiteral(" or "));
+}
+
 QString Config::defaultPath()
 {
     const QString base =
@@ -281,6 +312,12 @@ void Config::load(const QString &path)
         account.maildir = settings.value(QStringLiteral("maildir")).toString();
         account.drafts = settings.value(QStringLiteral("drafts")).toString();
 
+        // Optional, and absent for an account that keeps no sent mail locally.
+        // Trimmed because a trailing space would land inside the quoted path
+        // and match nothing, which is invisible in a config file.
+        account.sent =
+            settings.value(QStringLiteral("sent")).toString().trimmed();
+
         // Both optional, and both describe this account's chip in the thread
         // list. An account tag is a different taxonomy from a functional one,
         // saying which mailbox a thread arrived in rather than what state it