@remit/mailbox-service 0.0.90 → 0.0.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -9,10 +9,10 @@ import { carriesForeignUid, placementBindingOf } from "./placement-settled.js";
9
9
  * only end-to-end specs covered it, so a change made for the client's benefit
10
10
  * could have moved it without anything going red.
11
11
  *
12
- * Note what these cases say about `syncStatus: failed`: it answers `abandoned`
13
- * here for a row that may well be mid-retry. That is correct for a guard whose
14
- * consequence is a temporary refusal, and it is exactly why no user-facing
15
- * statement may be derived from that field alone.
12
+ * Note what these cases say about `syncStatus`: `failed` is a transient attempt
13
+ * with a redelivery behind it, so a foreign-uid row carrying it is `in_flight`
14
+ * and gets the settle ceiling. Only `abandoned` — the give-up value of the
15
+ * placement state model (imap-mutations R3) — refuses outright.
16
16
  */
17
17
  const row = (over: Partial<MessageItem>): MessageItem =>
18
18
  ({
@@ -38,10 +38,40 @@ describe("placementBindingOf", () => {
38
38
  assert.equal(placementBindingOf(row({})), "in_flight");
39
39
  });
40
40
 
41
- test("`failed` on a foreign-uid row is refused as abandoned", () => {
41
+ /**
42
+ * A give-up cannot reach this pair. `abandoned` is written only alongside
43
+ * `active` or `deleted`, on a row already put back on a placement the server
44
+ * confirmed, so the binding it produces is `consistent` — there is no
45
+ * give-up member here to return, and no dependent mutation is refused on
46
+ * account of one.
47
+ */
48
+ test("a give-up never presents as a foreign-uid row at all", () => {
49
+ assert.equal(
50
+ placementBindingOf(
51
+ row({
52
+ status: MessageStatus.active,
53
+ syncStatus: MessageSyncStatus.abandoned,
54
+ mailboxId: "mbx-src",
55
+ }),
56
+ ),
57
+ "consistent",
58
+ );
59
+ });
60
+
61
+ test("`failed` on a foreign-uid row is mid-retry, so it waits rather than refusing", () => {
42
62
  assert.equal(
43
63
  placementBindingOf(row({ syncStatus: MessageSyncStatus.failed })),
44
- "abandoned",
64
+ "in_flight",
65
+ );
66
+ });
67
+
68
+ // R3's state table calls `deleting` in flight exactly as `moving` is: a
69
+ // delete points the row at Trash with the source's uid, so a dependent
70
+ // mutation reading it resolves the same mismatched pair.
71
+ test("a delete in flight is unsettled, not settled", () => {
72
+ assert.equal(
73
+ placementBindingOf(row({ status: MessageStatus.deleting })),
74
+ "in_flight",
45
75
  );
46
76
  });
47
77
 
@@ -1,5 +1,5 @@
1
1
  import type { MessageItem } from "@remit/data-ports";
2
- import { MessageStatus, MessageSyncStatus } from "@remit/domain-enums";
2
+ import { MessageStatus } from "@remit/domain-enums";
3
3
 
4
4
  /**
5
5
  * Whether the message row's placement is still an unconfirmed local write
@@ -12,18 +12,26 @@ import { MessageStatus, MessageSyncStatus } from "@remit/domain-enums";
12
12
  *
13
13
  * `syncStatus` is not the signal. An ordinary freshly-synced inbound row is
14
14
  * `pending` forever (nothing on the inbound path promotes it), so keying off it
15
- * defers every outbound mutation in the product. `status` is set to `moving`
16
- * only by an actual move and cleared only once that move settles.
15
+ * defers every outbound mutation in the product. `status` is what an actual
16
+ * mutation writes and what settling clears.
17
+ *
18
+ * Both in-flight states count, per the R3 state table: a delete points the row
19
+ * at Trash with the source's uid exactly as a move points it at the
20
+ * destination, so a dependent mutation that reads a `deleting` row resolves the
21
+ * same mismatched pair. Reading `moving` alone let a move enqueued behind a
22
+ * delete bind to the row mid-delete and be dropped when the delete settled.
17
23
  */
18
24
  export const isPlacementUnsettled = (
19
25
  message: Pick<MessageItem, "status">,
20
- ): boolean => message.status === MessageStatus.moving;
26
+ ): boolean =>
27
+ message.status === MessageStatus.moving ||
28
+ message.status === MessageStatus.deleting;
21
29
 
22
30
  /**
23
31
  * Whether the row's `uid` belongs to a folder other than the one `mailboxId`
24
32
  * names — the state that makes the pair a lie rather than merely incomplete.
25
33
  *
26
- * `updateForMove` is the only writer of this shape: it points the row at the
34
+ * The optimistic half of a move is the only writer of this shape: it points the row at the
27
35
  * destination and records the pre-move pair, leaving `uid` untouched until the
28
36
  * server confirms and `updateUid` replaces it. A row with no `originalUid` was
29
37
  * never moved, so its uid names nothing but itself — a freshly copied row is
@@ -57,32 +65,27 @@ export const bindsForeignUid = (
57
65
  ): boolean => isPlacementUnsettled(message) && carriesForeignUid(message);
58
66
 
59
67
  /**
60
- * `in_flight` — a mover is still working on the row, so waiting resolves it.
61
- * `abandoned` — the last attempt failed (`syncStatus: failed`) and the row is
62
- * still `moving`: either a redelivery is pending, or the record dead-lettered
63
- * and nothing is coming for it. The two are indistinguishable from the row
64
- * (`message-settlement.ts`), and the pair is a lie either way, so neither is
65
- * worth spending the settle ceiling on. A mover that exhausts its budget
66
- * settles the row against IMAP instead of leaving this state behind (#1005).
68
+ * `in_flight` — a mutation is still working on the row, so waiting resolves it.
69
+ * That includes a row mid-retry: `message-move`, `message-delete` and
70
+ * `message-copy` write `syncStatus: failed` on an ordinary transient attempt
71
+ * and re-throw for redelivery, so a failed attempt is a mutation about to
72
+ * succeed and the settle ceiling is exactly what it is for (imap-mutations R3).
73
+ *
74
+ * There is no give-up member, because a give-up cannot reach here: `abandoned`
75
+ * is written only alongside `status: active` (a hand-back) or `deleted` (a copy
76
+ * that never existed), and the row it leaves names a placement the server
77
+ * confirmed — so it binds `consistent` and no dependent mutation is refused on
78
+ * account of it. A mutation that exhausts its budget settles the row against
79
+ * IMAP rather than leaving a mismatched pair behind (#1005).
67
80
  */
68
- export type PlacementBinding = "consistent" | "in_flight" | "abandoned";
81
+ export type PlacementBinding = "consistent" | "in_flight";
69
82
 
70
83
  export const placementBindingOf = (
71
84
  message: Pick<
72
85
  MessageItem,
73
- | "status"
74
- | "syncStatus"
75
- | "mailboxId"
76
- | "uid"
77
- | "originalMailboxId"
78
- | "originalUid"
86
+ "status" | "mailboxId" | "uid" | "originalMailboxId" | "originalUid"
79
87
  >,
80
- ): PlacementBinding => {
81
- if (!bindsForeignUid(message)) return "consistent";
82
- return message.syncStatus === MessageSyncStatus.failed
83
- ? "abandoned"
84
- : "in_flight";
85
- };
88
+ ): PlacementBinding => (bindsForeignUid(message) ? "in_flight" : "consistent");
86
89
 
87
90
  export interface PlacementSettleOptions {
88
91
  timeoutMs: number;
@@ -0,0 +1,482 @@
1
+ /**
2
+ * The three optimistic writers, against a row that moves under them
3
+ * (docs/architecture/imap-mutations.md R3).
4
+ *
5
+ * Each reads a message, does several lookups, then writes where it decided to
6
+ * put it. Between the read and the write, PLACEMENT_MOVE_PUSH can settle the
7
+ * same row: that lane rides a standard queue, which the account's FIFO group
8
+ * does not order against. A blind write then stamps `moving` and the OLD uid
9
+ * over a folder and uid the mail server has just confirmed — a pair
10
+ * `carriesForeignUid` reads as consistent, so nothing downstream catches it —
11
+ * and the event that follows sends the worker after whatever now holds the old
12
+ * number.
13
+ *
14
+ * The repository honours the predicate here the way the real one does, so a
15
+ * losing write returns `undefined` and lands nothing at all.
16
+ */
17
+
18
+ import assert from "node:assert/strict";
19
+ import { describe, it } from "node:test";
20
+ import type {
21
+ IAddressRepository,
22
+ IMailboxRepository,
23
+ IMailboxSpecialUseRepository,
24
+ IMessagePlacementMoveRepository,
25
+ IMessageRepository,
26
+ IThreadMessageRepository,
27
+ PlacementPredicate,
28
+ PlacementTransitionInput,
29
+ } from "@remit/data-ports";
30
+ import { MessagePlacementUnsettledError } from "@remit/data-ports/errors";
31
+ import { MessageMoveService } from "./message-move.js";
32
+ import { PlacementMoveService } from "./placement-move.js";
33
+ import { NO_JUNK_ROLES } from "./test-helpers/folder-roles.js";
34
+
35
+ const ACCOUNT = "acc-1";
36
+ const ACCOUNT_CONFIG = "cfg-1";
37
+ const INBOX = "mbx-inbox";
38
+ const ARCHIVE = "mbx-archive";
39
+ const TRASH = "mbx-trash";
40
+ const JUNK = "mbx-junk";
41
+ const MESSAGE_ID = "msg-1";
42
+
43
+ /** What the row is when each writer reads it. */
44
+ const READ_UID = 42;
45
+
46
+ /** What the placement push settles it to while the writer is still deciding. */
47
+ const SETTLED_UID = 907;
48
+
49
+ const mailboxes = [
50
+ { mailboxId: INBOX, fullPath: "INBOX", accountId: ACCOUNT, uidValidity: 1 },
51
+ {
52
+ mailboxId: ARCHIVE,
53
+ fullPath: "Archive",
54
+ accountId: ACCOUNT,
55
+ uidValidity: 1,
56
+ },
57
+ { mailboxId: TRASH, fullPath: "Trash", accountId: ACCOUNT, uidValidity: 1 },
58
+ { mailboxId: JUNK, fullPath: "Junk", accountId: ACCOUNT, uidValidity: 1 },
59
+ ];
60
+
61
+ interface CapturedEvent {
62
+ type: string;
63
+ messageId?: string;
64
+ uid?: number;
65
+ }
66
+
67
+ interface Row {
68
+ messageId: string;
69
+ accountConfigId: string;
70
+ mailboxId: string;
71
+ uid: number;
72
+ status: string;
73
+ syncStatus: string;
74
+ abandonedMutation: string;
75
+ originalMailboxId?: string;
76
+ originalUid?: number;
77
+ }
78
+
79
+ const freshRow = (): Row => ({
80
+ messageId: MESSAGE_ID,
81
+ accountConfigId: ACCOUNT_CONFIG,
82
+ mailboxId: INBOX,
83
+ uid: READ_UID,
84
+ status: "active",
85
+ syncStatus: "synced",
86
+ abandonedMutation: "none",
87
+ });
88
+
89
+ interface World {
90
+ row: Row;
91
+ events: CapturedEvent[];
92
+ writes: PlacementTransitionInput[];
93
+ /** Destination folders the listing row was actually moved to. */
94
+ threadMoves: string[];
95
+ /** Stand in for the push settling the row onto Archive with Archive's uid. */
96
+ settleElsewhere: () => void;
97
+ messageService: IMessageRepository;
98
+ threadMessageService: IThreadMessageRepository;
99
+ mailboxService: IMailboxRepository;
100
+ mailboxSpecialUseService: IMailboxSpecialUseRepository;
101
+ addressService: IAddressRepository;
102
+ }
103
+
104
+ const buildWorld = (onLookup?: (world: World) => void): World => {
105
+ const row = freshRow();
106
+ const events: CapturedEvent[] = [];
107
+ const writes: PlacementTransitionInput[] = [];
108
+
109
+ const threadMoves: string[] = [];
110
+ const world = { row, events, writes, threadMoves } as World;
111
+
112
+ world.settleElsewhere = () => {
113
+ row.mailboxId = ARCHIVE;
114
+ row.uid = SETTLED_UID;
115
+ row.status = "active";
116
+ row.syncStatus = "synced";
117
+ row.originalUid = undefined;
118
+ };
119
+
120
+ world.messageService = {
121
+ // A snapshot, the way a repository read is one. Handing back the live
122
+ // object would let the caller's `message` follow the concurrent settle,
123
+ // and the predicate it builds from it would match by accident.
124
+ get: async (ids: string | string[]) =>
125
+ Array.isArray(ids) ? [{ ...row }] : ({ ...row } as unknown),
126
+ update: async () => row,
127
+ transitionPlacement: async (
128
+ _messageId: string,
129
+ expected: PlacementPredicate,
130
+ next: PlacementTransitionInput,
131
+ ) => {
132
+ if (expected.status !== undefined && expected.status !== row.status) {
133
+ return undefined;
134
+ }
135
+ if (
136
+ expected.mailboxId !== undefined &&
137
+ expected.mailboxId !== row.mailboxId
138
+ ) {
139
+ return undefined;
140
+ }
141
+ if (expected.uid !== undefined && expected.uid !== row.uid) {
142
+ return undefined;
143
+ }
144
+ writes.push(next);
145
+ Object.assign(row, next);
146
+ return row;
147
+ },
148
+ } as unknown as IMessageRepository;
149
+
150
+ world.threadMessageService = {
151
+ getByMessageId: async () => ({
152
+ accountConfigId: ACCOUNT_CONFIG,
153
+ threadMessageId: "tm-1",
154
+ messageId: MESSAGE_ID,
155
+ mailboxId: row.mailboxId,
156
+ sentDate: 1,
157
+ isRead: false,
158
+ isDeleted: false,
159
+ hasStars: false,
160
+ hasAttachment: false,
161
+ }),
162
+ findAllByMessageId: async () => [],
163
+ update: async (
164
+ _accountConfigId: string,
165
+ _threadMessageId: string,
166
+ patch: { mailboxId?: string },
167
+ ) => {
168
+ if (patch.mailboxId) threadMoves.push(patch.mailboxId);
169
+ },
170
+ } as unknown as IThreadMessageRepository;
171
+
172
+ // Every writer resolves folders between reading the row and writing it, so
173
+ // this is where the concurrent settle is made to land.
174
+ world.mailboxService = {
175
+ get: async (_accountId: string, ids: string | string[]) => {
176
+ onLookup?.(world);
177
+ return Array.isArray(ids)
178
+ ? mailboxes.filter((mailbox) => ids.includes(mailbox.mailboxId))
179
+ : mailboxes.find((mailbox) => mailbox.mailboxId === ids);
180
+ },
181
+ } as unknown as IMailboxRepository;
182
+
183
+ world.mailboxSpecialUseService = {
184
+ findTrashMailbox: async () => mailboxes[2],
185
+ resolveTrashRole: async () => ({ kind: "flagged", mailbox: mailboxes[2] }),
186
+ resolveJunkRolesForConfig: async () => NO_JUNK_ROLES,
187
+ } as unknown as IMailboxSpecialUseRepository;
188
+
189
+ world.addressService = {
190
+ reconcileJunkOnlyForMessage: async () => {},
191
+ } as unknown as IAddressRepository;
192
+
193
+ return world;
194
+ };
195
+
196
+ const buildMoveService = (world: World): MessageMoveService => {
197
+ const service = new MessageMoveService({
198
+ messageService: world.messageService,
199
+ mailboxService: world.mailboxService,
200
+ mailboxSpecialUseService: world.mailboxSpecialUseService,
201
+ threadMessageService: world.threadMessageService,
202
+ addressService: world.addressService,
203
+ sqsQueueUrl: "http://localhost:9324/000000000000/remit-messages.fifo",
204
+ moveSettleTimeoutMs: 100,
205
+ moveSettlePollMs: 10,
206
+ });
207
+ (
208
+ service as unknown as {
209
+ enqueueEvent: (e: CapturedEvent) => Promise<void>;
210
+ enqueueEventsBatch: (e: CapturedEvent[]) => Promise<void>;
211
+ }
212
+ ).enqueueEvent = async (event) => {
213
+ world.events.push(event);
214
+ };
215
+ (
216
+ service as unknown as {
217
+ enqueueEventsBatch: (e: CapturedEvent[]) => Promise<void>;
218
+ }
219
+ ).enqueueEventsBatch = async (batch) => {
220
+ world.events.push(...batch);
221
+ };
222
+ return service;
223
+ };
224
+
225
+ describe("a user move writes only against the placement it read (R3)", () => {
226
+ it("moves the message when nothing else touched the row", async () => {
227
+ const world = buildWorld();
228
+ const service = buildMoveService(world);
229
+
230
+ await service.moveMessage(ACCOUNT_CONFIG, MESSAGE_ID, ARCHIVE, ACCOUNT);
231
+
232
+ assert.equal(world.events.length, 1);
233
+ assert.equal(world.row.status, "moving");
234
+ assert.equal(world.row.mailboxId, ARCHIVE);
235
+ });
236
+
237
+ it("refuses, and writes nothing, when the row settles elsewhere mid-decision", async () => {
238
+ let settled = false;
239
+ const world = buildWorld((w) => {
240
+ if (settled) return;
241
+ settled = true;
242
+ w.settleElsewhere();
243
+ });
244
+ const service = buildMoveService(world);
245
+
246
+ await assert.rejects(
247
+ () => service.moveMessage(ACCOUNT_CONFIG, MESSAGE_ID, JUNK, ACCOUNT),
248
+ (error: unknown) =>
249
+ error instanceof MessagePlacementUnsettledError &&
250
+ error.statusCode === 409,
251
+ );
252
+
253
+ assert.deepEqual(world.writes, [], "no placement was written");
254
+ assert.deepEqual(world.events, [], "and nothing was enqueued");
255
+ assert.equal(
256
+ world.row.mailboxId,
257
+ ARCHIVE,
258
+ "the winner's placement stands exactly as it left it",
259
+ );
260
+ assert.equal(world.row.uid, SETTLED_UID);
261
+ assert.equal(world.row.status, "active");
262
+ });
263
+ });
264
+
265
+ describe("a delete writes only against the placement it read (R3)", () => {
266
+ it("marks the message when nothing else touched the row", async () => {
267
+ const world = buildWorld();
268
+ const service = buildMoveService(world);
269
+
270
+ await service.deleteMessages(ACCOUNT_CONFIG, [MESSAGE_ID], ACCOUNT);
271
+
272
+ assert.equal(world.events.length, 1);
273
+ assert.equal(world.row.status, "moving");
274
+ assert.equal(world.row.mailboxId, TRASH);
275
+ });
276
+
277
+ it("skips the message, and enqueues nothing for it, when the row settles elsewhere", async () => {
278
+ let settled = false;
279
+ const world = buildWorld((w) => {
280
+ if (settled) return;
281
+ settled = true;
282
+ w.settleElsewhere();
283
+ });
284
+ const service = buildMoveService(world);
285
+
286
+ const { refusedMessageIds } = await service.deleteMessages(
287
+ ACCOUNT_CONFIG,
288
+ [MESSAGE_ID],
289
+ ACCOUNT,
290
+ );
291
+
292
+ assert.deepEqual(
293
+ refusedMessageIds,
294
+ [MESSAGE_ID],
295
+ "the caller is told which rows this delete never claimed",
296
+ );
297
+ assert.deepEqual(world.writes, [], "no placement was written");
298
+ assert.deepEqual(
299
+ world.events,
300
+ [],
301
+ "and no delete was enqueued against a uid the source no longer holds",
302
+ );
303
+ assert.equal(world.row.mailboxId, ARCHIVE);
304
+ assert.equal(world.row.uid, SETTLED_UID);
305
+ });
306
+ });
307
+
308
+ // The folder lookup is scoped to one account. The daily brief lists every
309
+ // account's mail, so a selection made there carries rows this lookup cannot
310
+ // resolve — and dropping them silently answered "deleted" over messages still
311
+ // sitting where they were.
312
+ describe("a delete reports a row whose folder it could not resolve", () => {
313
+ it("refuses it rather than counting it as deleted", async () => {
314
+ const world = buildWorld();
315
+ world.row.mailboxId = "mbx-another-account";
316
+ const service = buildMoveService(world);
317
+
318
+ const { refusedMessageIds } = await service.deleteMessages(
319
+ ACCOUNT_CONFIG,
320
+ [MESSAGE_ID],
321
+ ACCOUNT,
322
+ );
323
+
324
+ assert.deepEqual(refusedMessageIds, [MESSAGE_ID]);
325
+ assert.deepEqual(world.writes, [], "nothing was written");
326
+ assert.deepEqual(world.events, [], "and nothing was enqueued");
327
+ });
328
+ });
329
+
330
+ describe("a permanent delete writes only against the placement it read (R3)", () => {
331
+ // The row is already in Trash, so the batch takes the expunge path rather
332
+ // than the move-to-Trash one — a different writer, and the fourth of the
333
+ // four. Its event names one uid in one folder, so a row that has moved since
334
+ // the read must not be marked for it: a restore out of Trash settling in
335
+ // between was overwritten with `deleting`, and the expunge went after the
336
+ // uid Trash no longer holds.
337
+ const inTrash = (world: World): void => {
338
+ world.row.mailboxId = TRASH;
339
+ };
340
+
341
+ it("marks the message when nothing else touched the row", async () => {
342
+ const world = buildWorld();
343
+ inTrash(world);
344
+ const service = buildMoveService(world);
345
+
346
+ const { refusedMessageIds } = await service.deleteMessages(
347
+ ACCOUNT_CONFIG,
348
+ [MESSAGE_ID],
349
+ ACCOUNT,
350
+ { permanent: true },
351
+ );
352
+
353
+ assert.deepEqual(refusedMessageIds, []);
354
+ assert.equal(world.row.status, "deleting");
355
+ assert.equal(world.events.length, 1);
356
+ });
357
+
358
+ it("reports the message, and enqueues nothing, when the row settles elsewhere", async () => {
359
+ let settled = false;
360
+ const world = buildWorld((w) => {
361
+ if (settled) return;
362
+ settled = true;
363
+ w.settleElsewhere();
364
+ });
365
+ inTrash(world);
366
+ const service = buildMoveService(world);
367
+
368
+ const { refusedMessageIds } = await service.deleteMessages(
369
+ ACCOUNT_CONFIG,
370
+ [MESSAGE_ID],
371
+ ACCOUNT,
372
+ { permanent: true },
373
+ );
374
+
375
+ // Reported, never silent: the client removed the row optimistically, and
376
+ // one that reappears with nothing said is a failure the user cannot act
377
+ // on — the same class as a button that does nothing (#1229).
378
+ assert.deepEqual(refusedMessageIds, [MESSAGE_ID]);
379
+ assert.deepEqual(world.writes, [], "no placement was written");
380
+ assert.deepEqual(world.events, [], "and no expunge was enqueued");
381
+ assert.equal(world.row.mailboxId, ARCHIVE);
382
+ assert.equal(world.row.status, "active");
383
+ });
384
+ });
385
+
386
+ describe("a classification filing writes only against the placement it read (R3)", () => {
387
+ const buildPlacementService = (world: World, onPut?: () => void) => {
388
+ const markers = new Map<string, unknown>();
389
+ const pushed: string[] = [];
390
+ const markerService = {
391
+ find: async () => markers.get(MESSAGE_ID) ?? null,
392
+ // The last step between reading the row and writing it, so this is
393
+ // where a concurrent settle is staged.
394
+ put: async (input: Record<string, unknown>) => {
395
+ onPut?.();
396
+ const marker = { ...input, state: "pending", createdAt: Date.now() };
397
+ markers.set(MESSAGE_ID, marker);
398
+ return marker;
399
+ },
400
+ updateState: async () => markers.get(MESSAGE_ID),
401
+ delete: async () => {
402
+ markers.delete(MESSAGE_ID);
403
+ },
404
+ } as unknown as IMessagePlacementMoveRepository;
405
+
406
+ const service = new PlacementMoveService({
407
+ messageService: world.messageService,
408
+ threadMessageService: world.threadMessageService,
409
+ markerService,
410
+ addressService: world.addressService,
411
+ mailboxSpecialUseService: world.mailboxSpecialUseService,
412
+ sqsQueueUrl: "http://localhost:9324/000000000000/remit-message-mgmt",
413
+ moveSettleTimeoutMs: 100,
414
+ moveSettlePollMs: 10,
415
+ });
416
+ (service as unknown as { enqueuePush: () => Promise<void> }).enqueuePush =
417
+ async () => {
418
+ pushed.push(MESSAGE_ID);
419
+ };
420
+ return { service, markers, pushed };
421
+ };
422
+
423
+ it("files the message when nothing else touched the row", async () => {
424
+ const world = buildWorld();
425
+ const { service, markers, pushed } = buildPlacementService(world);
426
+
427
+ await service.moveMessage(ACCOUNT_CONFIG, MESSAGE_ID, JUNK, ACCOUNT);
428
+
429
+ assert.equal(world.row.mailboxId, JUNK);
430
+ assert.deepEqual(
431
+ world.threadMoves,
432
+ [JUNK],
433
+ "and the listing row follows the message it describes",
434
+ );
435
+ assert.deepEqual(pushed, [MESSAGE_ID]);
436
+ assert.ok(markers.get(MESSAGE_ID));
437
+ });
438
+
439
+ // The Message row is written first, so a loser leaves nothing behind. Moving
440
+ // the listing row ahead of the transition made the loser diverge instead: the
441
+ // listing showed the classification folder while the Message row sat where
442
+ // the winner put it, and nothing routine reconciles that.
443
+ it("leaves the listing row alone too when the row settles elsewhere", async () => {
444
+ const world = buildWorld();
445
+ const { service, markers, pushed } = buildPlacementService(world, () =>
446
+ world.settleElsewhere(),
447
+ );
448
+
449
+ await service.moveMessage(ACCOUNT_CONFIG, MESSAGE_ID, JUNK, ACCOUNT);
450
+
451
+ assert.deepEqual(world.writes, [], "no placement was written");
452
+ assert.deepEqual(
453
+ world.threadMoves,
454
+ [],
455
+ "and the listing row never claimed a folder the message is not in",
456
+ );
457
+ assert.deepEqual(pushed, [], "and no push was enqueued");
458
+ assert.equal(
459
+ markers.get(MESSAGE_ID),
460
+ undefined,
461
+ "the marker goes with it: nothing owes IMAP this move",
462
+ );
463
+ assert.equal(world.row.mailboxId, ARCHIVE);
464
+ });
465
+
466
+ // A permanent delete has already claimed the row. Waiting the ceiling out and
467
+ // then throwing drove an ordinary sequence toward the DLQ; there is nothing
468
+ // left to file, so this skips.
469
+ it("skips a message a delete has claimed, rather than burning the ceiling", async () => {
470
+ const world = buildWorld();
471
+ world.row.status = "deleting";
472
+ const { service, markers, pushed } = buildPlacementService(world);
473
+
474
+ const startedAt = Date.now();
475
+ await service.moveMessage(ACCOUNT_CONFIG, MESSAGE_ID, JUNK, ACCOUNT);
476
+
477
+ assert.ok(Date.now() - startedAt < 100, "and never entered the wait");
478
+ assert.deepEqual(world.writes, []);
479
+ assert.deepEqual(pushed, []);
480
+ assert.equal(markers.get(MESSAGE_ID), undefined);
481
+ });
482
+ });