feat: add cross-thread value types and notmuch RAII wrappers

ThreadSummary, MessageRef, and TagChange are plain-value structs that
carry query results across the worker/UI thread boundary via queued
signals. NmHandle<T, Destroy> wraps libnotmuch's C handles (query,
threads, messages, thread, message, tags) so early returns in the
query paths can't leak.

1 files changed, 51 insertions, 0 deletions

diff --git a/src/types.h b/src/types.h
new file mode 100644
index 0000000..da71e19
--- /dev/null
+++ b/src/types.h
@@ -0,0 +1,51 @@
+#pragma once
+
+#include <QDateTime>
+#include <QMetaType>
+#include <QString>
+#include <QStringList>
+
+struct ThreadSummary
+{
+    QString threadId;
+    QString subject;
+    QString authors;
+    QDateTime date;
+    int totalCount = 0;
+    int matchedCount = 0;
+    QStringList tags;
+
+    bool isUnread() const { return tags.contains(QStringLiteral("unread")); }
+    bool isFlagged() const { return tags.contains(QStringLiteral("flagged")); }
+};
+
+struct MessageRef
+{
+    QString messageId;
+    QString filePath;
+    QStringList tags;
+
+    /// True when the message itself matched the user's query, as opposed to
+    /// being pulled in only because a sibling in its thread matched. Drives
+    /// whether it renders expanded or as a stub.
+    bool matched = true;
+};
+
+/// One tag mutation, kept so it can be inverted for undo.
+struct TagChange
+{
+    QStringList messageIds;
+    QStringList added;
+    QStringList removed;
+    QString description;  ///< Shown in the undo action's text.
+
+    TagChange inverted() const
+    {
+        return TagChange{ messageIds, removed, added,
+                          QStringLiteral("Undo %1").arg(description) };
+    }
+};
+
+Q_DECLARE_METATYPE(ThreadSummary)
+Q_DECLARE_METATYPE(MessageRef)
+Q_DECLARE_METATYPE(TagChange)