@openlup/platform 0.23.0 → 0.24.0

package/CHANGELOG.md

@@ -10,6 +10,224 @@ in the source repository.
 
 ## [Unreleased]
 
+## [0.24.0]
+
+- Publishable on the npm `latest` dist-tag as `0.24.0`, from tag
+  `openlup-platform-v0.24.0`.
+
+- Require Zod `^4.6.6` to fix GHSA-mrhx-c7xc-m3w5; oversized constrained
+  request collections fail before element validation accumulates errors.
+- Preserve the observation adapter's accepted minute-precision occurrence timestamps and raw
+  idempotency-key bytes with the updated validator; impossible dates still fail.
+
+- Add the optional `runFulfillmentDispatchWorker.shadowCommandFingerprint` callback for a pure, local adopter command hash in shadow mode. Without it, shadow evidence still hashes the same `JSON.stringify(request)` bytes with SHA-256. The callback must return a lowercase 64-hex SHA-256 digest of the adopter's canonical command bytes, never command contents, credentials or contact data. The package accepts only strings matching `/^[a-f0-9]{64}$/`; invalid output or a throw returns a typed refusal with closed cause `adopter_fingerprint_invalid` or `adopter_fingerprint_failed`, without raw output, exception text or claim/attempt/evidence writes. Stage/live never invoke the callback. The fingerprint is used across shadow claim/readback/attempt, including mapped-attempt replay; shadow never begins, and live preparation must produce the same identity; shadow still performs no provider preparation, credentials lookup or POST.
+- Preserve optional boolean `submissionAttempted` and `responseBodyRead` facts on typed dispatch errors and finalize evidence. `submissionAttempted: false` proves no provider submission was attempted; absence is unknown. `responseBodyRead: true` means the response body was read, including empty or malformed JSON; `false` means reading failed, and absence means there is no body-read evidence. Credential/request-construction failures include explicit non-submission proof; command validation/rebuild retains its closed `not_dispatchable` refusal. No raw body, exception prose or credentials enter these facts; durable projections admit only actual booleans.
+
+Migration: existing callers need no changes. `shadowDispatchEvidence(request)` becomes `shadowDispatchEvidence(request, commandFingerprint?)`; omitting the new optional argument keeps the same evidence bytes and hash. These facts allow adopter classification without inferring uncertainty from retryability. Package classification remains unchanged: definitive rejections (including an unreadable HTTP 400 body) are `not_dispatched`; ambiguous submission and unreadable successful acknowledgements are `unknown`. No release, default binding, route, schedule or activation is added.
+
+- Add inert native unsupported invoicing ports and runner-independent offline adapter conformance for exact recovery, parent identity, scoped absence, declared host capabilities and safe evidence.
+- Document the invoicing design and host boundaries without installing workers, stores, fiscal providers, routes or activation.
+
+- Extract invoice issue sequencing, snapshot/canonical line verification, unchanged allocation, payment evidence and handoff helpers into the existing invoicing entry; retain host payloads, keys, seller/tax policy and routing.
+- Migration: compatibility callbacks preserve existing RPC/provider request bytes, issue fences and handoff descriptors. No native store, D7/O2 behavior, default provider, executor registration or activation is added.
+
+- Add correction and reversal workers to the experimental invoicing entry, preserving durable correction identity, recovery, host event/key semantics and fenced outcomes. The reference host requires an explicit conforming correction bridge; its legacy vendor copy stays unchanged and unselected.
+- Migration: introduce the two pinned managed v2/compatibility forwards with versioned adapter and pgTAP callers. Unkeyed attempted legacy corrections remain visibly unresolved for provider reconciliation. Preview correction references use correctionRef. Native forwards and runtime activation remain separate.
+- See the [M09 forward owner](../../docs/platform/DATA_AND_MIGRATIONS.md#m09-invoicing-forward-design-and-control-approval) for sync-first settlement and permanent-failure parking.
+- Registered limit: multi-reason / late-issue compensation can yield more than one full correction per invoice, as the incumbent does today.
+
+- Add an experimental structural-executor native invoice store, a create/readback issue binding, separate native/managed migration descriptors, and six byte-identical sparse SQL assets. Read-only bounded discovery exposes duty/order IDs before facts are installed. Missing host fiscal facts refuse before writes; local-only document construction retains its previous behavior. Native fresh non-ready preflights settle before dispatch; stale preflight/finalizer results write no failure.
+- Migration: append the three reviewed native duty/effect/payment forwards at positions 77–79 after the unchanged 160000/165000 prefix. Install the complete catalogue. Native child-document and managed base-row corrections have distinct descriptors. Seller revision and activation remain separate.
+
+### Independent native invoicing duties
+
+Experimental invoicing adds `collectInvoiceDuties` and
+`createIndependentInvoiceDutyBinding` for explicitly invoked, separately committed
+duty collection. Native fulfillment no longer waits for accounting readiness or
+invoice requests. Managed dispatch behavior stays unchanged.
+
+Install the full native catalogue, including 190000/191000 before the exact
+reviewed 192000 payment-decoupling forward. Captured settlement and dunning
+recovery survive invoice capture failure; retained paid/handoff facts support
+later repair. New unlinked payment events retain `accountingRequested=false`,
+including after independent issue; historical linked events retain their readback.
+Use owed-duty readback for invoice progress. No payment
+export, provider activation, scheduler registration or fiscal default is added.
+
+- Extract invoice delivery, PDF validation, accepted-document synchronization, payout item recording and document-history/read helpers into the existing invoicing entry; bind the reference host facades through explicit callbacks.
+- Migration: F8 retains A2 payout transport and exact settlement keys; the legacy batch/payment importer preserves donor calls and aggregate results, while package receipt reuse across item scopes is an identity conflict with continued processing and no extra write; distinct recorded receipts require an item-capable host recorder/resolver. F11 retains M04 content, recipient, locale, transport and uncertainty. F9 bounds reference consumers; F12 leaves runbooks and customer correction intent host-owned. Native delivery uses an optional host envelope projection over P4’s store; job store mode binds fenced terminal/backoff outcomes (whole seconds clamp 60..86400, absent/invalid 900, retryable:false parks); callback mode requires terminalFailure before claim; native history requires a safe owned projection. PDF downloads now refuse invalid bytes; the reference panel displays closed diagnostic codes without free-text provider errors. No SQL, activation, executor or fiscal-policy change.
+
+Explicit invoicing composition and first-claim seller revision
+
+PART A: `createInvoiceServices`, `InvoiceServices` and `createInvoiceContribution`
+use the existing `/invoicing` entry. Host selection is default-off; readiness
+precedes factories and claim. Native helpers compose the real P4/P5 store,
+collection, delivery, sync and read-model implementations. Host-specific factories
+retain auth, configuration, transport/query projection and the existing executor,
+registry and lease. Targeted module runs refuse before leasing.
+
+PART B — Migration: native 195000 and managed 195100 are forward-only,
+byte-identical introductions of the approved CTL-M09-4 fixtures. Eligible
+obligations freeze the seller at their first-ever durable claim, independently
+for corrections; retries retain it. Previously claimed legacy obligations keep
+execution-time fallback. Issued documents and installed buyer/line facts are
+unchanged. Native reversals use the correction request branch; managed order
+reversals preserve incumbent results through the seller request wrapper.
+Unknown/unsupported seller reads and order-scoped managed corrections refuse
+before claim. SQL replay conflicts surface as typed identity conflicts.
+
+### Selection and installation boundary
+
+Invoicing remains EXPERIMENTAL and DEFAULT-OFF. The issue/correction/reversal,
+durable duty collection, native store, delivery/document/payout sync, safe history
+and first-claim seller revision helpers are available for explicit host composition.
+Select a provider and capability, bind host ports and establish readiness before
+factories or claim; the structural contribution registers nothing itself. Fiscal
+policy, ownership/authentication, M04 transport, artifact/history projections,
+execution leases and route/job registration remain host responsibilities. No live
+provider, fiscal acceptance or inbox-delivery evidence is established. Adopters
+must not activate unselected or unready invoicing, or infer activation from SQL.
+
+M10 subscription renewal/retry stages remain EXPERIMENTAL, INCOMPLETE and
+DEFAULT-OFF, not for adopter activation: contracts, native stores/executor and
+N1 SQL are present, but runner activation and the G23/N1 host composition,
+correlation, authorization and replay obligations remain pending. Native delivery
+alignment must remain off or shadow until the host composes the renewal runner
+with its G23 admission decorator.
+
+Migration: upgrade core, outbox and platform together from `0.23.0` to `0.24.0`
+for exact internal peers. Install the complete canonical native migration chain
+through position 80 (`20261022195000_invoicing_seller_revision.sql`), including
+invoicing positions 77/78/79 (`190000`/`191000`/`192000`); P5 adds no SQL and P7
+adds position 80. Sparse package projections are not an installation chain.
+Managed installations use their own ordered forwards, including correction
+`193000`/`193100` and seller `195100`; managed descriptor paths are catalogue
+references, not files installed by the npm tarball. Preserve first-claim seller
+snapshots and legacy fallback; there is no retroactive backfill or reversal of
+forward SQL on application rollback. Retain the `0.23.0` shadow/observation retry
+and legacy stock-fingerprint migration precautions when upgrading older rows.
+
+### Limits closed by this set
+
+- The earlier invoicing contract-only/no-SQL/no-worker surface limit is closed:
+  P1b–P7 introduce explicit services, native store and helpers, with CTL-M09-1–4
+  reviewed forwards at native positions 77–80 and the managed correction/seller
+  forwards; see the [design boundary](../../docs/platform/plans/oss-m09-invoicing.md#p7-composition-and-seller-revision).
+  Default activation and live fiscal/provider acceptance remain unclaimed.
+- M08 stock-evidence replay/reopen was already closed in `0.23.0` by position 76;
+  this set does not close its legacy fingerprint conflict or other M08 gaps.
+
+### Known limitations
+
+- Managed dunning exhaustion still pauses active subscriptions; retaining active status needs a managed forward. Native N1 lands the bounded retry/failure repair, with the host obligations below still pending.
+- D8-1: native advisory v2 promo-code candidates/rejection details unavailable.
+- D8-2: native mounted v2 issue/honor/fallback unavailable.
+- D8-3: native acquisition-only mounted issuance/honor unavailable.
+- D8-4: full native/managed eligibility equivalence unavailable.
+- Bundle-1: independent DB human-only actor-kind enforcement absent natively; first in the native-backend parity round.
+- Bundle-2: managed-equivalent actor-kind/email history absent natively.
+- Bundle-3 closes injected-reader M05 mounted admin/feed readback only. Native new-purchase stock read absent despite P5a installed-store proof; deferred second after bundle-1 (owner 2026-10-21); readiness refuses.
+- Bundle-4: incumbent real-PostgreSQL contention only; no exactly-once guarantee.
+- Managed schema/pgTAP retain `44.404`; removal needs owner decision/forward; reference composition supplies it to app code.
+- A1 offline only; account/hosted-time/owner TEST evidence unclaimed; `communications/klaviyo` verification-pending.
+- M05 omitted opt-ins preserve defaults/outputs/read order/schedules/refusals/acceptance-token bytes/SQL.
+- Native inventory adjustment unavailable; address writes refuse readiness. Flat-rate save needs selected port/Core readiness/applied-seed observation.
+- Native shipping audit unavailable; handler swallows best-effort audit failure.
+- Native flat-rate integer bounds (0 through host maximum; reference 100,000 minor units) use request schema, not DB CHECK.
+- Managed ATP/forecast/dated-supply/pagination readback unproved/pending M06.
+- Managed two-session locks/concurrency/uncovered compensation unproved/pending M06.
+- Managed exact-prefix upgrade/ledger unproved/pending M06.
+- Managed address idempotency/conflict/readback unproved/pending M06.
+- Managed successful flat-rate read/save unproved/pending host authority.
+- M06 stock-wait lifecycle/durable timing/staging controls retain C5/C6; busy/try-gate, continuity/flag/TTL transfers are dispositions, not PASS.
+- Shipping national-registry fields/locale-specific `canonicalAddressKey` fold await M16 host market pack/key migration; reference shipping copy stays locale-specific until M16.
+- Native durable prepared storage, method setup, absence reopen and cumulative refunds unavailable; no production installation parity claimed.
+- Typed refusal-envelope forwarding unavailable (`failureReason` only); reusable registration needs host ownership resolution.
+- Incomplete chargebacks stay refunds/unapplied: reclassification bypasses evidence validation into dispute apply; limited operator recovery.
+- Audit compatibility still detects `chargeId`; refund operation identity/original money supply no typed charge identity.
+- M07 follow-up: repair poll can clear host redirect; post-timeout verify never restarts polling; unlocalized poller; fixture builds/never calls handler.
+- M07 follow-up: reference status route wrong-rail witness.
+- M07 follow-up: explicit reference-route refusal for unsupported method setup.
+- M07 follow-up: deployment-neutral disabled-verify reason.
+- M07 follow-up: reference card normalizer missing-amount path; package settling evidence already requires positive money.
+
+- Native delivery alignment stays off or shadow until a host composes the native automatic-renewal runner with the G23 renewal admission decorator. The decorator alone neither composes nor activates the runner.
+- The core fulfillment status map carries localized adopter labels; replace them with host-injected labels or internationalization keys at the host presentation boundary.
+- The warehouse adapter example is opt-in and has offline conformance only; no provider-account proof or activation is established. Exact absence, label create/void and cancellation remain unsupported.
+- After an alignment extension, a deferred renewal operation at the old schedule remains claimed with no reader or reservation effect. Changed terms snapshots conflict under the existing snapshot-conflict rules.
+
+Native parity remains host-owned at these seams. Missing native bindings use the shared `FULFILLMENT_NATIVE_UNSUPPORTED` refusal; no partial write or parity claim is implied.
+
+| Amendment | Host-owned seam and native boundary |
+| --- | --- |
+| G18 | Replacement creation and atomic eligibility/replay receipts; native replacement callback refuses. |
+| G19 | Operator mutations, actor attribution and replay receipts; native mutation callbacks refuse. |
+| G20 | Customer alignment rows; native reader refuses, while the pure delay projection remains callable. |
+| G21 | Commerce list/detail and shipments overview; native read callbacks refuse. |
+| G22 | Authoritative preparation edits, authorization and replay receipts; missing preparation binding refuses before dispatch, after disabled/selection/readiness checks. |
+
+- M08 parity D2 KEEP-GAP: native dispatch finish still loses rejected/unknown error detail.
+- M08 parity KEEP-GAP: immutable stock snapshot/alert evidence storage is absent; cursor JSON is overwritten. Hosts retain referenced evidence.
+- Stock-evidence replay/reopen is CLOSED by native position 76; legacy `0.22.0` alert fingerprints still conflict with `23505`, including after resolution.
+
+### Invoicing registered limitations
+
+These are notes carried from the landed design, not fixes in this preparation.
+
+- M07 `payment_truth_readback` still joins `accounting_documents`: operator
+  ACCESS EXCLUSIVE DDL or denied ACL can block/refuse the call. New unlinked
+  payment events remain `accountingRequested=false` after independent issue;
+  use owed-duty readback for invoice progress (PR #334).
+- Managed multi-reason and late-issue compensation can create more than one full
+  correction per invoice. A later finalizer can be fenced `claim_inactive`, leaving
+  its row `processing`; failed/pending rows on already-corrected parents may never
+  be reclaimed. Reconcile provider identity/evidence, including unresolved attempted
+  legacy corrections. Broader reversal/manual arbitration needs a separately
+  designed replacement forward (PR #329, #330, #348).
+- An in-flight issue can still compensate outside the seller wrapper with
+  `legacy_fallback`; latest-parent reselection retains incumbent behavior.
+  Managed keys are scoped to invoice/provider/reason, and delegated void stores
+  no key; native cross-order reuse refuses. Pre-wrapper native reversal-key
+  retries can conflict after wrapper evidence is added (PR #346, #348).
+- Managed paid/handoff contention (`55P03`) is a visible retryable no-effect
+  refusal with no automatic adapter retry. Fail-soft dispatch can finish without
+  an invoice request; durable recreation can require operator recovery and delayed
+  shipped-without-invoice monitoring (PR #348).
+- A bad host fiscal revision can refuse an entire scoped/provider batch. A null
+  payment `providerRef` falls back to the fiscal provider: hosts must supply explicit
+  payment identity. A failing `store.fail` aborts remaining leased work; retain
+  lease recovery and host retry handling (PR #334).
+- Reversed-duty fact installation can still report owed: read authoritative
+  reversal/duty evidence, never treat that answer as permission to issue.
+  Unsupported reversal and parked document/request residues remain visible and
+  unclaimable; later fact installation/reversal retry can change their diagnostics
+  (PR #332, #334; design phase obligations).
+- Native corrections ride the issue batch; a separate correction operation without
+  a host factory refuses `host_binding_required`. Unknown native seller selection
+  currently maps to non-retryable unsupported; hosts must handle recovery explicitly
+  (PR #348).
+- Delivery visibility must exceed transport timeout. Fenced settlement, database
+  failure or lease expiry can abort a batch and leave unsent leased rows uncertain.
+  Retryable/unsupported transport diagnostics may project as `retryable`; counters
+  omit projection failures/parked mismatches, so inspect durable status/error
+  evidence. Malformed projections and permanently invalid PDFs can retry without
+  an attempt cap (PR #332, #344).
+- Reused settlement-receipt detection continues within one call only; it does not
+  detect another item's reuse in a later run. Legacy host aggregates expose item
+  conflicts through count differences; distinct receipts require an item-capable
+  recorder/resolver (PR #344).
+- Hosts retain accepted-document observation polling and safe history composition.
+  `resolveDownload` must bind the document to the authorized order; the package
+  ticket check compares `documentRef`. Opaque-reference filtering covers its listed
+  schemes only (PR #344).
+- Closed diagnostic policy reduces managed message-only/non-allowlisted errors to
+  `unknown`; an empty/non-string earlier `code` can hide a later closed code. The
+  separate OMS projection retains redacted free text. Missing-order cleanup can
+  log error rather than warn with the same refused/discarded outcome (PR #344, #348).
+- PDF content-type normalization retains OpenLup behavior; signature checks are
+  stricter than donor ASCII decoding. `invoicePdfFilename` falls back to English
+  `invoice`; supply host captions (PR #344).
+
 ## [0.23.0]
 
 - Publishable on the npm `latest` dist-tag as `0.23.0`, from tag
@@ -441,62 +659,3 @@ Native parity remains host-owned at these seams. Missing native bindings use the
 | G20 | Customer alignment rows; native reader refuses, while the pure delay projection remains callable. |
 | G21 | Commerce list/detail and shipments overview; native read callbacks refuse. |
 | G22 | Authoritative preparation edits, authorization and replay receipts; missing preparation binding refuses before dispatch, after disabled/selection/readiness checks. |
-
-## [0.21.0]
-
-- Publishable on the npm `latest` dist-tag as `0.21.0`, from tag
-  `openlup-platform-v0.21.0`.
-- Preview set: core/outbox unchanged, UI private `0.0.0`; published `0.20.0` size baselines, unchanged caps.
-
-### Cumulative M07 status: payment truth and repair surfaces complete for this wave
-
-- Experimental payments/contracts/runtime: unchanged prepared ordering; neutral execution/evidence/readback/conformance, verified truth, first-receipt ingress, method lifecycle/reconciliation; host-owned persistence, translation/failure policy.
-- Native PostgreSQL truth/settlement/later-only alignment; three unchanged sparse SQL projections, not an install chain. Refunds never cancel subscriptions.
-- Repair/recovery/buyer verify inject rail capabilities; unknown rails refuse. Reference BFF retains mapping/schemas/ownership/auth order/transient callbacks. Browser/verify outcomes never prove payment success.
-- Reference-application source (no new export), opt-in repair view: `commerce/paymentStatusClient`, `commerce/paymentVerifyClient`, `payment/components/PaymentStatusPoller`; stored paid alone confirms, redirects require HTTPS, collection/confirmation stay injected, unsupported setup is visible. Exact file/specifier guards refuse broad commerce/operator clients; source-import proof keeps default view unmounted.
-- Truth services/one optional named binder use the host executor, no new schedule/executor. Selectors default-off: nothing activates by default. First-insert adapter fingerprint excludes receipt time/audit.
-- Two experimental example adapter subpaths under `./payments/`, named in the README. Card-processor example: three frozen exports, injected host client/neutral ports; refund creation, split authorization/capture and exact absence unavailable; cancellation needs host support.
-- Regional-processor example: host I/O, Model O aliases, verified observations, purpose-sensitive readback; check certificate validity/notification freshness. Both examples have no import I/O/default binding and await account TEST evidence.
-- Example adapter advisory: mismatched nonzero refusal money stays unknown/manual; trusted document refusals mean customer data correction; configuration mismatches throw before I/O. Unpaid/transient no-dispatch classifications unchanged.
-- Settling money missing/invalid/non-positive or blank currency refuses as amount mismatch; conformance requires positive money. Empty optional transients stop false leak refusals; JSON-escaped transients in diagnostics/readbacks/stored payloads and payer contact in execution results now refuse.
-- Private types reuse canonical money/attempts; unused imports removed, runtime/API unchanged.
-
-Migration: upgrade all `@openlup/*` `0.20.0` → `0.21.0` for exact pins. No schema migration; install the canonical catalogue, not sparse projections. Attempts add optional method selection/transient payer contact; contact is dispatch-only, never persisted/audited/logged/diagnosed. Missing adapter-required input requires exact before-dispatch `notDispatched`. Registration refs/kind/status require host `resolveMethodOwner` client/subscription ownership or are omitted. Lifecycle/normalized nested audit copies typed fields only; conformance scans all for secrets/contact. Adapter-filtered redacted audit never stores raw bodies; typed evidence overrides reader facts, audit bag fills untyped facts; identity/fingerprint exclude bag/receipt time. Other changes need no migration, and nothing rewires a host automatically.
-
-Migration: F2 replaces assumed full refund with `require-evidence`: missing/null kind/amount/operation identity is durably recorded/acknowledged, not applied. Supply original money, stable operation identity and cumulative snapshot, event delta or explicit full reversal (`refund`/`chargeback`); full evidence stays valid. Former default needs `refundEvidencePolicy: "legacy-assume-full"`, also in the reference handler; no native parity implied.
-
-Migration: D11 changes every caller of the reference payment control port (the selected verified ingress, the existing provider webhook handler and the captured reference checkout): apply/post-process redelivery using the first stored receipt instant, not redelivery time, so it cannot shift the cycle again. Replay reads winning receipt evidence and refuses (503) when that instant is unavailable. A legacy pre-fingerprint row takes the later clock once. Retain receipt evidence on upgrade; provider routes are not switched to opt-in ingress.
-
-### Known limitations
-
-- Portable dunning repair has no managed twin: exhaustion still pauses active subscriptions there; retaining active status needs a managed forward.
-- D8-1: native advisory v2 promo-code candidates/rejection details unavailable.
-- D8-2: native mounted v2 issue/honor/fallback unavailable.
-- D8-3: native acquisition-only mounted issuance/honor unavailable.
-- D8-4: full native/managed eligibility equivalence unavailable.
-- Bundle-1: independent DB human-only actor-kind enforcement absent natively; first in the native-backend parity round.
-- Bundle-2: managed-equivalent actor-kind/email history absent natively.
-- Bundle-3 closes injected-reader M05 mounted admin/feed readback only. Native new-purchase stock read absent despite P5a installed-store proof; deferred second after bundle-1 (owner 2026-10-21); readiness refuses.
-- Bundle-4: incumbent real-PostgreSQL contention only; no exactly-once guarantee.
-- Managed schema/pgTAP retain `44.404`; removal needs owner decision/forward; reference composition supplies it to app code.
-- A1 offline only; account/hosted-time/owner TEST evidence unclaimed; `communications/klaviyo` verification-pending.
-- M05 omitted opt-ins preserve defaults/outputs/read order/schedules/refusals/acceptance-token bytes/SQL.
-- Native inventory adjustment unavailable; address writes refuse readiness. Flat-rate save needs selected port/Core readiness/applied-seed observation.
-- Native shipping audit unavailable; handler swallows best-effort audit failure.
-- Native flat-rate integer bounds (0 through host maximum; reference 100,000 minor units) use request schema, not DB CHECK.
-- Managed ATP/forecast/dated-supply/pagination readback unproved/pending M06.
-- Managed two-session locks/concurrency/uncovered compensation unproved/pending M06.
-- Managed exact-prefix upgrade/ledger unproved/pending M06.
-- Managed address idempotency/conflict/readback unproved/pending M06.
-- Managed successful flat-rate read/save unproved/pending host authority.
-- M06 stock-wait lifecycle/durable timing/staging controls retain C5/C6; busy/try-gate, continuity/flag/TTL transfers are dispositions, not PASS.
-- Shipping national-registry fields/locale-specific `canonicalAddressKey` fold await M16 host market pack/key migration; reference shipping copy stays locale-specific until M16.
-- Native durable prepared storage, method setup, absence reopen and cumulative refunds unavailable; no production installation parity claimed.
-- Typed refusal-envelope forwarding unavailable (`failureReason` only); reusable registration needs host ownership resolution.
-- Incomplete chargebacks stay refunds/unapplied: reclassification bypasses evidence validation into dispute apply; limited operator recovery.
-- Audit compatibility still detects `chargeId`; refund operation identity/original money supply no typed charge identity.
-- M07 follow-up: repair poll can clear host redirect; post-timeout verify never restarts polling; unlocalized poller; fixture builds/never calls handler.
-- M07 follow-up: reference status route wrong-rail witness.
-- M07 follow-up: explicit reference-route refusal for unsupported method setup.
-- M07 follow-up: deployment-neutral disabled-verify reason.
-- M07 follow-up: reference card normalizer missing-amount path; package settling evidence already requires positive money.

package/README.md

@@ -1,25 +1,46 @@
 # @openlup/platform
 
+Invoicing exports explicit `createInvoiceServices`, `InvoiceServices` and inert
+`createInvoiceContribution` through `/invoicing`, with no new composition entry.
+`claimInvoiceSellerRevision` reads an injected selection before claim; the pinned
+SQL wrappers persist it for eligible obligations. `InvoiceSellerRevision` is also
+available from the type-only contracts entry. Legacy obligations keep fallback.
+
 Development preview. This package is part of the publishable set with core and outbox; preparation does not establish a registry release or a stable API. Its repository-directory publish command refuses publication; the authorized package-release workflow owns publication.
 
 It holds the runnable server substrate an OpenLup application composes: the Node HTTP runtime, BFF dispatch, scheduling and job leases, blob storage, data gateways, the node-postgres migration runner and bundle composition. Ports and their contracts stay in `@openlup/core/platform-runtime`.
 
-For the prepared `0.23.0` set, read the [adjacent-release migration and known
-limitations](CHANGELOG.md#0230) before selecting the opt-in parity seams.
-Install the complete native chain through position 76; follow the `0.22.0`
-native-row migration notes. Native delivery alignment stays off or shadow until
-a host composes its automatic-renewal runner with G23 admission.
+For the prepared `0.24.0` set, read the [adjacent-release migration and known
+limitations](CHANGELOG.md#0240) before selecting optional services.
+Install the complete native chain through position 80, including invoicing
+positions 77–79 and the first-claim seller revision forward; sparse SQL projections
+are not an install chain. Keep the older native-row migration precautions in the
+release notes when upgrading `0.22.0` data. Native delivery alignment stays off or
+shadow until a host composes its automatic-renewal runner with G23 admission.
 M10 subscription renewal/retry (P1 exports, forward controls, P2 stores/executor,
-native N1 SQL landed) and M09 invoicing selection/type-only contracts (no SQL)
-are **EXPERIMENTAL, INCOMPLETE and DEFAULT-OFF**, not for adopter activation.
-No runner is activated; G23/N1 host obligations remain pending.
+native N1 SQL) remains **EXPERIMENTAL, INCOMPLETE and DEFAULT-OFF**, not for
+adopter activation; G23/N1 host obligations remain pending.
+M09 invoicing remains **EXPERIMENTAL and DEFAULT-OFF**, available for explicit
+provider/capability selection and ready host composition, including issue,
+correction, independent duties, delivery/read-side and seller revision helpers.
+Adopters must not activate unselected or unready invoicing; installation and
+inert contributions register no runner, worker, route or schedule.
 M06 managed-host proof classes remain pending in the
 [M06 parity ledger](../../docs/platform/plans/oss-m06-stock-reservations-delivery.md#parity-pending-rows).
-Size comparison uses the published `0.22.0` tarball. Preparation and offline
+Size comparison uses the published `0.23.0` tarball. Preparation and offline
 adapter evidence grant no publication or provider-account certification.
 
 Longer module recipes live in the [platform package reference](../../docs/platform/PLATFORM_PACKAGE_REFERENCE.md).
 
+The prepared set requires Zod `^4.6.6` for GHSA-mrhx-c7xc-m3w5.
+Public quote requests retain their collection limits and valid-input behavior;
+oversized collections now fail with the size error before accumulating invalid
+element errors. Package API and installed-consumer checks remain required.
+The observation adapter explicitly retains minute-precision timestamps
+alongside seconds/fractions, compact offsets and local timestamps. Calendar
+validation still rejects impossible dates; validation never rewrites the raw
+timestamp used in the webhook's idempotency key.
+
 ## Package surface
 
 `release-gates.json` declares kind `rail`: this foundation provides runtime infrastructure over core ports, matching the architecture's rail responsibility. Its experimental entries each bind a declaration snapshot and package-owned smoke tests. The API checker reads this same inventory.
@@ -45,7 +66,7 @@ Longer module recipes live in the [platform package reference](../../docs/platfo
 | `./payments` | Experimental prepared-attempt ordering with injected persistence, execution and failure policy; contracts at `./payments/contracts`. |
 | `./fulfillment`, `./fulfillment/contracts` | [Experimental fulfillment services, contracts and status canon](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#fulfillment-contracts). |
 | `./subscriptions`, `./subscriptions/contracts` | Default-off, incomplete; [experimental subscription contracts and renewal port](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#subscription-contracts). |
-| `./invoicing`, `./invoicing/contracts` | Default-off, incomplete invoicing selection and type-only contracts; no SQL or activation. |
+| `./invoicing`, `./invoicing/contracts` | Default-off invoicing contracts and independent duty collection; no provider activation. |
 | `./inventory` | Experimental schemas/ports, handlers, native stores, projection, injected forecast and SQL descriptor; `./inventory/contracts` DTOs. |
 | `./catalog` | Experimental neutral catalog schemas, drafts, reads, media source packs and publication ports |
 | `./catalog/contracts` | Dependency-free catalog DTOs, media resolver, authority and canonicalization helpers |
@@ -710,4 +731,65 @@ Experimental `@openlup/platform/invoicing` exposes `readInvoiceCapabilities`;
 Frozen facts, correction recovery, exact absence, owed duties and host-only fiscal,
 artifact, delivery, payout and owned-history seams are described in the
 [invoicing reference](../../docs/platform/PLATFORM_PACKAGE_REFERENCE.md#invoicing-contracts).
-No store, worker, adapter, route or activation is supplied by this contract step.
+The contract entry supplies no executor or activation.
+`createNativeUnsupportedInvoicePorts` supplies inert typed refusals for every
+host, store and provider seam. `runInvoiceAdapterConformance` checks adapter-owned
+offline fixtures; its sanitized evidence does not establish live fiscal readiness.
+
+Issue helpers in `invoicing` preserve claim/preflight/projection/fresh-money/
+create/fenced-finalize order. Hosts bind compatibility payloads, seller/date/tax
+policy, captions, event descriptors and key scopes. Canonical and legacy line
+checks share the unchanged donor allocation; handoff helpers register no job or
+executor. Eight issue/line/payment/handoff cases join the existing package smoke
+selection. Continuity cutover and activation remain separate.
+
+Correction and reversal workers preserve durable identity, recovery and fenced
+outcomes through host callbacks. The reference host requires a conforming
+correction bridge; the legacy vendor method stays unselected. Reversal handlers pass
+through the RPC action (`voided`, `correction_requested`, `corrected`, `no_invoice`). The required package
+selection includes correction/reversal witnesses in `test/invoicing/contracts.test.ts`.
+See the [invoicing design](../../docs/platform/plans/oss-m09-invoicing.md#p3-correction-and-reversal-boundary)
+for managed migration and reconciliation limits.
+
+See the [M09 forward owner](../../docs/platform/DATA_AND_MIGRATIONS.md#m09-invoicing-forward-design-and-control-approval) for the registered managed-correction limit and follow-up.
+
+`createPostgresInvoiceStore` uses a caller-owned structural executor for native
+owed duties, split fact leases, claims and fenced issue/correction results.
+Missing host facts refuse before writes; clearance remains host work. Delivery
+requires an explicit host envelope projection and M04 transport. `INVOICING_MIGRATIONS` separates native child-document and managed
+base-row correction storage. Install the complete native catalogue, not its
+seven sparse byte-identical SQL assets. The local-only Postgres adapter consumes
+this store without claiming fiscal parity or registering a worker. The
+[invoicing architecture owner](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#invoicing-contracts)
+describes reversal recovery, capture faults and cutover fencing.
+`collectInvoiceDuties` and `createIndependentInvoiceDutyBinding` collect retained
+paid/handoff duties through separately committed store phases. Hosts invoke them
+outside payment and fulfillment work; missing facts remain owed. The pinned
+payment-decoupling SQL is a sparse catalogue projection, requiring the full P4
+native chain. See the architecture owner for continuity and activation limits.
+
+`runNativeInvoiceIssueJob` supplies the native create/readback binding over
+explicit local/fresh money and provider ports. Fresh non-ready results settle
+before returning; stale results write no failure. No scheduler or default
+composition is registered. Operator DDL/ACL limits of the unchanged M07 readback
+remain registered in the architecture owner.
+
+For bounded duty discovery before facts exist, including cursor continuation past
+unavailable facts, follow the [invoicing architecture owner](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#invoicing-contracts).
+
+The invoicing read side adds `runInvoiceDeliveryJob`, `assertInvoicePdf`,
+`invoicePdfFilename`, `syncAcceptedInvoiceDocuments`,
+`syncInvoicePayoutSettlements`, `resolveInvoiceDocumentHistory` and
+`createInvoiceReadModel`. Hosts supply authorization, storage, M04 transport,
+terminal/backoff callbacks or the native store, and safe native history projection. See the
+[read-helper recipe](../../docs/platform/PLATFORM_PACKAGE_REFERENCE.md#invoicing-read-helpers).
+
+`createInvoiceServices` and `createInvoiceContribution` compose the existing
+helpers through `/invoicing`, with explicit selection, default-off and readiness
+before execution. Native collection, issue, delivery, document/payout sync and
+history use their module implementations; host facades may bind factories where
+transport or query projection is host-owned. No executor is installed.
+`claimInvoiceSellerRevision` selects a seller before leasing. The optional native
+store seller binding and managed wrappers persist its first-ever claim revision;
+legacy fallback and forward-only migration limits are owned by the
+[M09 migration section](../../docs/platform/DATA_AND_MIGRATIONS.md#m09-invoicing-forward-design-and-control-approval).

package/dist/fulfillment/contracts/dispatch.d.ts

@@ -90,6 +90,10 @@ export interface FulfillmentOperationError {
     status: number | null;
     retryable: boolean;
     mayHaveSucceeded: boolean;
+    /** Whether provider submission was attempted; absent means unknown, never proven false. */
+    submissionAttempted?: boolean;
+    /** Whether the HTTP response body was read, including empty or malformed JSON; absent means no body-read evidence. */
+    responseBodyRead?: boolean;
     /** Machine cause only; never an arbitrary exception message. */
     cause?: string;
 }

package/dist/fulfillment/dispatchProjection.d.ts

@@ -19,7 +19,7 @@ export declare function durableStrings(priorCount?: number): {
 /** Copy only the durable allowlist, including when an adapter object has extra runtime properties. */
 export declare function dispatchEvidence(evidence: DispatchEvidence): DispatchEvidence;
 /** Shadow has a local command identity; it never invokes a provider or resolves credentials. */
-export declare function shadowDispatchEvidence(request: FulfillmentDispatchRequest): DispatchEvidence;
+export declare function shadowDispatchEvidence(request: FulfillmentDispatchRequest, commandFingerprint?: string): DispatchEvidence;
 export declare function dispatchResult(result: FulfillmentDispatchResult): FulfillmentDispatchResult;
 export declare function acceptedProviderProof(record: DispatchRecord | null): record is DispatchRecord & {
     externalRef: string;

package/dist/fulfillment/dispatchProjection.js

@@ -22,6 +22,8 @@ export function operationError(error) {
     const cause = typeof error.cause === "string" ? privacy.token(error.cause, value => /^ack(?::[A-Za-z0-9_]{1,96}){0,2}$/u.test(value) ? value.slice(0, 180) : null) : null;
     return { code, status: Number.isInteger(error.status) && error.status >= 100 && error.status <= 599 ? error.status : null,
         retryable: error.retryable === true, mayHaveSucceeded: error.mayHaveSucceeded === true,
+        ...(typeof error.submissionAttempted === "boolean" ? { submissionAttempted: error.submissionAttempted } : {}),
+        ...(typeof error.responseBodyRead === "boolean" ? { responseBodyRead: error.responseBodyRead } : {}),
         ...(cause ? { cause } : {}), ...(privacy.redactedFieldCount ? { redactedFieldCount: privacy.redactedFieldCount } : {}) };
 }
 // The fulfillment opaque-ID rule; never accept free-form metadata as a reference.
@@ -78,10 +80,10 @@ export function dispatchEvidence(evidence) {
     };
 }
 /** Shadow has a local command identity; it never invokes a provider or resolves credentials. */
-export function shadowDispatchEvidence(request) {
+export function shadowDispatchEvidence(request, commandFingerprint) {
     if (!request.selection.providerRef || !request.lines.length || request.lines.some(line => !Number.isSafeInteger(line.quantity) || line.quantity <= 0))
         throw new Error("dispatch_shadow_command_invalid");
-    return dispatchEvidence({ commandFingerprint: createHash("sha256").update(JSON.stringify(request)).digest("hex"),
+    return dispatchEvidence({ commandFingerprint: commandFingerprint ?? createHash("sha256").update(JSON.stringify(request)).digest("hex"),
         contactRevision: request.contactRevision, providerRef: request.selection.providerRef,
         carrierRef: request.selection.carrierRef, serviceRef: request.selection.serviceRef,
         transcript: { itemCount: request.lines.length, items: request.lines.map(line => ({ skuRef: line.skuRef, quantity: line.quantity,

package/dist/fulfillment/omnipack/client.js

@@ -58,24 +58,32 @@ async function requestJson(fetchImpl, config, operation, path, init, refuseRedir
     let lastError = null;
     for (let attempt = 1; attempt <= attempts; attempt += 1) {
         let submitted = false;
+        let responseBodyRead;
+        const dispatchFacts = () => operation === "createOrder" ? { submissionAttempted: submitted,
+            ...(responseBodyRead !== undefined ? { responseBodyRead } : {}) } : {};
         try {
             const base = new URL(config.baseUrl);
             const url = new URL(path, base);
             if (url.origin !== base.origin || url.username || url.password || url.protocol !== "https:")
                 throw new Error("Invalid fulfillment path");
             const response = await fetchWithTimeout(fetchImpl, url, config, init, () => { submitted = true; });
+            responseBodyRead = false;
+            const body = await readJsonBody(response).then(value => { responseBodyRead = true; return value; }).catch(error => {
+                if (response.ok)
+                    throw error;
+                return null;
+            });
             if (response.ok)
-                return await readJsonBody(response);
+                return body;
             const retryable = method === "GET" && isRetryableStatus(response.status);
             // A failed body read cannot erase the rejection status already received.
-            const body = await readJsonBody(response).catch(() => null);
-            lastError = new OmnipackProviderError({
+            lastError = Object.assign(new OmnipackProviderError({
                 operation,
                 status: response.status,
                 code: refuseRedirectRetry && response.status >= 300 && response.status < 400 ? "redirect_refused" : readProviderErrorCode(body) ?? `http_${response.status}`,
                 retryable,
                 mayHaveSucceeded: mayPostHaveSucceeded(method, response.status),
-            });
+            }), dispatchFacts());
             if (!retryable || attempt === attempts)
                 throw lastError;
         }
@@ -83,13 +91,13 @@ async function requestJson(fetchImpl, config, operation, path, init, refuseRedir
             const retryable = method === "GET" && attempt < attempts;
             lastError = submitted && error instanceof OmnipackProviderError
                 ? error
-                : new OmnipackProviderError({
+                : Object.assign(new OmnipackProviderError({
                     operation,
                     status: null,
                     code: diagnoseRedirectFailure && isRedirectRefusal(error) ? "redirect_refused" : "network_error",
                     retryable,
                     mayHaveSucceeded: submitted && mayPostHaveSucceeded(method, null),
-                });
+                }), dispatchFacts());
             if (!retryable || (refuseRedirectRetry && lastError.code === "redirect_refused"))
                 throw lastError;
         }

package/dist/fulfillment/omnipack/index.js

@@ -242,10 +242,13 @@ export function createOmnipackFulfillmentAdapter(config) {
                         return { kind: "refused", refusal: refusal("unsupported_event", "normalize") };
                     const original = payload;
                     // Validate calendar fields here only; keep compact offsets and local
-                    // timestamps accepted by the base parser, without rewriting key bytes.
+                    // timestamps and minute precision accepted by the base parser,
+                    // without rewriting key bytes.
                     if (original.occurredAt !== undefined && original.occurredAt !== null
                         && (typeof original.occurredAt !== "string" || !timestamp(original.occurredAt)
-                            || !z.iso.datetime({ offset: true, local: true }).safeParse(original.occurredAt.replace(/([+-]\d{2})(\d{2})$/u, "$1:$2")).success))
+                            || !z.iso.datetime({ offset: true, local: true })
+                                .or(z.iso.datetime({ offset: true, local: true, precision: -1 }))
+                                .safeParse(original.occurredAt.replace(/([+-]\d{2})(\d{2})$/u, "$1:$2")).success))
                         return { kind: "refused", refusal: refusal("malformed", "normalize"), diagnostics: { invalidTimestamp: true } };
                     const rejectedCorrelationRefs = [original.orderId, original.providerOrderId, original.orderNumber, original.fulfilmentNumber]
                         .filter(value => value !== undefined && value !== null && (typeof value !== "string" || !correlationReference(value, config.observationCodecs))).length;

package/dist/fulfillment/providerDispatchWorker.d.ts

@@ -16,8 +16,46 @@ export declare function runFulfillmentDispatchWorker(input: {
         mode: DispatchRecord["mode"];
         batchLimit: number;
     };
+    /** Pure local shadow fingerprint: a lowercase 64-hex SHA-256 digest of the adopter's canonical command bytes. Invalid output or a throw refuses before evidence writes. Never return raw command/PII. Used across shadow claim/readback/attempt; shadow never begins, and live preparation must produce the same identity. */
+    shadowCommandFingerprint?: (request: FulfillmentDispatchRequest) => string;
     now?: () => Date;
 }): Promise<{
+    redactedFieldCount: number;
+    ok: boolean;
+    failures: number;
+    reason: "adopter_fingerprint_invalid" | "adopter_fingerprint_failed";
+    refusal: {
+        reason: "malformed";
+        phase: "prepare";
+        retryable: false;
+        cause: "adopter_fingerprint_invalid" | "adopter_fingerprint_failed";
+    };
+    skipped: boolean;
+    checked: number;
+    updated: number;
+    mode: "shadow" | "stage" | "live";
+    replayed: number;
+    providerCalls: number;
+    readBacks: number;
+} | {
+    redactedFieldCount?: undefined;
+    ok: boolean;
+    failures: number;
+    reason: "adopter_fingerprint_invalid" | "adopter_fingerprint_failed";
+    refusal: {
+        reason: "malformed";
+        phase: "prepare";
+        retryable: false;
+        cause: "adopter_fingerprint_invalid" | "adopter_fingerprint_failed";
+    };
+    skipped: boolean;
+    checked: number;
+    updated: number;
+    mode: "shadow" | "stage" | "live";
+    replayed: number;
+    providerCalls: number;
+    readBacks: number;
+} | {
     redactedFieldCount: number;
     ok: boolean;
     skipped: boolean;

package/dist/fulfillment/providerDispatchWorker.js

@@ -53,8 +53,26 @@ export async function runFulfillmentDispatchWorker(input) {
             for (let remapCount = 0;; remapCount += 1) {
                 const request = { ...mappedCandidate, requestKey };
                 stage = "dispatch_command_prepare_failed";
+                let shadowFingerprint;
+                if (input.config.mode === "shadow" && input.shadowCommandFingerprint) {
+                    let value;
+                    let cause;
+                    try {
+                        value = input.shadowCommandFingerprint(request);
+                    }
+                    catch {
+                        cause = "adopter_fingerprint_failed";
+                    }
+                    if (!cause && typeof value === "string" && /^[a-f0-9]{64}$/.test(value))
+                        shadowFingerprint = value;
+                    else
+                        cause ??= "adopter_fingerprint_invalid";
+                    if (cause)
+                        return { ...result, ok: false, failures: result.failures + 1, reason: cause,
+                            refusal: { reason: "malformed", phase: "prepare", retryable: false, cause }, ...diagnostics() };
+                }
                 const prepared = input.config.mode === "shadow"
-                    ? { kind: "prepared", evidence: shadowDispatchEvidence(request) }
+                    ? { kind: "prepared", evidence: shadowDispatchEvidence(request, shadowFingerprint) }
                     : await input.provider.prepare(request);
                 if (prepared.kind === "refused") {
                     result.ok = false;