@openlup/outbox 0.15.0 → 0.17.0

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 ## [Unreleased]
 
+## [0.17.0]
+
+- Publishable on the npm `latest` dist-tag as `0.17.0`, from tag
+  `openlup-outbox-v0.17.0`.
+
+- Republish with the exact `@openlup/core` `0.17.0` peer pin; APIs, runtime
+  behavior and shipped SQL are unchanged from `0.16.0`.
+
+Baseline evidence (2026-10-20): published `0.16.0` tarball 38,673 packed bytes,
+SHA256 `1219a95952ae1dd8a7ceee80ad58b8ab5a9501527d5e20194b4c4db43d031ebd`.
+The initial `0.16.0` release-gates baseline is retained under S1 option B.
+
+## [0.16.0]
+
+- Publishable on the npm `latest` dist-tag as `0.16.0`, from tag
+  `openlup-outbox-v0.16.0`.
+
+- Republish with the exact `@openlup/core` `0.16.0` peer pin; Outbox APIs, runtime behavior and shipped SQL are unchanged.
+
 ## [0.15.0]
 
 - Publishable on the npm `latest` dist-tag as `0.15.0`, from tag

package/README.md

@@ -65,6 +65,19 @@ admission policy and does not prove effective authorization or SQL behavior.
 
 The root companion tests retain real interruption and lost-response fixtures. Their owned JSON witness markers are written completely to a same-directory temporary file and then renamed into place, so readers never treat a newly created, partially written file as a ready observation. A plain Node process owns each fixture's service and launcher and stays in the root test process group until teardown finishes, even when Vitest's worker exits. Only the bounded Docker cleanup commands detach; their process-start window can still receive a group TERM. The companion fixture allows one recovery only for a child terminated by SIGTERM with no reported error, inside the original 10-second inspect or removal deadline. An interrupted removal is followed by actual Docker inspection: normal no-such-object refusal confirms absence, otherwise the same full ID, name and UUID label must still match before one removal retry. The recovery never resets its deadline, treats a signal as absence, or masks a timeout, nonzero result, wrong owner or second interruption. Cleanup recovers by the known unique name after a lost creation response. Root cancellation regressions interrupt actual Vitest workers after service creation and after detached proof readiness, and check resource termination before releasing their own test lock. They create no verification stamp or shared verifier lock. Separate teardown regressions cancel the actual npm/launcher route during each cleanup operation and assert that its container or UUID database is removed while an unrelated supplied-service database remains.
 
+The standalone-driver fixtures run builtin-only proof stubs or stop before the
+packed consumer starts, so they need no Zod directory copy. Artifact-set and
+digest refusals remain in [the manifest-input tests](../../scripts/packages/pack-manifest-input.test.ts);
+installed missing-export refusal remains in [the required-package-gate tests](../../scripts/packages/required-package-gates.test.ts).
+The required cold package gate executes the actual installed reference proof,
+including the replay and token-fencing witness above. The root companion tests
+focus on cancellation, ownership and bounded cleanup without repeating that
+consumer proof against planted artifact or replay faults.
+
+The root group-liveness fixture keeps polling after a signal-zero `EPERM`, which
+can occur for zombie-only groups on Darwin. Only `ESRCH` establishes group
+absence; the original cancellation deadline still applies.
+
 Upgrade the complete `@openlup/*` set together after reading each changelog. Use ports and composition; do not edit or patch installed package bytes. Sources are in `src/`, built JavaScript/declarations in `dist/`. Synthetic packed-consumer proof is first-party package evidence, not an independent adopter, provider-delivery or deployment certificate.
 
 ## Adoption and native extensions
@@ -93,3 +106,14 @@ installed contract. This package guide conveys version-bound contract informatio
 not tool permissions, an automatic control installation or external-write authority.
 The existing wiring and packed protocol examples remain narrow package evidence;
 a complete extension/absorption/retry witness belongs to the actual module adoption.
+
+## Package artifact limits
+
+The monorepo's package artifact checker enforces this package's
+`release-gates.json` caps and packed content allowlist. Only
+`--release-set <version>` checks compressed growth against the last released
+baseline, with explanations in the new set's changelog section and release body. See the
+[package artifact policy](https://github.com/openlup/openlup/blob/main/.github/VERSIONING_AND_EOL.md#package-artifact-limits)
+for measured sizes, current caps, the S1 baseline refresh and refusal remedies.
+Artifact checks require a clean package directory; `--manifest-only` supplies no
+artifact evidence.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openlup/outbox",
-  "version": "0.15.0",
+  "version": "0.17.0",
   "private": false,
   "description": "Transactional PostgreSQL outbox rail; development preview.",
   "license": "Apache-2.0",
@@ -37,7 +37,7 @@
     "test:consumer": "node --experimental-strip-types ./scripts/consumer-proof.ts"
   },
   "peerDependencies": {
-    "@openlup/core": "0.15.0"
+    "@openlup/core": "0.17.0"
   },
   "exports": {
     ".": {

package/release-gates.json

@@ -39,15 +39,20 @@
   },
   "pack": {
     "code": {
-      "maxPackedBytes": 32768,
-      "maxFiles": 48
+      "maxPackedBytes": 43008,
+      "maxFiles": 70
     },
     "docs": {
-      "maxPackedBytes": 16384,
+      "maxPackedBytes": 26624,
       "maxFiles": 12
     },
-    "maxPackedBytes": 65536,
-    "maxUnpackedBytes": 262144,
-    "maxFiles": 64
+    "maxPackedBytes": 81920,
+    "maxUnpackedBytes": 266240,
+    "maxFiles": 90,
+    "baseline": {
+      "version": "0.16.0",
+      "packedBytes": 38718
+    },
+    "browserEntries": {}
   }
 }