@openlup/platform 0.29.0 → 0.30.0

package/CHANGELOG.md

@@ -10,6 +10,156 @@ in the source repository.
 
 ## [Unreleased]
 
+## [0.30.0]
+
+- Publishable on the npm `latest` dist-tag as `0.30.0`, from tag
+  `openlup-platform-v0.30.0`.
+
+### Qualified reference-source installation and retained imports
+
+Migration: The reference-source PostgreSQL binding still selects the unchanged
+88-unit legacy plan by default. Fresh PostgreSQL 16 installations may explicitly
+select `qualified-v2` and either `installer-managed` or `operator-provisioned`
+roles. The actual migration session must use the declared SUPERUSER login that
+owns the database; it may be the cluster bootstrap login or a separate declared
+migration login. Runtime and optional restore logins must be distinct restricted
+non-owner principals. Admission checks the actual role graph and capabilities;
+selection alone establishes no installation or managed-host readiness.
+
+Migration: Qualified bootstrap/runtime SQL and the reference selection binding
+are source-tree inputs, not a complete installation catalogue shipped in the npm
+package. The E-only 89-unit shape remains a separate historical expectation.
+Selecting the retained-import tail requires the explicit restore binding and its
+90-unit catalogue. This fresh-generation route does not convert a legacy database.
+
+Migration: The qualified retained-import tail gives the restore login EXECUTE
+only on `client_import_retained_row` and
+`subscription_cycle_import_retained_row`. These fixed routines insert an absent
+row, replay an identical retained row and refuse a differing row with `23505`;
+non-`origin` replication mode refuses with `55000`. Ordinary runtime writes keep
+their existing lifecycle and delivery-alignment behavior. Restore parents,
+history, frozen terms and identity mappings through their existing owners; the
+two routines do not provide a full-store restore or stable upgrade service.
+
+### Added
+
+Add the experimental Node-only `@openlup/platform/lifecycle` entry with explicit
+application-file snapshot planning and apply. It preserves unmanaged files and
+customized upstream-unchanged files, refuses divergent changed paths before
+writes, and recognizes exact completed states for interruption/resume. It needs
+no optional SDK and activates no route, timer, provider or installer.
+
+The same entry exports `inspectLegacyPostgresInstallRoles` for one fixed,
+read-only PostgreSQL role observation through an injected query handle. Its
+`legacy-fresh-bootstrap-role-prerequisites` / `rolePrerequisitesMet` result
+retains the immutable legacy bootstrap's superuser, shared-login, mode and
+pre-existing-role refusals. It adds no DDL, role support or install-readiness claim.
+
+The owner-authorized byte reserve after the direct directory-prefix and catalog
+binding repair sets code-gzip 1,743,872 B, tarball 2,029,568 B and unpacked
+9,447,424 B caps. The supervisor computed each as 5% above the actual measured
+1,660,249 / 1,932,801 / 8,996,893 B, rounded up to KiB. These fixed limits
+supersede the historical exact-minimum C+D allocation and grant no automatic
+future increases or additional programme scope. Code/total file caps remain
+2574/2628; docs/browser caps, released baseline, versions and locks stay exact.
+Actual approved-input remeasurement remains required because metadata edits can
+change packed bytes; this budget decision establishes no final review or proof.
+
+### Migration
+
+Select this entry explicitly from a Node application. Supply immutable UTF-8
+predecessor/candidate snapshots, an absolute canonical root and separately
+observed schema-range evidence. Hold an exclusive maintenance window. Apply
+rechecks the current tree; a changed managed file with divergent local bytes
+requires adopter reconciliation. Existing managed path components must match
+their actual directory-entry spelling exactly; a filesystem case or normalization
+alias does not authorize changing an unlisted entry. Per-file rename is not an
+all-files transaction or a hostile-concurrency/power-loss guarantee. No SQL, dependency install,
+version marker or deployment runs, and file completion does not establish their
+compatibility or completion. Keep database expand/contract and dependency
+provenance work at their existing owners.
+
+- Add an optional trusted-source session admission observation to the experimental PostgreSQL migration runner. It runs once under the existing migration lock after exact-prefix validation and before status, dry-run or pending SQL; existing sources retain their current queries and execution.
+
+### Added
+
+- Experimental operations contracts/browser/server subpaths expose existing
+  settings, pipeline-read, alert overview, watchdog delivery and control-plane
+  behavior through injected host ports. The public reference binds these owners.
+
+### Migration
+
+- Existing reference imports remain compatible. Select the new operations entries
+  explicitly; imports register no route, job or provider. Identity membership and
+  tracking effects retain their existing owners.
+- Native control-plane storage requires the complete canonical native prefix,
+  including the job ledger and `20260814010000_platform_control_plane.sql`.
+  The packaged SQL is a sparse unchanged projection. Supply current capability-local
+  operator authority, routine EXECUTE and underlying relation grants; no managed
+  parity or hosted-provider certification is established.
+
+### Packaging
+
+- Code/total file limits are 2,574/2,628. After the 0.29.0 main integration, the
+  operations candidate measures 2,553 code files and 2,607 total files. The remaining 21
+  files are allocated to the seven already-authored B/C/D production TypeScript
+  files (4/2/1), each packaged as source, JavaScript and declarations. This is a
+  finite source-derived forecast, not an executed B–D package result or capacity
+  for later modules. Each stacked candidate must pass its actual pack checks;
+  additional files or byte-limit crossings need another bounded review.
+- Integrated main's byte, documentation-file and browser limits are unchanged.
+  Combining or deleting contracts solely to reduce the count would add ownership and proof churn without
+  changing the required capability.
+
+### Added
+
+Add the experimental Node-only `@openlup/platform/portability` entry for verified,
+bounded object copy/resume and compatible PostgreSQL row capture/restore through
+injected transaction handles. Object reads distinguish absent, denied and
+unavailable; private filesystem publication preserves bytes, metadata and source
+lineage with an explicit process-owner access policy. Row replay is exact and
+conflicts refuse atomically; every enabled user INSERT trigger refuses.
+
+Filesystem publication and readback share one encoded-descriptor byte ceiling
+covering admitted Unicode metadata; oversize encodings refuse before publication.
+Filesystem locators hash JSON-encoded logical keys, preserving distinct admitted
+strings including lone UTF-16 surrogates. This first unpublished layout has no
+legacy-format migration or fallback.
+
+The bounded M14 B budget reads approved the initial code-gzip minimum of
+1,650,493 bytes, exactly 128 bytes for that necessary Unicode repair and 10 bytes
+for exact string-key identity. The current measured minimum is 1,650,631 bytes,
+cumulatively 2,631 above 1,648,000.
+This allocates no additional forecast headroom. Other byte, file, docs and
+browser limits and the released baseline are unchanged by this decision; later
+candidates still need their own actual package measurement.
+
+### Migration
+
+Select the entry explicitly. Install the canonical target catalogue
+and qualify the source/target privileges separately; this API does not install
+schema, copy migration ledgers, map managed identities or activate executors.
+Changed-row catch-up, guarded-domain import and hosted effect-time fencing remain
+M14 dependencies. Local synthetic proof does not certify complete-store transfer,
+provider revocation or a stable migration service.
+
+Node host shutdown now fences its stopped scheduler registrations and waits for
+admitted callbacks, including pending lock acquisition and asynchronous unlock,
+before closing the dedicated advisory-lock session. Other hosts remain excluded
+until the running job releases ownership. Shutdown still attempts the listener
+and lock cleanup, caches its promise and aggregates failures in the existing order.
+PostgreSQL advisory locks now refuse locally pending or held numeric keys,
+including colliding job IDs, so a dedicated session cannot reenter a job lock.
+Failed acquisition permits a later attempt; failed unlock remains reserved until
+the session closes.
+
+Migration: `NodeSchedulerAdapter.stopAll()` explicitly returns `Promise<void>`
+instead of `void`. Await it before disposing resources used by admitted callbacks.
+It fences/stops current timers synchronously and supports later registrations.
+The only in-tree production caller, `createNodeHost`, awaits that drain before
+closing the lock; its public `stop(): Promise<void>` signature remains unchanged.
+Custom implementations of `NodeSchedulerAdapter` must return the drain promise.
+
 ## [0.29.0]
 
 - Publishable on the npm `latest` dist-tag as `0.29.0`, from tag
@@ -395,141 +545,3 @@ reference handle or schema requirement is forwarded.
 Configured recovery/purchase elements use explicit host paths and clients. No SQL, version, serving
 activation or source-release snapshot changes. Regenerated account-support and
 composition API reports describe these additions; no sibling API report changed.
-
-## [0.27.0]
-
-- Publishable on the npm `latest` dist-tag as `0.27.0`, from tag
-  `openlup-platform-v0.27.0`.
-
-- Bind experimental native new-purchase previews to the existing ATP reader through the inventory and reference composition, protecting subscription stock without another stock calculation.
-- Migration: PostgreSQL hosts supply the optional `stockSourceKey` binding dependency to enable `newPurchaseStockReadPort`. The preview then binds with no unsupported reason; an absent or blank key reports `inventory_stock_source_key_required`. Admin readiness is unchanged; a required preview leaves reference readiness refused until the key is supplied.
-- Migration: Native previews subtract all live holds, remaining active subscription demand inside 14 days and channel exposure. For 20 units with 5 held and 7 still due, both availability fields report 8; a provider-tag-filtered preview counting only 2 of those held units would report 11 for new purchases. Credited own-cycle holds are not subtracted twice. Exposure of 4 reduces a budget of 11 to 7.
-- Migration: Native budgets clamp at zero, stale stock contributes zero to ATP, and local-only stock has no native source. The native preview refuses own-order exclusions or a horizon other than 14 days as `native_stock_read_options_unsupported`; it provides no one-time or replacement allocation seam.
-- Migration: Managed hosts apply the managed forward `20261025109000_inventory_new_purchase_stock_read.sql` after the managed migration prefix (`public.inventory_new_purchase_stock_read(p_skus jsonb, p_as_of timestamptz) RETURNS jsonb`, service_role-only execution), then supply optional `stockRpc` to the inventory binding (also forwarded through the reference store). An injected `newPurchaseStockReadPort` wins; without either dependency the existing `inventory_new_purchase_stock_reader_required` remains.
-- Migration: Managed preview quantities equal ATP with renewal exemption fixed false, preserving M10 provider-tagged holds, safety, 14-day uncredited demand and channel exposure. Both availability fields now include demand and clamp at zero. Other horizons and own-order exclusions refuse `managed_stock_read_options_unsupported`; SQL accepts at most 200 requested array items before deduplication and refuses a NULL as-of timestamp as `inventory_stock_as_of_invalid` (SQLSTATE `22023`). The managed preview treats ANY stale provider-stock evidence for the SKU as stale (fail-safe; exact when one provider kind exists); quantities remain unchanged and the allocator's own stale refusal stays authoritative.
-- Migration: Managed `source` is "provider" iff ATP returns a row for the SKU; otherwise it is "missing".
-
-- Add experimental `@openlup/platform/commerce` neutral schema cores, contract helpers and ports, plus type-only browser-safe `@openlup/platform/commerce/contracts`. Reference bindings extend these cores with existing profile, locale, fiscal and provider policy. No version or artifact cap changes.
-Migration: Commerce-owned ports and generic records may be imported from `commerce/contracts`. Pricing DTOs remain at `@openlup/platform/pricing/contracts` directly, without convenience re-exports from commerce. Reference exported names remain available.
-Migration: `commerceOfferVersionSchema` now validates opaque offer tokens of at most 40 characters, using the lower-case token grammar (D1).
-Migration: The commerce quote port's out-of-band `CreateQuoteOptions` now accepts the server-bound `offerVersion`; the M05 options and quote DTOs remain their existing owner (D2).
-Migration: Reference quote context types additionally carry optional shipping and acquisition terms using their existing package definitions (D3).
-Migration: Checkout expected-quote acceptance and price-change responses now admit acquisition expectations independently of totals; invalid revisions and discount bounds are refused (D4).
-Migration: Configurator intents additionally admit acquisition capability, opaque `offerVersion` and bounded `minimumUnits` asks (D5).
-Migration: A supplied minimum replaces the injected host default for untrusted intent validation only; it does not authorize server checkout admission (D6).
-Migration: `offerAvailabilityRequestItems` projects one unit per variant in input order and the supplied checkout mode (D7).
-Migration: The reference configurator-to-quote mapper forwards an admitted acquisition capability, leaving absent capabilities absent (D8). This does not activate an acquisition issuer or offer guard.
-Migration: `CheckoutOfferPolicyPort<Intent, Quote>` and its bound/refused result are available as types only (D9). Offer resolution, evidence execution and the starter guard remain outside K1 and are deferred to K2a.
-Migration: Reference recovery policy, nominal errors and order-contact helpers delegate to the package with identity preserved. Neutral checkout, resume and defaults schema factories require explicit host bindings; their reference extensions retain existing acceptance, parsed output and error paths.
-Migration: `commerce/server` is a reserved empty Node-only entry; browser consumers continue to use `commerce` and `commerce/contracts`. Canonical order-money and commerce outbox payload validation are available from `commerce`; host quote/draft schemas are injected with the existing validation behavior.
-Migration: Checkout admission refuses unbound offer/minimum asks while no server offer resolver is composed, retaining the host floor for ordinary requests; untrusted intent parsing still accepts those asks.
-Migration: The commerce quote port requires request, response and host-options type parameters; the reference binds the existing pricing definitions and retains its named types. This removes an unnecessary pricing declaration closure without copying its contracts or changing pricing behavior.
-- Add browser-safe `@openlup/platform/pricing/browser` with direct re-exports of the existing quote primitive factory and acquisition capability/expectation schemas. Reference imports retain symbol identity and validation behavior; the pricing root and contracts entry are unchanged.
-Migration: Regenerated `communications.api.md`, `fulfillment.api.md` and `inventory.api.md` change declaration order only: TypeScript emits union and enum members in literal-creation order across the program. For `defaultCommunicationPurposeRegistry`, before: `"transactional" | "marketing_launch_offer" | "marketing_newsletter" | "tester_program" | "subscription_dunning" | "admin_notification"`; after: `"transactional" | "subscription_dunning" | "marketing_launch_offer" | "marketing_newsletter" | "tester_program" | "admin_notification"`. Communications newsletter, fulfillment and inventory enum members likewise appear in a different order. The member sets and all types are unchanged; type consumers are unaffected and need no code or SQL migration.
-
-- K2 lands no SQL. A dedicated later PR, L1, lands all nine reviewed managed M11 slots (`scripts/fixtures/reviewed-m11/supabase/migrations/20261025100000..110000`) in order; no release ships K2 without them (D-M11-SQL-LAND-1).
-- Until L1 lands on the managed rail, a 21-day starter graduation cadence passes admission but fails at provisional-subscription creation: the installed `subscription_create_provisional_for_checkout` and `subscription_apply_starter_graduation` still accept only 14 and 28. Checkout returns the generic failure (HTTP 503).
-- Until L1 lands on the managed rail, the finalize acquisition-admission backstop is inert: `commerce_finalize_order_for_checkout` does not invoke `private.commerce_assert_acquisition_admission` to raise `acquisition_terms_changed` (SQLSTATE 55000), so the package mapping and the safe-compensation re-quote it triggers never fire from the database. The TypeScript quote guard still re-quotes a changed acquisition expectation before finalize.
-- Until L1 lands on the managed rail, `commerce_configurator_persist_intent` lacks the donor preference write scope: preference/consent writes are not restricted to the authenticated owner, and the legacy country fallback stays as installed.
-
-- Move the unchanged checkout compensation helper and cleanup port into `@openlup/platform/commerce/server`. The reference facade re-exports the identical function; release/cancellation ordering, idempotency keys, reasons and warnings are unchanged.
-
-- Move checkout handlers, the shared paid-order saga, runtime and command execution into the experimental Node-only commerce entry. Host projections, schemas, response routing, starter policy and existing payment execution are injected; reference paths delegate to one package implementation.
-Migration: Acquisition expectations independently reject changed terms in the TypeScript quote guard before finalize; a locked finalize refusal re-quotes only after safe draft compensation once the managed forwards land (L1) (N1). Shipping or acquisition terms now require promotion acceptance even without a current promotion discount (F2).
-Migration: Failed promotion-price-change re-quotes now map `CommerceQuoteError` code `UNKNOWN_SKU` to `BAD_REQUEST` (HTTP 400), and `PRICE_NOT_CONFIGURED`, `UNSUPPORTED_TAX_PROFILE` or `PRICING_INVARIANT_VIOLATION` to `CONFLICT` (HTTP 409), forwarding `error.message` and `error.details` instead of the base's `UPSTREAM_UNAVAILABLE` (HTTP 503), "Checkout failed" and `{ feature: "checkout", stage: "quote" }`. Newly supported acquisition-terms-change re-quotes use the same typed mapping (donor N1).
-Migration: Failed promotion-price-change re-quotes with `CommerceQuoteCatalogReadError` retain `UPSTREAM_UNAVAILABLE` (HTTP 503), but now return "Commerce catalog is unavailable" and `{ reason: "catalog_unavailable", refusalCode: error.code }` instead of the base's "Checkout failed" and `{ feature: "checkout", stage: "quote" }`. Newly supported acquisition-terms-change re-quotes use the same catalog mapping (donor N1).
-Migration: Initial quotes, including normal quoting after saved-continuation fallback, and promotion-price-change re-quotes now map `AcquisitionTermsError` reasons `acquisition_terms_capability_required` and `acquisition_terms_v2_required` to `CONFLICT` (HTTP 409), "Acquisition terms unavailable" and `{ reason: error.reason, refreshRequired: true }`. The base returned `UPSTREAM_UNAVAILABLE` (HTTP 503), "Checkout failed" and `{ feature: "checkout", stage: "orchestrate_order" }` with an optional sanitized preview `diagnosticReason` for initial quotes, or `{ feature: "checkout", stage: "quote" }` for promotion re-quotes. Newly supported acquisition-terms-change re-quotes use the same acquisition mapping (donor N1).
-Migration: On those initial/continuation and promotion re-quote paths, `AcquisitionTermsError` reasons `acquisition_terms_policy_unconfigured`, `acquisition_terms_invalid`, `acquisition_terms_ambiguous` and `acquisition_terms_not_effective` retain `UPSTREAM_UNAVAILABLE` (HTTP 503), but now return "Acquisition terms unavailable" and `{ reason: error.reason, refreshRequired: false }` instead of the base's "Checkout failed" and initial-quote orchestration/preview or promotion re-quote stage details described above. Newly supported acquisition-terms-change re-quotes use the same acquisition mapping (donor N1).
-Migration: An offer-version or minimum-units ask requires a server offer-policy binding. Without a resolver, reference admission retains its host minimum and original validation refusal before persistence. A composed resolver binds or refuses before any quote, order-draft or runtime write; identity persistence retains its existing earlier ordering. Accepted evidence is bounded and the bound version follows authoritative, steady and replacement quotes (N2).
-Migration: An owned saved acquisition quote may continue before re-quoting only when subject context, basket, total, terms, contact, invoice, delivery and starter state match exactly; edits and failed/incomplete lookups take normal quoting (N3).
-Migration: Scoped inventory admission contention returns retryable unavailability without provider dispatch or compensation capability; retry identities are unchanged (N4). Raw database error classification remains an adapter responsibility.
-Migration: Starter admission accepts injected terms and a supplied graduation constraint, includes the 21-day graduation cadence, compares acquisition revision and rate, and freezes the selected second-delivery discount with steady quote policy/version (N5). Reference starter defaults remain host inputs. End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: The best-effort account-link helper accepts an optional trigger for its existing timeout log; without a trigger its log and timeout behavior are unchanged (N8).
-Migration: Saved-method alias and recurring-mode metadata are host-defined string generics throughout the checkout resolver, handler, orchestration, command and runtime APIs. Reference bindings retain their existing provider unions, wire values and execution behavior.
-Migration: The offer-evidence JSON-length limit is internal; consumers use the exported evidence schema.
-Migration: The reference browser quote context now admits optional shipping and resolved acquisition terms through their existing validators, preserving strictness and existing fields (donor D3; K1-scope port carried by K2). `pricing/browser` re-exports the identical schema objects without new validation logic.
-Migration: `outbox.commerceOrderDraftCreatedEventSchema` now accepts the 21-day starter cadence at `payload.quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`, `payload.orderDraftSnapshot.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `outbox.commerceOrderDraftCreatedOutboxRecordSchema` now accepts the 21-day starter cadence at `payload.quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`, `payload.orderDraftSnapshot.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `outbox.commerceOrderDraftCreatedPayloadSchema` now accepts the 21-day starter cadence at `quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`, `orderDraftSnapshot.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `checkout.checkoutRequestSchema` now accepts the 21-day starter cadence at `intent.starterOffer.steady.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `checkout.checkoutResponseSchema` now accepts the 21-day starter cadence at `authoritativeQuote.quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.commerceQuoteSchema` now accepts the 21-day starter cadence at `context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.createOrderDraftRequestSchema` now accepts the 21-day starter cadence at `quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.createOrderDraftResponseSchema` now accepts the 21-day starter cadence at `orderDraft.quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.createQuoteBatchResponseSchema` now accepts the 21-day starter cadence at `quotes.0.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.createQuoteResponseSchema` now accepts the 21-day starter cadence at `quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.orderDraftSummarySchema` now accepts the 21-day starter cadence at `quoteSnapshot.quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.publicCreateQuoteBatchResponseSchema` now accepts the 21-day starter cadence at `quotes.0.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.publicCreateQuoteResponseSchema` now accepts the 21-day starter cadence at `quote.context.starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.quoteContextSchema` now accepts the 21-day starter cadence at `starterPack.graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `contracts.starterPackPlanSchema` now accepts the 21-day starter cadence at `graduation.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `intent.configuratorIntentSchema` now accepts the 21-day starter cadence at `starterOffer.steady.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: `persistence.configuratorIntentPersistenceRequestSchema` now accepts the 21-day starter cadence at `starterOffer.steady.cadenceDays`; invalid-cadence issue alternatives change from `[14, 28]` to `[14, 21, 28]` in that order (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-Migration: The reference subscription starter-marker reader now also accepts the 21-day graduation cadence, matching the checkout starter plan; 30 days remains refused (donor N5). End-to-end managed checkout with this cadence requires the managed forwards to land (L1).
-
-- Move generic draft/finalize/intent/resume stores, cancellation and sweep adapters, bounded recovery classifiers and token helpers into `commerce/server`. Reference factories inject existing schemas, ordered arguments, response projections and phone normalization; verified subject stamping remains last. Recovery projection/routes stay reference-owned; the C2 release handoff is to be released.
-Migration: Runtime-finalize `acquisition_terms_changed` now retains its scoped conflict reason; database-triggered safe pre-dispatch draft compensation and repricing become reachable once the managed forwards land (L1) (N1).
-Migration: Draft catalog-head-moved, missing-anchor and offer-membership refusals now map to catalog-admission conflicts without superseding a draft (N1).
-Migration: Expired subscription recovery permits an absent host subject only with the exact persisted neutral-command marker and all other eligibility fences; public runtime schemas gain no marker bypass (N6).
-Migration: Recovery commercial fingerprints now include shipping terms version, currency, flat charge and threshold; same-money policy drift refuses recreation (N6).
-Migration: The token-state classifier permits continuation only for active/order-not-recoverable, separates expired-policy handling and refuses revoked/used/missing/unknown states. Retained routes are not rewired by this addition (N7).
-Migration: `StarterDeclaration` stays internal to the checkout engine; derive a declaration type from the `createStarterOfferGuard` binding signature instead of importing a standalone type from `commerce/server`.
-
-- Add the unchanged physical-table offer-availability projection at `commerce/server` over a structural client and explicit provider predicate, and the pure status/reason ladder at browser-safe `commerce`. Reference adapters retain SDK/provider policy and delegate to the one package implementation; M06 retains normalized stock reads and reservation TTL ownership. No preview ATP switch or second allocator.
-Migration: The reference reservation binding now maps protected inventory `55P03` failures to scoped `inventory_admission_busy`/`inventory_lock_unavailable` details, refuses schema fallback under contention and preserves the original retry keys (N4). Checkout exposes the existing retryable refusal before dispatch; no compensation capability is fabricated.
-- Give structural draft, resume, intent and compensation factories neutral RPC/query names. Reference bindings retain their incumbent exported names and behavior.
-
-- Add experimental neutral OMS schema cores, browser-safe DTOs and ports, generic handler factories, read builders and managed adapters through the existing commerce entries. Reference wrappers bind identity, settlement, fiscal fields, governance and provider projections. No versions, SQL, migrations or pack caps change.
-Migration: Host integrations supply `respond`, `authorizeAdmin` and optional read-gate/schema bindings. Mutation request parsing and response envelopes use the donor shared helpers; invalid results remain 502, nominal conflicts 409 and upstream throws 503 with their existing messages.
-Migration: Managed clients are structural and RPC-only; query hydration and idempotent note persistence require a separately injected query capability. Manual refund marking calls only the operator-mark RPC and creates no refund.
-Migration: Neutral read contracts omit private identity and first-cycle presentation, use open provider/accounting status strings, a neutral fiscal field and neutral provider counter. Hosts extend the schema and pass projections through final validation to preserve their existing response fields and acceptance.
-Migration: The reference replacement facade now delegates to the existing fulfillment handler instead of its local handler engine. For managed results, request parsing, success bodies (including defaulted released hold IDs), replay receipts, metadata, idempotency keys, RPC arguments, receiver identity, named 409 refusals and ordinary 400/401/403/405/502/503 responses are unchanged. The fulfillment handler additionally recognizes the native-unsupported sentinel and returns its specific 503; the old local handler would classify that sentinel as an invalid 502 response. The managed adapter does not emit this sentinel. Neither path creates a refund or confirms delivery alignment.
-Migration: Default neutral settlement validation checks a three-letter currency and labels empty totals with `XXX`; hosts inject their actual acceptance/default policy. Delivery summaries and labels use neutral defaults until the host supplies its projections.
-Migration: Browser-safe `./commerce` exports schemas and pure helpers; handlers, managed RPC/query adapters and detail composition now import from the Node-only `./commerce/server` entry. `./commerce/contracts` remains type-only.
-Migration: Unprojected OMS timeline labels now use canonical step keys (for example `delivered`) instead of the reference locale labels. Unknown tokens retain `Delivery status updated`; reference presentation remains behind the existing `timelineLabel` projection. Managed query clients must implement the required `is(column, value)` filter for hydration; class query receivers are preserved by the adapter factory.
-Migration: Omitted fulfillment debug now defaults to `No fulfillment data.` in neutral detail schemas. The reference schema binding retains its previous localized summary and serialized field order.
-Migration: Commerce no longer re-exports the core locale label helper `timelineLabelForStep` or the label-bearing `FULFILLMENT_STATUS_MAP`. Presentation consumers import these from their core owner or host binding; commerce retains pure canonical step and recovery helpers.
-Migration: OMS binds K1 order-money and paid-event exports directly. The concrete OMS payment type is `OmsOrderPaymentStatus`, using K1's unchanged generic `OmsPaymentStatus<PaymentIntentStatus>`. Fulfillment recovery DTOs are commerce-owned alongside their pure recovery helpers.
-Migration: Regenerated `commerce.api.md`, `commerce-contracts.api.md`, `commerce-server.api.md`, `communications.api.md`, `fulfillment.api.md` and `identity.api.md` reflect this final declaration graph. Beyond the commerce additions described above, existing declarations change order only: newsletter event `ignored`, fulfillment status members and identity lifecycle-stage members move within their existing declarations. Before and after member sets and types are identical; consumers need no code or SQL migration for this ordering.
-- @openlup/platform size growth: Neutral OMS read model, handlers, managed adapters and contracts moved into `@openlup/platform/commerce` and the new Node-only `./commerce/server` entry, together with the rest of the M11 commerce stack; K1+K3a measured 1,562,728 packed bytes; adding K3b, K4, K2 (K2a x1.4) and F3 projects 1,749,300 packed bytes; caps raised once with 10% headroom to 1,925,000 packed bytes, 1,648,000 code-gzip bytes, 8,970,000 unpacked bytes, 2,520 code files and 2,580 total files (K3a PR #370, cap-raise commit 5e42e9ec).
-
-- Add experimental returns, native order review/media and separate hosted-feedback contracts at `@openlup/platform/commerce`, with handlers and adapters at `@openlup/platform/commerce/server`. Reference paths remain thin facades; no route, SQL, activation or release is added.
-- Migration: Import returns and native order-review/media handlers and adapters from `@openlup/platform/commerce/server`; schemas and port declarations remain at `@openlup/platform/commerce`. Standalone returns handlers require an injected `BffResponder`; reference handler signatures and observed response context are preserved by their facades. Raw upload HTTP types now use the equivalent package HTTP shapes.
-- Migration: Hosted-feedback schemas and RPC-name constants are available from `@openlup/platform/commerce`; Supabase submit/token-check factories are at `@openlup/platform/commerce/server`. Adopters must supply `submit_order_feedback` and `check_order_feedback_token`; native `db/platform` has neither RPC. Hosted feedback remains distinct from native order reviews.
-- Returns scope (F9): only request, approve and reject exist. `restockDisposition`, `refundMode` and `refundAmountCents` record intent; receive, restock and refund execution were never implemented. Request owner/key/fingerprint enforcement stays in the database; the contributed TypeScript RPC arguments are unchanged.
-- Native handler donor-ahead command-runner contribution is observably identical to the prior inline handlers: the 96 pre-move result pins pass, including admin error mapping and exact `replayed` presence. No behavior migration arises from this command-runner contribution.
-- HOST-OWNED class (b) retention: review delay is SQL-only, 14 days native and 21 days in the contributed managed profile. No TypeScript delay seam or SQL change is included.
-- Media retains its existing private storage/upload seams. M02 blob storage lacks private read, inspection, temporary write and promotion operations, so a behavior-changing bridge is not included.
-- Migration: The package default returns reason set is neutral. Use `createCommerceReturnsSchemas(reasonCodes)` and the customer handler's `requestSchema` dependency for host policy; the reference keeps the legacy set with BASE-identical parsed output, refusal details and responses. Return request/approve/reject RPC behavior is unchanged.
-- Migration: Reference browser review and hosted-feedback facades restore jitless Zod initialization before package schema construction. This restores BASE/donor CSP behavior without adding global configuration to the package modules.
-- Migration: `runOrderReviewCommand` is internal to the package. Import the customer/admin handler factories from the commerce/server entry; the reference customer-handler facade keeps its BASE factory export.
-- Migration: Handlers, adapters and raw upload use the existing `@openlup/platform/commerce/server` entry. The `./commerce` runtime graph is browser-safe; `./commerce/contracts` stays type-only. Reference import paths and observed behavior are unchanged.
-
-- Add experimental Node-only commerce domain-effect consumers at `@openlup/platform/commerce/server`; browser-safe event contracts, projections and ports stay at `@openlup/platform/commerce`. No new executor, emitter or dispatcher.
-- Record omitted adopter-private W8/W9 assertions and their owners in the [reference commerce guide](../../src/domains/commerce/README.md#w8w9-conformance-dropped-adopter-private-assertions).
-- Migration: Import handler factories, registry composition and `CommerceEmailRuntime` from `@openlup/platform/commerce/server`. The browser entry never imports the server entry or M08 runtime.
-- Migration: Reference email handlers and the dispatch registry bind a single neutral implementation. Package ports use `contextName` and `messageId`; reference adapters retain their existing extension/provider fields and public send behavior.
-- Migration: `uniqueRegistry` is injected from the existing outbox rail, with no new package dependency. `CommerceEmailRuntime` requires explicit communications parser, transactional scaffold, outcome mapping, locale, money, line-label, paid-presentation, tracking and notification-policy bindings. Reference locale, formatting, provider outcomes and legacy tracking URLs remain unchanged.
-- Migration: Refund notices display amounts only with `refundEvidenceVersion: "provider-refund.v2"`; historical order totals and unversioned refund amounts no longer appear as refund evidence (donor-ahead).
-- Migration: The frozen refund consumer subset ignores legacy `totalCents` and admits optional string `refundEvidenceVersion`; supplied refund amounts and currencies retain their existing validation.
-- Migration: Paid-receipt presentation forwards its proved discount percentage, including non-default percentages (donor-ahead); commercial eligibility stays with the host.
-- Migration: Core handler descriptors and expected-descriptor validation are available before claiming. Claim order, flags, independent paid-email/fulfillment duties, same-event timeout composition and risk gating retain donor behavior.
-- Migration: Channel-owned buyer communication settles as processed with `skipped: "channel_owns_buyer_comms"`, using a live policy read per event. Cancellation email remains unregistered; its fact can be consumed through adopter `extraHandlers`.
-- Migration: Producer event-type literals and payload schema behavior remain unchanged; the draft-event factory accepts exact host snapshot schemas. The neutral source projection preserves external-reference bytes and case, with no inventory SQL or exposure default.
-- Migration: Reference email payload parsing binds the existing fulfillment `parseOutboxPayload` export; its schema issues and bounded discard reason are unchanged. K1 owns all producer schemas through `createCommerceOutboxEventSchemas`; all nine golden parse/refusal cases pass unchanged.
-- Migration: Paid-fulfillment registration re-exports the existing fulfillment descriptor, preserving its identity, event literal and timeout instead of maintaining a second descriptor.
-
-- Add an experimental structural commerce contribution at the existing composition entry, with explicit installed commerce exports, namespaced ports and existing handler, route and schedule descriptors. Duplicate registrations refuse before maps can overwrite an executor.
-- Add an inert, default-off reference commerce binding over existing package callables and the existing native checkout-recovery adapter. Only ready schema observations admit work; unknown and unsatisfied candidates leave the serving selection intact. Native recovery records reminder intents, authorizes their delivery and compacts terminal outbox rows; managed-only expiry and recreation remain separate.
-- K5 adds no refactor: the event-contract gap and server entry scaffold are already resolved in the preceding imports. Existing commerce witnesses and engines remain unchanged; no SQL, timer, route activation or second executor is introduced.
-Migration: `@openlup/platform/composition` additively exports `createCommerceContribution`. Supply the selected callables, complete required schema and existing descriptors; the factory declares them without installation or execution. Existing imports and default compositions need no change.
-
-- Managed commerce migrations preserve the exact reviewed fixture bytes and ordered prerequisite chain.
-Migration: Guest configurator destinations do not rewrite saved delivery or payment preferences; preference writes require a server-proved matching account.
-Migration: Legacy omitted-country fallback uses `platform_region_code()` for address identity and insertion; configure the adopter's settlement region. Neutral commands require explicit country.
-Migration: Return creation and replay require the server-supplied principal's owned order and identical normalized command; foreign or changed commands refuse atomically.
-Migration: Checkout payment-link receipts use the service-only operator entry point and the `checkout_payment_link_mint` audit action.
-Migration: Subscription finalize validates retained acquisition terms under the shared policy lock; policy writers require its exclusive counterpart. Completed finalize replay preserves its response after policy changes; one-time checkout is exempt.
-Migration: The acquisition terms reader refuses absent effective terms; the no-policy finalize compatibility branch remains available.
-Migration: New-purchase stock reads use ATP with renewal exemption fixed false, bounded SKU arrays and conservative stale reporting. The service-only reader uses owner privileges with `SECURITY DEFINER` and `search_path = pg_catalog, pg_temp`.
-Migration: Starter graduation admits 14, 21 or 28 days, while provisional creation uses the retained starter interval and subscription timezone default. Rolling back below the forward with a 21-day marker is unsupported; roll forward.

package/README.md

@@ -10,8 +10,8 @@ Development preview. This package is part of the publishable set with core and o
 
 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.29.0` set, read the [adjacent-release migration and known
-limitations](CHANGELOG.md#0290) before selecting optional services. Experimental
+For the prepared `0.30.0` set, read the [adjacent-release migration and known
+limitations](CHANGELOG.md#0300) before selecting optional services. Experimental
 M13 marketing uses browser-safe `./marketing`, type-only browser-safe
 `./marketing/contracts`, and Node-only `./marketing/server` and
 `./marketing/server/postgres`. Marketing contributions and bindings remain
@@ -54,7 +54,7 @@ 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.28.0` tarball. Preparation and offline
+Size comparison uses the published `0.29.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).
@@ -68,12 +68,52 @@ 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.
 
+The experimental migration source may supply `assertSession` to observe host
+facts once under the existing advisory lock, after exact ledger-prefix admission
+and before status, dry-run or pending SQL. Sources without it retain current
+execution. The [migration owner](../../docs/platform/DATA_AND_MIGRATIONS.md#module-catalogues-and-installed-histories)
+and [runner witness](test/migrations/postgresRunner.test.ts) define that boundary;
+this callback does not provision or qualify a hosted installation.
+
 ## Package surface
 
+The experimental Node-only `./lifecycle` entry plans and applies explicit
+application-file snapshots. It preserves unmanaged files and local edits in
+upstream-unchanged files, refuses divergent changed files before writes, and
+resumes exact completed replacements after interruption. The caller holds an
+exclusive maintenance window and supplies schema-range evidence; this entry
+runs no database migration, npm install or deployment. Read the
+[file-ownership boundary](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#application-file-upgrades)
+and [disposable app recipe](../../docs/platform/PLATFORM_PACKAGE_REFERENCE.md#application-file-upgrade).
+
+The same entry exports `inspectLegacyPostgresInstallRoles`, a read-only query
+through a caller-owned PostgreSQL handle. Its
+`legacy-fresh-bootstrap-role-prerequisites` report observes finite immutable
+legacy bootstrap role conditions; `rolePrerequisitesMet` does not establish
+install readiness, schema/ACL correctness or provider support. See the
+[legacy role boundary](../../docs/platform/DATA_AND_MIGRATIONS.md#legacy-fresh-bootstrap-role-observation).
+
+The experimental Node-only `./portability` entry copies a bounded, explicitly
+complete immutable/quiesced object inventory and captures/restores selected
+compatible PostgreSQL rows through injected transaction handles. Private
+filesystem objects publish bytes and metadata together, bind an explicit access
+label to the filesystem owner's private policy and resume by verified readback.
+Row replay preserves exact JSON/numeric/time values, refuses conflicts and every
+enabled user INSERT trigger, and copies no schema, migration ledger or grants.
+The host qualifies the canonical catalogue, credentials and source completeness.
+These helpers activate no executor and do not supply managed identity mapping,
+live changed-row catch-up or hosted old-worker fencing. Read the
+[transfer boundary](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#existing-store-transfer-and-recovery)
+and the retained [M14 obligations](../../docs/platform/plans/oss-m14-operations-portability.md).
+The provider-owned HTTP counterexample exercises an existing adapter's cached
+bearer; its local fixture establishes no hosted revocation guarantee.
+
 `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.
 
 | Export | Contents |
 | --- | --- |
+| `./lifecycle` | Experimental Node file-snapshot planning/apply and read-only legacy PostgreSQL role prerequisites; no install-readiness claim, optional SDK or activation |
+| `./portability` | Experimental server object copy/resume, private filesystem transfer store and compatible PostgreSQL row capture/restore; injected handles, explicit refusal and no activation |
 | `./http` | Generic capped raw-body reader, hex HMAC and constant-time token comparison; Node request adaptation, deadlines, security headers and static documents, and `createNodeHttpRuntime` with its fixed request order |
 | `./bff` | `createBffDispatcher`, `lazyBffRoute`, the hosted router URL rewrite, the response envelope (`createBffResponder`), the observed request context and the health route |
 | `./scheduler` | Transport-neutral scheduled jobs (`ScheduledJob`, the job registry, the lease-aware runner and the authenticated HTTP cron entry), path-declared jobs from configuration, the node-cron scheduler with per-job advisory locks, hosted cron verification, the cron entrypoint guard (it compares the presented bearer token with `CRON_SECRET` in constant time) and direct job bindings |
@@ -723,6 +763,25 @@ both exported helpers and their signatures: `calculateIncludedVat` delegates to
 
 A job is `{ id, schedule, lease?, run(context) }` with a UTC cron expression. Domains and packages contribute jobs to `createScheduledJobRegistry`, which refuses duplicate ids and ships empty. The Node host runs registry jobs on its own timers and calls `run` directly, with no HTTP request and no secret. `createScheduledJobHttpEntry` mounts the same job behind the cron guard for a hosted cron. A job that declares `lease` runs only after the injected job-lease port grants it; a lease held elsewhere skips the run, and a finish the port refuses fails the run. `scheduledJobsFromContribution` turns a contribution's cadence schedules into jobs and refuses a cadence that no cron expression matches exactly; a contribution run that reports a failed outcome fails the job.
 
+`NodeSchedulerAdapter.stopAll()` returns `Promise<void>`. It fences and stops the
+current registrations synchronously, then waits for callbacks already admitted,
+including pending lock acquisition and unlock. Await it before disposing their
+resources; custom scheduler implementations must return that drain promise.
+Later registrations remain supported. The Node host caches its `stop()` promise,
+closes its listener and retains the dedicated PostgreSQL lock session until the
+drain settles, including failure cleanup.
+
+The PostgreSQL lock adapter also reserves each numeric advisory key locally
+before acquisition. This prevents reentry on the same session, including pending
+acquisitions and colliding job IDs. Failed acquisition releases the reservation;
+failed unlock retains it until session disposal. The
+[disposable PostgreSQL witness](../../tests/postgres/nodeHostRuntimeDrain.test.ts)
+checks same-session exclusion and replacement-host admission after drain.
+This graceful-stop contract does not fence an old host at external provider I/O
+or settle an effect accepted before an acknowledgement; the
+[transfer boundary](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#existing-store-transfer-and-recovery)
+retains those separate duties.
+
 ## Bundle readiness
 
 `PLATFORM_BUNDLE` selects `vercel-supabase` (the default when absent), `node-supabase` or `node-postgres`. A bundle's readiness refuses, before any traffic or timer: an unknown `PLATFORM_BUNDLE` (resolution itself still falls back to the default); a self-host bundle without `APP_BASE_URL`; and, reported together under `OPENLUP_E_ENV_MISSING`, every selected capability without its settings: the scheduler without `CRON_SECRET`, Node scheduling without `DATABASE_URL` for its cluster lock (never a silent single-instance lock), and the selected blob capability without its settings (see Blob storage). An unknown `PLATFORM_BLOB` is refused too. The Node host checks readiness at boot.
@@ -1283,3 +1342,21 @@ their owner meaning. Contribution descriptors install no routes, handlers,
 schedules or workers. See the
 [reference recipe](../../docs/platform/RUNTIME_AND_SELF_HOSTING.md#opt-in-disposable-subscription-reference)
 for the host's schema and transport obligations.
+
+## Operations and diagnostics
+
+The experimental `./operations` entry contains browser-safe operational schemas,
+alert projections and `createOperationsClients`, which binds an existing BFF
+requester. `./operations/contracts` contains DTOs and narrow ports only.
+`./operations/server` contains settings read/update, pipeline read, alert overview,
+control-plane handlers and the existing watchdog delivery mechanism. Authorization,
+SQL execution, evidence evaluation and alert transport are supplied by the host;
+importing these entries registers no route, schedule or provider.
+
+`runControlPlaneWatchdogTick` evaluates persisted neutral job failures and records
+an idempotent heartbeat unless `checkOnly` is true. The richer watchdog accepts a
+typed evaluator; the public reference binds its maintained domain evaluator.
+Settings preserve scalar values, and pipeline reads preserve the existing tester
+and email projection. Identity membership and tracking effects keep their owners.
+See the [operations architecture](../../docs/platform/ARCHITECTURE_AND_EXTENSIONS.md#operations-and-diagnostics)
+for refusal behavior, SQL prerequisites and the bounded preview scope.

package/dist/composition/nodeHost.d.ts

@@ -88,7 +88,7 @@ export interface ServeNodeResult {
     bundleId: string;
     httpRuntime: HttpRuntimePort;
     registeredJobs: string[];
-    /** Stop timers and the local listener after a host signal; safe to call repeatedly. */
+    /** Fence timers, drain admitted jobs, then close their lock session; also close the local listener. Safe to call repeatedly. */
     stop(): Promise<void>;
 }
 export interface NodeHost {

package/dist/composition/nodeHost.js

@@ -133,12 +133,13 @@ export function createNodeHost(deps) {
     return { assertBundleReady, serveNode };
 }
 async function stopNodeHost(scheduler, advisoryLock, httpRuntime) {
-    const timers = Promise.resolve().then(() => scheduler?.stopAll());
+    const timers = scheduler?.stopAll() ?? Promise.resolve();
     const server = httpRuntime.server;
     const listener = server
         ? new Promise((resolveClose, reject) => server.close((error) => error ? reject(error) : resolveClose()))
         : Promise.resolve();
-    const results = await Promise.allSettled([timers, advisoryLock?.close(), listener]);
+    const lock = timers.then(() => advisoryLock?.close(), () => advisoryLock?.close());
+    const results = await Promise.allSettled([timers, lock, listener]);
     const failures = results.flatMap((result) => result.status === "rejected" ? [result.reason] : []);
     if (failures.length > 0)
         throw new AggregateError(failures, "node_host_shutdown_failed");

package/dist/lifecycle/appUpgrade.d.ts

@@ -0,0 +1,52 @@
+/** Exact UTF-8 scaffold files; every unlisted path remains application-owned. */
+export interface AppVersionSnapshot {
+    version: string;
+    schema: {
+        min: number;
+        max: number;
+    };
+    files: Readonly<Record<string, string>>;
+}
+export interface AppUpgradeInput {
+    /** Absolute canonical path (as returned by realpath) of an existing app directory. */
+    root: string;
+    from: AppVersionSnapshot;
+    to: AppVersionSnapshot;
+    /** Observed by the caller; planning and applying execute no database work. */
+    schemaVersion: number;
+}
+export type AppUpgradeAction = "create" | "replace" | "remove" | "unchanged" | "preserved" | "already-applied";
+export interface AppUpgradeConflict {
+    path: string;
+    reason: string;
+}
+export interface AppUpgradePlan {
+    fromVersion: string;
+    toVersion: string;
+    schemaVersion: number;
+    files: {
+        path: string;
+        action: AppUpgradeAction;
+    }[];
+    conflicts: AppUpgradeConflict[];
+}
+export declare class AppUpgradeConflictError extends Error {
+    readonly conflicts: readonly AppUpgradeConflict[];
+    constructor(conflicts: readonly AppUpgradeConflict[]);
+}
+/** Read-only comparison of explicit predecessor and candidate snapshots. */
+export declare function planAppUpgrade(input: AppUpgradeInput): Promise<AppUpgradePlan>;
+/**
+ * The caller must hold an exclusive maintenance window over the application tree.
+ * This is not a lock against concurrent editors or hostile filesystem mutation.
+ * All conflicts are checked before any writes. A later I/O failure can leave a
+ * partial upgrade: rerun the same snapshots to recognize exact completed bytes.
+ * Each replacement is atomic on a local filesystem; the complete upgrade is not.
+ * An abrupt process termination can leave a uniquely named temporary file; it is
+ * never treated as a managed app file or resumed operation.
+ * No SQL, dependency install, version marker, deployment or user hook is executed.
+ */
+export declare function applyAppUpgrade(input: AppUpgradeInput): Promise<{
+    plan: AppUpgradePlan;
+    applied: string[];
+}>;