@remit/mailbox-service 0.0.86 → 0.0.87

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/mailbox-service",
-  "version": "0.0.86",
+  "version": "0.0.87",
   "type": "module",
   "main": "src/index.ts",
   "types": "src/index.ts",

package/src/index.ts

@@ -249,7 +249,11 @@ export {
 	type ResolveExhaustedPlacementMoveResult,
 	resolveExhaustedPlacementMoveFailure,
 } from "./placement-move-terminal.js";
-export { isPlacementUnsettled } from "./placement-settled.js";
+export {
+	isPlacementUnsettled,
+	type PlacementBinding,
+	placementBindingOf,
+} from "./placement-settled.js";
 export {
 	type QuarantineContext,
 	QuarantinedUids,

package/src/placement-settled.ts

@@ -44,10 +44,12 @@ export const bindsForeignUid = (
 
 /**
  * `in_flight` — a mover is still working on the row, so waiting resolves it.
- * `abandoned` — the mover gave up without confirming (`syncStatus: failed`,
- * written by every handler's give-up path while `status` stays `moving`, since
- * only `updateUid` clears it). Nothing routine settles such a row, so waiting
- * on one is a wait that never ends, and the pair stays a lie either way.
+ * `abandoned` — the last attempt failed (`syncStatus: failed`) and the row is
+ * still `moving`: either a redelivery is pending, or the record dead-lettered
+ * and nothing is coming for it. The two are indistinguishable from the row
+ * (`message-settlement.ts`), and the pair is a lie either way, so neither is
+ * worth spending the settle ceiling on. A mover that exhausts its budget
+ * settles the row against IMAP instead of leaving this state behind (#1005).
  */
 export type PlacementBinding = "consistent" | "in_flight" | "abandoned";