@openlup/outbox 0.14.0 → 0.16.0

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 ## [Unreleased]
 
+## [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
+  `openlup-outbox-v0.15.0`.
+
+- Republish with the exact `@openlup/core` `0.15.0` peer pin in the set that adds `@openlup/platform`; Outbox APIs, runtime behavior and shipped SQL are unchanged.
+
 ## [0.14.0]
 
 - Publishable on the npm `latest` dist-tag as `0.14.0`, from tag

package/README.md

@@ -28,7 +28,7 @@ Prune defaults to 30 days for processed and 90 for discarded, in batches of 500.
 
 ## Readiness and verification
 
-<!-- openlup-doc-impact {"unit":"outbox-rail","digest":"sha256-207a9646260642afdf50398c025d2305f1126fc89a45a5652ededd14bef1f402","reason":"The Outbox version and exact Core peer pin move together from 0.13.1 to 0.14.0. This preparation changes no Outbox API, runtime, SQL, readiness responsibilities or verification step."} -->
+<!-- openlup-doc-impact {"unit":"outbox-rail","digest":"sha256-9445d29261300fbb26fc654d53e7c99ac9bde297ba426d2d000906ab9bc8e598","reason":"The manifest moves from 0.14.0 to 0.15.0 with the exact @openlup/core 0.15.0 peer pin, for the set that first publishes @openlup/platform, and the reference outbox inventory test reads the expected set version from the live core manifest instead of a pinned value. The rail, its ports, readiness and verification described here are unchanged."} -->
 
 Compose the contribution with `@openlup/core/readiness`, actual loaded package metadata, selected-adapter schema observations and host bindings to the exact contribution run/handle functions before activating the exact new candidate. Only `ready` admits; `unknown` and `unsatisfied` leave the serving version running. Descriptors are inert; the builder supplies the same actual event identities and effective timeouts after lease acquisition. The default schema declaration describes catalog existence and overloads; it does not prove bodies, ACL or recovery. Use framework-free fence conformance from `./testing` and real transactional proof for your adapter. No ambient database URL is used by the packed proof.
 
@@ -65,6 +65,15 @@ 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 omit the Zod directory copy because they run
+builtin-only proof stubs or stop before the packed consumer starts. The six
+actual consumer invocation cases retain their ordinary Zod copy and installation
+checks. Every case, ownership assertion and cleanup deadline remains in place.
+
+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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openlup/outbox",
-  "version": "0.14.0",
+  "version": "0.16.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.14.0"
+    "@openlup/core": "0.16.0"
   },
   "exports": {
     ".": {