@remit/backend 0.0.85 → 0.0.87

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/backend",
-  "version": "0.0.85",
+  "version": "0.0.87",
   "description": "Remit Mail Inspector API backend",
   "license": "MIT",
   "author": "",

package/src/service/create-remit-client.ts

@@ -330,6 +330,7 @@ export const createRemitClient = (deps: RemitClientDeps): RemitClient => {
 				threadMessageService: repositories.threadMessage,
 				markerService: repositories.placementMove,
 				addressService: repositories.address,
+				mailboxSpecialUseService: repositories.mailboxSpecialUse,
 				sqsQueueUrl: placementMoveQueueUrl,
 			})
 		: undefined;

package/src/service/organize.ts

@@ -594,6 +594,7 @@ export const buildOrganizeMoveService = (
 		threadMessageService: client.threadMessage,
 		markerService: client.placementMove,
 		addressService: client.address,
+		mailboxSpecialUseService: client.mailboxSpecialUse,
 		sqsQueueUrl: queueUrl,
 	});
 };

package/src/service/trigger-sync.ts

@@ -24,10 +24,10 @@ interface TriggerAccountSyncInput {
 	 * this unset, and takes the freshness gate — see `mailboxNeedsSync` in
 	 * imap-worker's sync-mailboxes handler.
 	 *
-	 * The poll cannot use this to outrun the gate: its interval is floored at
-	 * the gate's own window (`MIN_POLL_INTERVAL_MS` in the client hook), so
-	 * however low `mailboxPollIntervalSeconds` is set, a timer never fans out
-	 * more often than the gate would have allowed anyway.
+	 * How often a timer may do that is bounded on the client, by the poll's own
+	 * floor (`MIN_POLL_INTERVAL_MS` in the client hook, 30s) rather than by the
+	 * gate: `mailboxPollIntervalSeconds` can lengthen the interval, never
+	 * shorten it past that.
 	 */
 	explicitRequest?: boolean;
 	/**