@remit/data-ports 0.0.53 → 0.0.55

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/data-ports",
-  "version": "0.0.53",
+  "version": "0.0.55",
   "type": "module",
   "main": "src/index.ts",
   "types": "src/index.ts",

package/src/conformance/calendar-suggestion.ts

@@ -0,0 +1,293 @@
+import assert from "node:assert/strict";
+import { after, before, describe, test } from "node:test";
+import {
+	CalendarInviteMethod,
+	CalendarSuggestionSource,
+	CalendarSuggestionState,
+	ZoneCertainty,
+} from "@remit/domain-enums";
+import { deriveCalendarSuggestionId } from "../id.js";
+import type { ICalendarSuggestionRepository } from "../interfaces/calendar-suggestion.js";
+import type { PutCalendarSuggestionInput } from "../types.js";
+import type { RepositoryConformanceHarness } from "./harness.js";
+
+const suggestion = (
+	accountConfigId: string,
+	messageId: string,
+	bodyPartId: string,
+	icalUid: string,
+	overrides: Partial<PutCalendarSuggestionInput> = {},
+): PutCalendarSuggestionInput => ({
+	accountConfigId,
+	messageId,
+	bodyPartId,
+	icalUid,
+	sequence: 0,
+	method: CalendarInviteMethod.Request,
+	source: CalendarSuggestionSource.IcalendarPart,
+	summary: "Design review",
+	dtStart: "2026-09-01T10:00:00+02:00",
+	dtEnd: "2026-09-01T11:00:00+02:00",
+	allDay: false,
+	location: "",
+	organizer: "organizer@example.test",
+	zoneCertainty: ZoneCertainty.Explicit,
+	icalData: "BEGIN:VCALENDAR\r\nEND:VCALENDAR\r\n",
+	...overrides,
+});
+
+export function calendarSuggestionRepositoryConformance(
+	harness: RepositoryConformanceHarness<ICalendarSuggestionRepository>,
+): void {
+	describe("ICalendarSuggestionRepository conformance", () => {
+		let repo: ICalendarSuggestionRepository;
+
+		before(async () => {
+			repo = await harness.createRepository();
+		});
+
+		after(() => harness.teardown());
+
+		test("put writes a Pending suggestion under its derived id", async () => {
+			const accountConfigId = harness.makeId();
+			const messageId = harness.makeId();
+			const bodyPartId = harness.makeId();
+
+			const written = await repo.put(
+				suggestion(accountConfigId, messageId, bodyPartId, "uid-1"),
+			);
+
+			assert.equal(
+				written.suggestionId,
+				deriveCalendarSuggestionId(messageId, bodyPartId, "uid-1"),
+			);
+			assert.equal(written.state, CalendarSuggestionState.Pending);
+			assert.equal(written.acceptedCalendarObjectId, "");
+		});
+
+		test("put re-reading the same message converges on one row", async () => {
+			const accountConfigId = harness.makeId();
+			const messageId = harness.makeId();
+			const bodyPartId = harness.makeId();
+
+			await repo.put(
+				suggestion(accountConfigId, messageId, bodyPartId, "uid-1"),
+			);
+			await repo.put(
+				suggestion(accountConfigId, messageId, bodyPartId, "uid-1", {
+					summary: "Design review, moved",
+				}),
+			);
+
+			const rows = await repo.listByMessage(accountConfigId, messageId);
+			assert.equal(rows.length, 1);
+			assert.equal(rows[0]?.summary, "Design review, moved");
+		});
+
+		test("put leaves an answered suggestion answered", async () => {
+			// A re-sync must never walk a decision back to Pending: the user
+			// already added this event to a calendar, and a producer write is not
+			// allowed to un-decide that.
+			const accountConfigId = harness.makeId();
+			const messageId = harness.makeId();
+			const bodyPartId = harness.makeId();
+
+			const written = await repo.put(
+				suggestion(accountConfigId, messageId, bodyPartId, "uid-1"),
+			);
+			await repo.settle(accountConfigId, written.suggestionId, {
+				state: CalendarSuggestionState.Accepted,
+				acceptedCalendarObjectId: "cal-object-1",
+			});
+			await repo.put(
+				suggestion(accountConfigId, messageId, bodyPartId, "uid-1"),
+			);
+
+			const reread = await repo.get(accountConfigId, written.suggestionId);
+			assert.equal(reread.state, CalendarSuggestionState.Accepted);
+			assert.equal(reread.acceptedCalendarObjectId, "cal-object-1");
+		});
+
+		test("get rejects a suggestion that is not there", async () => {
+			const accountConfigId = harness.makeId();
+			await assert.rejects(
+				() => repo.get(accountConfigId, harness.makeId()),
+				(error: unknown) => harness.isNotFoundError(error),
+			);
+		});
+
+		test("get scopes to the account config", async () => {
+			const accountConfigId = harness.makeId();
+			const written = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "uid"),
+			);
+
+			await assert.rejects(
+				() => repo.get(harness.makeId(), written.suggestionId),
+				(error: unknown) => harness.isNotFoundError(error),
+			);
+		});
+
+		test("listByMessage returns every suggestion one message produced", async () => {
+			const accountConfigId = harness.makeId();
+			const messageId = harness.makeId();
+			const other = harness.makeId();
+
+			await repo.put(
+				suggestion(accountConfigId, messageId, harness.makeId(), "uid-a"),
+			);
+			await repo.put(
+				suggestion(accountConfigId, messageId, harness.makeId(), "uid-b"),
+			);
+			await repo.put(
+				suggestion(accountConfigId, other, harness.makeId(), "uid-c"),
+			);
+
+			const rows = await repo.listByMessage(accountConfigId, messageId);
+			assert.deepEqual(rows.map((row) => row.icalUid).sort(), [
+				"uid-a",
+				"uid-b",
+			]);
+		});
+
+		test("listByState returns only the state asked for", async () => {
+			const accountConfigId = harness.makeId();
+			const pending = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "p"),
+			);
+			const declined = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "d"),
+			);
+			await repo.settle(accountConfigId, declined.suggestionId, {
+				state: CalendarSuggestionState.Declined,
+				acceptedCalendarObjectId: "",
+			});
+
+			const page = await repo.listByState(
+				accountConfigId,
+				CalendarSuggestionState.Pending,
+			);
+			assert.deepEqual(
+				page.items.map((row) => row.suggestionId),
+				[pending.suggestionId],
+			);
+		});
+
+		test("listByState scopes to the account config", async () => {
+			const accountConfigId = harness.makeId();
+			await repo.put(
+				suggestion(harness.makeId(), harness.makeId(), harness.makeId(), "x"),
+			);
+
+			const page = await repo.listByState(
+				accountConfigId,
+				CalendarSuggestionState.Pending,
+			);
+			assert.equal(page.items.length, 0);
+		});
+
+		test("listByState pages, and the token resumes where the page stopped", async () => {
+			const accountConfigId = harness.makeId();
+			for (const uid of ["a", "b", "c"]) {
+				await repo.put(
+					suggestion(accountConfigId, harness.makeId(), harness.makeId(), uid),
+				);
+			}
+
+			const first = await repo.listByState(
+				accountConfigId,
+				CalendarSuggestionState.Pending,
+				{ limit: 2 },
+			);
+			assert.equal(first.items.length, 2);
+			assert.ok(first.continuationToken);
+
+			const second = await repo.listByState(
+				accountConfigId,
+				CalendarSuggestionState.Pending,
+				{ limit: 2, continuationToken: first.continuationToken },
+			);
+			const seen = [...first.items, ...second.items].map(
+				(row) => row.suggestionId,
+			);
+			assert.equal(new Set(seen).size, 3);
+		});
+
+		test("settle records the accepted resource", async () => {
+			const accountConfigId = harness.makeId();
+			const written = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "uid"),
+			);
+
+			const settled = await repo.settle(accountConfigId, written.suggestionId, {
+				state: CalendarSuggestionState.Accepted,
+				acceptedCalendarObjectId: "cal-object-9",
+			});
+
+			assert.equal(settled.state, CalendarSuggestionState.Accepted);
+			assert.equal(settled.acceptedCalendarObjectId, "cal-object-9");
+		});
+
+		test("supersedeIfPending retires a card still waiting on the user", async () => {
+			const accountConfigId = harness.makeId();
+			const written = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "uid"),
+			);
+
+			const retired = await repo.supersedeIfPending(
+				accountConfigId,
+				written.suggestionId,
+			);
+
+			assert.equal(retired?.state, CalendarSuggestionState.Superseded);
+		});
+
+		test("supersedeIfPending leaves an answered card alone and says so", async () => {
+			// The producer reads the pending set and writes to it in two steps. A
+			// person accepting in between must keep their acceptance — and the
+			// link to the event it put in their calendar.
+			const accountConfigId = harness.makeId();
+			const written = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "uid"),
+			);
+			await repo.settle(accountConfigId, written.suggestionId, {
+				state: CalendarSuggestionState.Accepted,
+				acceptedCalendarObjectId: "cal-object-7",
+			});
+
+			const retired = await repo.supersedeIfPending(
+				accountConfigId,
+				written.suggestionId,
+			);
+
+			assert.equal(retired, null);
+			const reread = await repo.get(accountConfigId, written.suggestionId);
+			assert.equal(reread.state, CalendarSuggestionState.Accepted);
+			assert.equal(reread.acceptedCalendarObjectId, "cal-object-7");
+		});
+
+		test("supersedeIfPending scopes to the account config", async () => {
+			const accountConfigId = harness.makeId();
+			const written = await repo.put(
+				suggestion(accountConfigId, harness.makeId(), harness.makeId(), "uid"),
+			);
+
+			assert.equal(
+				await repo.supersedeIfPending(harness.makeId(), written.suggestionId),
+				null,
+			);
+		});
+
+		test("settle rejects a suggestion that is not there", async () => {
+			const accountConfigId = harness.makeId();
+			await assert.rejects(
+				() =>
+					repo.settle(accountConfigId, harness.makeId(), {
+						state: CalendarSuggestionState.Declined,
+						acceptedCalendarObjectId: "",
+					}),
+				(error: unknown) => harness.isNotFoundError(error),
+			);
+		});
+	});
+}

package/src/conformance/index.ts

@@ -1,6 +1,7 @@
 export { calendarCollectionRepositoryConformance } from "./calendar-collection.js";
 export { calendarEventIndexRepositoryConformance } from "./calendar-event-index.js";
 export { calendarObjectRepositoryConformance } from "./calendar-object.js";
+export { calendarSuggestionRepositoryConformance } from "./calendar-suggestion.js";
 export type { RepositoryConformanceHarness } from "./harness.js";
 export { labelRepositoryConformance } from "./label.js";
 export { senderSignerStandingRepositoryConformance } from "./sender-signer-standing.js";

package/src/id.test.ts

@@ -6,6 +6,7 @@ import {
 	deriveBodyPartId,
 	deriveCalendarId,
 	deriveCalendarObjectId,
+	deriveCalendarSuggestionId,
 	deriveCopyMessageId,
 	deriveEnvelopeId,
 	deriveMessageId,
@@ -161,8 +162,71 @@ describe("deriveCalendarObjectId", () => {
 	});
 });
 
+describe("deriveCalendarSuggestionId", () => {
+	const MESSAGE = "msg-1";
+	const PART = "part-1";
+	const UID = "invite@example.com";
+
+	it("converges a re-read of the same message on one row", () => {
+		assert.equal(
+			deriveCalendarSuggestionId(MESSAGE, PART, UID),
+			deriveCalendarSuggestionId(MESSAGE, PART, UID),
+		);
+	});
+
+	it("keeps two invitations in one message apart", () => {
+		assert.notEqual(
+			deriveCalendarSuggestionId(MESSAGE, PART, UID),
+			deriveCalendarSuggestionId(MESSAGE, "part-2", UID),
+		);
+	});
+
+	it("gives a revision its own row, so the superseded card survives", () => {
+		// A later message carrying the same UID is a second suggestion, never an
+		// overwrite of the first: the older message keeps its card and the user
+		// can see which revision replaced which.
+		assert.notEqual(
+			deriveCalendarSuggestionId(MESSAGE, PART, UID),
+			deriveCalendarSuggestionId("msg-2", PART, UID),
+		);
+	});
+
+	it("separates two events sent as one part", () => {
+		assert.notEqual(
+			deriveCalendarSuggestionId(MESSAGE, PART, UID),
+			deriveCalendarSuggestionId(MESSAGE, PART, "other@example.com"),
+		);
+	});
+});
+
+describe("deriveThreadId", () => {
+	const ROOT = "<root@example.com>";
+
+	// #1017: the account is not part of the name, so every mailbox connected to
+	// one config resolves the same root header to one conversation. Keyed on the
+	// account, a reply sent from the second account opened a thread of its own.
+	it("gives one root header one thread across the accounts of a config", () => {
+		assert.equal(deriveThreadId("cfg-1", ROOT), deriveThreadId("cfg-1", ROOT));
+	});
+
+	it("separates two account configs holding the same conversation", () => {
+		assert.notEqual(
+			deriveThreadId("cfg-1", ROOT),
+			deriveThreadId("cfg-2", ROOT),
+		);
+	});
+
+	it("separates two conversations under one config", () => {
+		assert.notEqual(
+			deriveThreadId("cfg-1", ROOT),
+			deriveThreadId("cfg-1", "<other@example.com>"),
+		);
+	});
+});
+
 describe("derived ids are stored primary keys: a changed value orphans every row already written and needs a migration, never a new expectation here", () => {
 	const ACCOUNT = "account-golden";
+	const ACCOUNT_CONFIG = "account-config-golden";
 	const MESSAGE = "message-golden";
 	const MAILBOX = "mailbox-golden";
 	const ABSENT_HEADER_SOURCE = {
@@ -221,10 +285,10 @@ describe("derived ids are stored primary keys: a changed value orphans every row
 		);
 	});
 
-	it("deriveThreadId pins the thread primary key, lowercased root header included", () => {
+	it("deriveThreadId pins the thread primary key, keyed on the account config, lowercased root header included", () => {
 		assert.equal(
-			deriveThreadId(ACCOUNT, "<Golden.Root@Example.COM>"),
-			"bcy76e2uat5yq3xd1p7j7z4pr",
+			deriveThreadId(ACCOUNT_CONFIG, "<Golden.Root@Example.COM>"),
+			"3tl03sgy85b60rfb15u6vtiex",
 		);
 	});
 
@@ -268,6 +332,17 @@ describe("derived ids are stored primary keys: a changed value orphans every row
 		);
 	});
 
+	it("deriveCalendarSuggestionId pins the calendar_suggestion primary key", () => {
+		assert.equal(
+			deriveCalendarSuggestionId(
+				MESSAGE,
+				"bodypart-golden",
+				"golden-invite@example.com",
+			),
+			"1pesdr3fl02uyoz5k1qrfik3e",
+		);
+	});
+
 	it("quarantineMessageIdHash pins the stored Message-ID hash that correlates reports", () => {
 		assert.equal(
 			quarantineMessageIdHash("<golden@example.com>"),

package/src/id.ts

@@ -64,6 +64,34 @@ export const deriveCalendarObjectId = (
 ): string =>
 	base36uuidv5(`calendarobject:${calendarId}:${resourceName}`, REMIT_NAMESPACE);
 
+/**
+ * Identity of a suggestion read out of a message (issue #1033). Derived from
+ * the message, the MIME part the bytes came from and the event's iCalendar
+ * UID, so re-reading the same message converges on the row it already wrote
+ * instead of stacking a second card on the message every pass.
+ *
+ * All three parts are needed. The message alone would merge two invitations
+ * sent in one mail; the part alone is not stable enough to key on across a
+ * re-parse; and the UID keeps two events sent as one part apart.
+ *
+ * The message is in the seed, so identity is per message, not per event: a
+ * later message carrying the same UID derives its own id, and the earlier
+ * suggestion survives beside it as `Superseded`. The user can see which
+ * revision they are being asked about, and the older message still has a card.
+ * The same holds for a plain resend — a redelivered copy is a new message and
+ * so a new card, which the SEQUENCE comparison then declines to supersede
+ * anything for.
+ */
+export const deriveCalendarSuggestionId = (
+	messageId: string,
+	bodyPartId: string,
+	icalUid: string,
+): string =>
+	base36uuidv5(
+		`calendarsuggestion:${messageId}:${bodyPartId}:${icalUid}`,
+		REMIT_NAMESPACE,
+	);
+
 export const isValidMessageId = (messageId: string | undefined): boolean => {
 	if (!messageId) return false;
 	const trimmed = messageId.trim();
@@ -122,12 +150,22 @@ export const deriveCopyMessageId = (
 		REMIT_NAMESPACE,
 	);
 
+/**
+ * Identity of a conversation (issue #1017). Keyed on the account config, not on
+ * the account: two mailboxes connected to one config hold the same conversation,
+ * and keying on the account gave each of them its own thread rooted at the same
+ * header — so a reply sent from the second account opened a conversation of one
+ * beside the one it answered.
+ *
+ * Messages stay per account (`deriveMessageId`). Each account keeps its own copy
+ * of a mail, and the copies meet in one thread through the shared root header.
+ */
 export const deriveThreadId = (
-	accountId: string,
+	accountConfigId: string,
 	rootMessageIdHeader: string,
 ): string =>
 	base36uuidv5(
-		`thread:${accountId}:${rootMessageIdHeader.toLowerCase()}`,
+		`thread:${accountConfigId}:${rootMessageIdHeader.toLowerCase()}`,
 		REMIT_NAMESPACE,
 	);
 

package/src/index.ts

@@ -7,6 +7,10 @@ export type { IAddressRepository } from "./interfaces/address.js";
 export type { ICalendarCollectionRepository } from "./interfaces/calendar-collection.js";
 export type { ICalendarEventIndexRepository } from "./interfaces/calendar-event-index.js";
 export type { ICalendarObjectRepository } from "./interfaces/calendar-object.js";
+export type {
+	ICalendarSuggestionRepository,
+	SettleCalendarSuggestionInput,
+} from "./interfaces/calendar-suggestion.js";
 export type {
 	CalendarUnitOfWorkRepositories,
 	ICalendarUnitOfWork,
@@ -46,6 +50,11 @@ export type {
 	IUnitOfWork,
 	UnitOfWorkRepositories,
 } from "./interfaces/unit-of-work.js";
+export {
+	FILTER_NO_ACTION,
+	isSenderMuted,
+	isSenderMuteFilter,
+} from "./sender-mute.js";
 export type {
 	AccountConfigDescription,
 	AccountConfigItem,
@@ -68,6 +77,7 @@ export type {
 	CalendarEventIndexItem,
 	CalendarObjectItem,
 	CalendarOccurrenceInput,
+	CalendarSuggestionItem,
 	ConfigImportItem,
 	ConfigImportUnresolvedRefItem,
 	CreateAccountConfigInput,
@@ -113,6 +123,7 @@ export type {
 	OutboxAttachmentItem,
 	OutboxMessageItem,
 	PutCalendarObjectInput,
+	PutCalendarSuggestionInput,
 	PutMessageFlagPushInput,
 	PutMessagePlacementMoveInput,
 	QuarantineItem,

package/src/interfaces/calendar-suggestion.ts

@@ -0,0 +1,73 @@
+import type {
+	CalendarSuggestionItem,
+	PutCalendarSuggestionInput,
+	ResultList,
+} from "../types.js";
+
+/**
+ * The two fields that record what a person decided about a suggestion. They
+ * move together and only through {@link ICalendarSuggestionRepository.settle},
+ * so no producer write can walk an answered card back to `Pending`, and no
+ * state can name a calendar object that was never written.
+ *
+ * `acceptedCalendarObjectId` is `""` for every outcome but `Accepted` — the
+ * named absent state, never a missing attribute.
+ */
+export interface SettleCalendarSuggestionInput {
+	state: CalendarSuggestionItem["state"];
+	acceptedCalendarObjectId: string;
+}
+
+export interface ICalendarSuggestionRepository {
+	/**
+	 * Writes the suggestion under its derived `suggestionId`. An upsert: the
+	 * producer re-reading the same message rewrites the row it already wrote.
+	 *
+	 * Never touches `state` or `acceptedCalendarObjectId` on a row that already
+	 * exists, so a re-sync of a message whose invitation the user accepted
+	 * leaves the acceptance intact. A row it creates starts `Pending`.
+	 */
+	put(input: PutCalendarSuggestionInput): Promise<CalendarSuggestionItem>;
+	get(
+		accountConfigId: string,
+		suggestionId: string,
+	): Promise<CalendarSuggestionItem>;
+	/** Every suggestion one message produced, superseded revisions included. */
+	listByMessage(
+		accountConfigId: string,
+		messageId: string,
+	): Promise<CalendarSuggestionItem[]>;
+	/**
+	 * The account's suggestions in one state, newest first. Also how the
+	 * producer finds the revision a new message supersedes: only a `Pending`
+	 * suggestion can be superseded, so the candidate set is this one.
+	 */
+	listByState(
+		accountConfigId: string,
+		state: CalendarSuggestionItem["state"],
+		options?: { limit?: number; continuationToken?: string },
+	): Promise<ResultList<CalendarSuggestionItem>>;
+	/**
+	 * Records the outcome of a person's decision. Returns the settled row.
+	 */
+	settle(
+		accountConfigId: string,
+		suggestionId: string,
+		input: SettleCalendarSuggestionInput,
+	): Promise<CalendarSuggestionItem>;
+	/**
+	 * Retires a card as `Superseded`, but only while it is still `Pending`.
+	 * Returns the retired row, or `null` when the card had already been
+	 * answered and nothing was written.
+	 *
+	 * A compare-and-set rather than a plain `settle` because the producer reads
+	 * the pending set and writes to it in two steps, and a person can accept a
+	 * card in between. An unconditional write there would overwrite their
+	 * acceptance with `Superseded` and blank `acceptedCalendarObjectId`,
+	 * severing the card from the event it put in their calendar.
+	 */
+	supersedeIfPending(
+		accountConfigId: string,
+		suggestionId: string,
+	): Promise<CalendarSuggestionItem | null>;
+}

package/src/interfaces/calendar-unit-of-work.ts

@@ -1,6 +1,7 @@
 import type { ICalendarCollectionRepository } from "./calendar-collection.js";
 import type { ICalendarEventIndexRepository } from "./calendar-event-index.js";
 import type { ICalendarObjectRepository } from "./calendar-object.js";
+import type { ICalendarSuggestionRepository } from "./calendar-suggestion.js";
 
 /**
  * The repositories one calendar write set touches, bound to a single unit of
@@ -10,6 +11,13 @@ export interface CalendarUnitOfWorkRepositories {
 	calendarCollection: ICalendarCollectionRepository;
 	calendarObject: ICalendarObjectRepository;
 	calendarEventIndex: ICalendarEventIndexRepository;
+	/**
+	 * Present so accepting a suggestion settles the card in the same unit that
+	 * writes the resource (issue #1033). The two are one fact: a card still
+	 * asking with the event already in the calendar, or a card marked accepted
+	 * with no event behind it, is a state nothing later can repair.
+	 */
+	calendarSuggestion: ICalendarSuggestionRepository;
 }
 
 /**

package/src/sender-mute.test.ts

@@ -0,0 +1,76 @@
+import assert from "node:assert/strict";
+import { describe, it } from "node:test";
+import { isSenderMuted, isSenderMuteFilter } from "./sender-mute.js";
+import type { FilterItem } from "./types.js";
+
+const rule = (overrides: Partial<FilterItem> = {}): FilterItem =>
+	({
+		scope: "Standing",
+		literalClauses: [{ field: "From", value: "ada@example.test" }],
+		actionLabelId: "None",
+		actionMailboxId: "None",
+		...overrides,
+	}) as unknown as FilterItem;
+
+describe("isSenderMuteFilter", () => {
+	it("recognises a standing rule that names a sender and does nothing", () => {
+		assert.equal(isSenderMuteFilter(rule()), true);
+	});
+
+	it("declines a rule that applies a label", () => {
+		assert.equal(isSenderMuteFilter(rule({ actionLabelId: "label-1" })), false);
+	});
+
+	it("declines a rule that moves the message", () => {
+		assert.equal(
+			isSenderMuteFilter(rule({ actionMailboxId: "mailbox-1" })),
+			false,
+		);
+	});
+
+	it("declines a rule that matches on something other than the sender", () => {
+		assert.equal(
+			isSenderMuteFilter(
+				rule({
+					literalClauses: [{ field: "Subject", value: "invitation" }],
+				} as Partial<FilterItem>),
+			),
+			false,
+		);
+	});
+
+	it("declines a rule with no clauses, which would mute everybody", () => {
+		assert.equal(isSenderMuteFilter(rule({ literalClauses: [] })), false);
+	});
+
+	it("declines a temporary rule", () => {
+		assert.equal(isSenderMuteFilter(rule({ scope: "Temporary" })), false);
+	});
+});
+
+describe("isSenderMuted", () => {
+	it("matches an address whatever case either side was written in", () => {
+		assert.equal(isSenderMuted([rule()], "Ada@Example.TEST"), true);
+	});
+
+	it("matches the whole address, never a substring of one", () => {
+		// A rule about ada@example.test must not silence an address that merely
+		// contains it — the lookalike is exactly what a spoofer would send from.
+		assert.equal(
+			isSenderMuted([rule()], "not-ada@example.test.evil.test"),
+			false,
+		);
+	});
+
+	it("says no when nothing names the sender", () => {
+		assert.equal(isSenderMuted([rule()], "someone@example.test"), false);
+	});
+
+	it("says no for an empty sender rather than matching an empty clause", () => {
+		assert.equal(isSenderMuted([rule()], ""), false);
+	});
+
+	it("says no with no rules at all", () => {
+		assert.equal(isSenderMuted([], "ada@example.test"), false);
+	});
+});

package/src/sender-mute.ts

@@ -0,0 +1,59 @@
+import { FilterClauseField, FilterScope } from "@remit/domain-enums";
+import type { FilterItem } from "./types.js";
+
+/**
+ * The `Filter` model's sentinel for "this rule takes no such action" — the
+ * value `actionLabelId` and `actionMailboxId` hold when a filter applies no
+ * label and moves nothing (RFC 034 Decision 3.1).
+ */
+export const FILTER_NO_ACTION = "None";
+
+/**
+ * A standing rule that names senders and does nothing else.
+ *
+ * That combination has exactly one meaning. The index-time filter pipeline
+ * skips a filter with no label and no move, so such a rule changes nothing
+ * about where mail lands or how it is tagged; the only thing it can express is
+ * the user saying "not from this sender". `dismiss{muteSender:true}` writes
+ * one, and the calendar-suggestion producer reads it.
+ *
+ * Structural, never name-matching: the rule is recognised by its shape, so a
+ * rename in the settings UI cannot quietly un-mute a sender.
+ */
+export const isSenderMuteFilter = (
+	filter: Pick<
+		FilterItem,
+		"scope" | "literalClauses" | "actionLabelId" | "actionMailboxId"
+	>,
+): boolean =>
+	filter.scope === FilterScope.Standing &&
+	filter.actionLabelId === FILTER_NO_ACTION &&
+	filter.actionMailboxId === FILTER_NO_ACTION &&
+	filter.literalClauses.length > 0 &&
+	filter.literalClauses.every(
+		(clause) =>
+			clause.field === FilterClauseField.From && clause.value.trim() !== "",
+	);
+
+const fold = (value: string): string => value.trim().toLowerCase();
+
+/**
+ * Whether one of these rules mutes an address. Compared case-insensitively and
+ * whole: a mail address is one value, and a substring match would let a rule
+ * about `ada@example.com` silence `not-ada@example.com.evil.test`.
+ */
+export const isSenderMuted = (
+	filters: readonly Pick<
+		FilterItem,
+		"scope" | "literalClauses" | "actionLabelId" | "actionMailboxId"
+	>[],
+	sender: string,
+): boolean => {
+	const wanted = fold(sender);
+	if (wanted === "") return false;
+	return filters.some(
+		(filter) =>
+			isSenderMuteFilter(filter) &&
+			filter.literalClauses.some((clause) => fold(clause.value) === wanted),
+	);
+};

package/src/types.ts

@@ -9,6 +9,7 @@ import type {
 	CalendarCollectionSchema,
 	CalendarEventIndexSchema,
 	CalendarObjectSchema,
+	CalendarSuggestionSchema,
 	ConfigImportSchema,
 	ConfigImportUnresolvedRefSchema,
 	EnvelopeAddressSchema,
@@ -607,6 +608,29 @@ export type CalendarOccurrenceInput = Omit<
 	"calendarId" | "calendarObjectId" | "createdAt" | "updatedAt"
 >;
 
+export type CalendarSuggestionItem = z.infer<typeof CalendarSuggestionSchema>;
+
+/**
+ * A whole suggestion, as the producer read it out of a message. Every field is
+ * derived from the message — nothing here is client-supplied — and
+ * `suggestionId` is derived from messageId + bodyPartId + icalUid, so this is
+ * an upsert: re-reading the same message rewrites its own row rather than
+ * stacking a second card on the message.
+ *
+ * `state` and `acceptedCalendarObjectId` are excluded: a producer only ever
+ * writes a `Pending` suggestion, and the two fields that record what a person
+ * decided move exclusively through `settle`, so a re-sync can never walk an
+ * answered card back to Pending.
+ */
+export type PutCalendarSuggestionInput = Omit<
+	CalendarSuggestionItem,
+	| "suggestionId"
+	| "state"
+	| "acceptedCalendarObjectId"
+	| "createdAt"
+	| "updatedAt"
+>;
+
 export type SenderSignerStandingItem = z.infer<
 	typeof SenderSignerStandingSchema
 >;