@openlup/core 0.0.0 → 0.6.0

package/CHANGELOG.md

@@ -0,0 +1,184 @@
+# Changelog
+
+Notable changes to this public-source workspace package are recorded here.
+“Unreleased” means no npm version carries the change yet; immutable OpenLup
+source previews may already ship some changes, and their release notes say
+which. Declaration snapshots track candidate drift, not a stable API or
+SemVer promise.
+
+## Unreleased — checkout recovery contracts
+
+- Add neutral checkout recovery evidence, method, operation and action contracts
+  to the existing payment surface. They describe guidance only and do not change
+  payment admission, renewal classification or enabled payment methods.
+
+## [Unreleased]
+
+### Changed
+
+- Publishable on the npm `preview` dist-tag as `0.6.0`, for source preview
+  `openlup-source-preview/6`. Directory `npm publish` stays refused.
+
+- **BREAKING for `slugSchema`'s accepted language.** The `./catalog` schema no
+  longer trims its input, so a slug with leading or trailing whitespace is now
+  rejected rather than normalised and accepted, which is what the published
+  `catalogSlugFormat` it tests against always described. A caller that relied on
+  that normalisation must trim before validating.
+- **BREAKING for the retry ladder's semantics.** `nextRetryAttemptAt` now
+  TERMINATES past the end of the ladder instead of capping at its last slot: an
+  attempt beyond the configured backoff length answers `null`, which is the pause
+  signal, rather than repeating the final interval forever. The stored schedule
+  this kernel mirrors has always terminated, so the two rails now agree; the
+  previous capping behaviour meant a caller asking for attempt 4 (or 9) was told
+  a fourth charge was scheduled when none was. Callers that guarded with
+  `attempt <= maxRetryAttempts()` before calling should drop the guard — asking
+  for the next slot IS the decision, and a second copy of the budget check is how
+  the two rails drifted apart in the first place.
+
+### Added
+
+- `recordPaymentFailure` accepts an optional neutral `failureClass` and passes it
+  to the canonical retry-ladder decision. Existing callers remain
+  source-compatible. The shipped terminating-class set is exactly
+  `["hard_do_not_retry"]`: that refusal gets no later rung, while every other
+  class keeps the existing 24h/72h/168h schedule.
+- Class-aware retry termination on `./subscription`.
+  `CycleRetryCadence` gains an optional `terminatingFailureClasses`, the new
+  `ladderTerminatedByClass(failureClass, cadence?)` answers whether the REASON
+  for a refusal ends the ladder, and `nextRetryAttemptAt` / `shouldScheduleRetry`
+  take an optional trailing `failureClass`. `DEFAULT_CYCLE_RETRY_CADENCE` ships
+  only `hard_do_not_retry`. The predicate fails open for an absent or unlisted
+  class, for a listed class the taxonomy does not recognise, and for a listed
+  class that `failureClassDecision` still permits. Only explicit membership plus
+  the taxonomy's existing refusal can end the ladder early.
+- Injectable retry cadence on `./subscription`: `CycleRetryCadence` and the
+  frozen `DEFAULT_CYCLE_RETRY_CADENCE` (24h/72h/168h). `nextRetryAttemptAt`,
+  `shouldScheduleRetry` and `maxRetryAttempts` each take an optional cadence and
+  default to the shipped one, so a deployment can publish its own ladder without
+  forking the kernel and nothing changes for a caller that passes none.
+
+- Pack budgets raised (packed 98 KiB -> 106 KiB, unpacked 448 KiB -> 480 KiB;
+  file count unchanged at 186): the new allocation kernel ships as one source file
+  plus its two build artifacts, and its adopter-facing JSDoc — the floor-clamp
+  rule, the two-line split rationale and the failure-versus-throw split — is most
+  of the added bytes. The docs are the deliverable, so the budget moves rather
+  than the docs. Measured, not estimated: clean base packs 98532/446519/183 and
+  this change packs 106488/475826/186.
+- Experimental bundle target-price allocation on `./pricing`:
+  `allocateBundleTargetPrice`, the pure kernel that turns ONE operator-set price
+  for a composed bundle into exact per-component money. Largest-remainder
+  (Hamilton) split weighted by each component's own reference subtotal, all in
+  BigInt, ties broken by component code so output never depends on input order.
+  Two rules bound it — a component never allocates below its minimum payable per
+  unit (and a component priced under that minimum is held to its own reference
+  price, because no floor may lift a component above what it is worth), and never
+  above its reference unit price. A quantity whose allocated subtotal does not
+  divide evenly emits TWO lines rather than a rounded unit price, so the
+  `unitPrice x quantity === lineSubtotal` identity every quote line refines still
+  holds. The single asserted invariant is that the emitted lines sum to the target
+  exactly. Three refusals stay data rather than exceptions: nothing to weigh
+  against, a target above the sum of the parts, and a target that cannot cover
+  every minimum payable. No clock, no randomness, no I/O.
+- Line-scoped `bundle` component in the pricing breakdown vocabulary, with an
+  optional `bundle_allocated_discount_minor` on the line input: positive on the
+  way in, emitted as one negative component, absent or zero emits nothing. It is
+  line-scoped rather than order-scoped because a bundle prices a subset of the
+  cart, and refunding one line must return exactly what that line was charged.
+- Pack budgets raised (packed 90 KiB -> 94 KiB, unpacked 416 KiB -> 432 KiB,
+  files 180 -> 186): one new kernel module ships as a source file plus its build
+  artifacts and their maps, and its adopter-facing JSDoc is most of the added
+  bytes. The docs are the deliverable, so the budget moves rather than the docs.
+- Experimental payment-method lifecycle vocabulary on `./payment`: the five
+  transitions a rail may report about a method it holds on file
+  (`method_registered`, `method_updated`, `method_revoked`, `method_expired`,
+  `method_suspended`), the neutral event an adapter translates its own event
+  names into, and the three published facts (`schemeLabel`, `lastDigits`,
+  `expiresAt`) a transition may carry — never the instrument number. Plus two
+  pure helpers: `endsStoredMethodUsability`, the single place that answers
+  whether a transition means the method can no longer back a charge (a rotation
+  is not a death), and `expiryInstantFromMonthYear`, which pins the convention
+  that a month-and-year validity runs to the LAST instant of that month in UTC.
+  No rail is named and no clock, network or storage is read.
+- Pack budgets raised (packed 88 KiB -> 90 KiB, unpacked 400 KiB -> 416 KiB): the provider-capability contracts
+  add ~0.9 KiB of shipped declarations and their adopter-facing JSDoc; the
+  docs are the deliverable, so the budget moves rather than the docs.
+- (formatting) the block-reason alias is declared single-line so the
+  generated declaration snapshot carries no trailing whitespace.
+- Experimental payment-provider capability contracts on `./payment`: a
+  descriptor an adapter publishes so renewal and dunning can decide from
+  CAPABILITIES — whether stored consent evidence must be read and whether it
+  is chargeable unattended, which provider flow an unattended charge uses,
+  what payer context the request needs, and what a stored method must satisfy
+  before a charge — plus a registry contract keyed by provider kind. Types
+  only, with no provider named and no runtime consumer yet; branching on
+  provider identity is unchanged.
+- Experimental payment-failure taxonomy on `./payment`: a pure classifier that
+  resolves a refusal into one of seven neutral classes from optional evidence
+  (scheme retry advice, adopter-asserted neutral hints, an opaque decline code
+  read through an adopter-supplied hint table, and the internal reason key),
+  with a documented precedence order, a frozen per-class retry decision record,
+  and a scheme retry ceiling helper pinned at 15 attempts per 30 days. The
+  kernel embeds no acquirer code tables and has no runtime consumer yet; retry
+  scheduling is unchanged.
+- Experimental provider-neutral payment-decline evidence on `./payment`, with
+  a provider code (never free-form prose) and retryability hint that lets
+  adopters classify synchronous PSP refusals without persisting customer data.
+  Extended with optional `declineCode` and `adviceCode`, so a refusal keeps the
+  finer bank reason and the provider's retry recommendation — both codes, never
+  messages — for a later classification policy to read. Extended again with
+  optional `neutralReasonHints`, so an adapter can carry its OWN reading of a
+  refusal — already translated out of its code vocabulary — and a classifier
+  never has to learn which adapter refused.
+- `PAYMENT_FAILURE_CLASSIFICATION_SOURCES` on `./payment`: the classification
+  sources published as a value as well as a type, so a boundary schema can
+  validate `decidedBy` against the kernel's own vocabulary instead of restating
+  it. The type is unchanged and still derives from the same four members.
+- Additive `evaluatePromotionAdjustmentsV2` API in the existing candidate
+  `./promo` subpath. It chooses one best product and shipping adjustment,
+  interprets product percentages as target-effective basis points against a
+  trusted reference subtotal, and requires an adopter-defined product floor.
+  The legacy evaluator and DB-shaped types remain unchanged for compatibility;
+  downstream applications can adopt the package boundary before any separately
+  flagged runtime cutover.
+- Experimental `./fulfillment` normalized-fact contract with explicit schema,
+  strict N/N-1 parsing, adopter-supplied canonical-status validation,
+  discriminated provenance, application-minted evidence references, comparable
+  provider ordinals, deterministic fingerprint/dedupe, and self-contained
+  transition-conflict diagnostics with strict stream/decision validation.
+- The then-current package identity and extracted-root governance evidence;
+  this is historical evidence, not authorization for a separate repository or
+  release channel.
+- Package-local documentation and governance material for the portability
+  boundary.
+- Candidate and experimental maturity metadata for the package surface.
+
+### Changed
+
+- Marked candidate/experimental declarations `@beta` and testing-only
+  declarations `@internal`, without changing package exports or runtime shapes.
+  Removed the private `./testing` neutrality matcher after moving all packaged
+  leak classes into the packed-artifact audit.
+- Reclassified all declaration snapshots as private package-surface drift proof;
+  this changes no exports, runtime behavior, dependencies, or publish refusal.
+- Raised the reviewed packed/unpacked artifact ceilings by 4/16 KiB to admit
+  the additive promo v2 declarations and implementation.
+- Replaced public-surface and freeze language with the private package-surface
+  inventory: 16 current exports have package smoke evidence but no public
+  stability claim.
+
+### Removed
+
+- Removed the unused `./external-effects` API, implementation, snapshot, and
+  self-conformance fixture before any public release. The application
+  one-writer cleanup left no runtime consumer, so external-effect retry
+  semantics stay adopter-owned instead of becoming a fourth core concern.
+
+### Security
+
+- Recorded the private vulnerability-reporting contact for this proof package.
+
+## Release Status
+
+No npm version has been released yet. A `preview` version establishes no
+stable package API or supported upgrade channel. Add a dated section only
+after a version is published.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,39 @@
+# Code of Conduct
+
+## Our Standard
+
+We want participation in this project to be respectful, specific, and
+constructive. Examples of welcome behavior include:
+
+- discussing ideas and evidence rather than attacking people,
+- giving actionable feedback and accepting correction with grace,
+- respecting different backgrounds, identities, experiences, and skill levels,
+- protecting private information and allowing others to set personal
+  boundaries,
+- taking responsibility for mistakes and repairing harm where possible.
+
+Harassment, threats, discriminatory language, sexualized attention, sustained
+disruption, personal attacks, doxxing, and publication of another person's
+private information are not acceptable.
+
+## Scope
+
+This standard applies in repository issues, pull requests, reviews,
+discussions, and project-run community spaces. It also applies when someone is
+representing the project in public.
+
+## Enforcement
+
+Maintainers may edit or remove content, close or lock threads, reject
+contributions, or temporarily or permanently restrict participation when needed
+to protect the community. Enforcement decisions should consider context,
+severity, prior behavior, impact, and the safety of affected people.
+
+## Reporting
+
+The repository-root `CODE_OF_CONDUCT.md` owns conduct reporting and enforcement.
+The repository-root `SECURITY.md` owns vulnerability reporting. This packaged
+copy defines no separate moderator, inbox, or fallback reporting route.
+
+Do not put private, sensitive, or identifying incident details in a public
+issue. Follow the currently authorized repository-root policies.

package/CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing
+
+Commerce Core is public source for framework-independent commerce kernels.
+Its npm versions ride on the source previews (`preview` dist-tag only) and
+activate no separate package product or stable API.
+
+## Set up and verify
+
+In this package directory, use the Node and npm versions from `package.json`:
+
+```sh
+npm ci
+npm run ci
+```
+
+The gate builds every export, runs standalone tests and isolated package smoke,
+verifies declaration snapshots, and checks license, SBOM, audit, pack, and
+publish controls. Neither the root test script nor root CI runs it.
+
+## Scope
+
+Keep deterministic rules and provider-neutral contracts here. UI, HTTP routes,
+database orchestration, schedulers, credentials, provider SDKs, and
+product-specific policy remain outside the package.
+
+Treat exported declarations as internal candidate surfaces. When a declaration
+change is intentional, update tests, record the reason in [CHANGELOG.md](CHANGELOG.md),
+run `npm run api:update`, and review the snapshot diff. Do not infer a stable
+API, SemVer promise, independent release, or external adoption from that proof.
+
+## Security
+
+Never include credentials, customer data, private repository links, or deployment
+evidence. For vulnerabilities follow [SECURITY.md](SECURITY.md).

package/LICENSE

@@ -0,0 +1,204 @@
+Copyright (c) 2026 Bartlomiej Roszkowski
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/MAINTAINERS.md

@@ -0,0 +1,33 @@
+# Maintainers
+
+`@openlup/core` is maintained in the phase-5 platform monorepo. It is not an
+independent product; its versions ride on the source previews.
+
+## Responsibilities
+
+- preserve the `preview` publication settings and the directory-publish
+  refusal;
+- keep package smoke, license, SBOM, audit, pack, import, and gitleaks proofs
+  green;
+- keep provider and product-specific behavior outside this package;
+- review declaration-snapshot drift as an internal candidate contract change,
+  without implying public stability or SemVer;
+- use the smallest change that preserves the existing export graph and package
+  portability proof.
+
+## Local package gate
+
+```sh
+npm ci
+npm run ci
+```
+
+`npm run ci` builds every export, runs tests and coverage, validates declaration
+snapshots and documentation, checks licenses/SBOM/audit/pack/publish settings,
+and exercises a packed first-party consumer. That consumer is package smoke,
+not external-consumer evidence.
+
+## Security
+
+Do not put credentials, customer data, private deployment evidence, or product
+policy into this package. Report vulnerabilities through [SECURITY.md](SECURITY.md).

package/README.md

@@ -1,5 +1,66 @@
-# @openlup/core
+# Commerce Core
 
-This version reserves the package name and contains no code. It is deprecated on publication.
+`@openlup/core` is a framework-independent TypeScript workspace package of
+subscription and bundle commerce kernels, not a separate library product.
 
-Real versions of `@openlup/core` are staged by the OpenLup release workflow from a published source preview (`openlup-source-preview/<n>` → `0.<n>.0`) and approved by the maintainer. See https://github.com/openlup/openlup/blob/main/.github/VERSIONING_AND_EOL.md.
+> [!IMPORTANT]
+> Version `0.<n>.0` is packed from source preview `openlup-source-preview/<n>`,
+> staged with provenance and approved with 2FA, on the `preview` dist-tag only.
+> `npm publish` from this directory is refused. No version implies a stable
+> API or supported consumer path. Build, pack, and isolated-import checks are
+> package smoke evidence only.
+
+## Package Surface Maturity
+
+Every current export is an internal candidate, experimental kernel, or testing
+surface. Its declaration snapshot is a reviewable drift proof, not a public API
+promise.
+
+| Export | Role | Maturity | Package smoke |
+| --- | --- | --- | --- |
+| `./bundle` | kernel | candidate | `smoke/subscriptionBundleStandalone.test.ts` |
+| `./catalog` | kernel | candidate | `smoke/catalogStandalone.test.ts` |
+| `./checkout` | kernel | experimental | `smoke/checkoutStandalone.test.ts` |
+| `./company-identity` | kernel | experimental | `smoke/companyIdentityStandalone.test.ts` |
+| `./fulfillment` | kernel | experimental | `smoke/fulfillmentStandalone.test.ts` |
+| `./inventory` | kernel | candidate | `smoke/inventoryStandalone.test.ts` |
+| `./marketing/research` | kernel | experimental | `smoke/marketingResearchStandalone.test.ts` |
+| `./partners` | kernel | experimental | `smoke/partnersStandalone.test.ts` |
+| `./payment` | kernel | experimental | `smoke/paymentStandalone.test.ts` |
+| `./platform-runtime` | kernel | experimental | `smoke/platformRuntimeStandalone.test.ts` |
+| `./pricing` | kernel | candidate | `smoke/pricingStandalone.test.ts` |
+| `./promo` | kernel | candidate | `smoke/promoStandalone.test.ts` |
+| `./risk` | kernel | candidate | `smoke/riskStandalone.test.ts` |
+| `./shipping` | kernel | candidate | `smoke/shippingStandalone.test.ts` |
+| `./subscription` | kernel | candidate | `smoke/subscriptionBundleStandalone.test.ts` |
+| `./testing` | testing | testing | `smoke/testingStandalone.test.ts` |
+
+`release-gates.json` records four distinct evidence classes:
+
+- `packageSmokeEvidence`: required hermetic build/import/pack/publish-refusal
+  proof for this package;
+- `conformanceEvidence`: required only when a declared port/adapter seam needs
+  a framework-free suite;
+- `dogfoodEvidence`: first-party integration seams, not independent adoption;
+- `externalConsumerEvidence`: not yet evaluated; a first-party packed consumer
+  remains package smoke, not external adoption.
+
+## Local verification
+
+From this package directory:
+
+```sh
+npm ci
+npm run ci
+```
+
+Focused proofs are `npm run api:check`, `npm run release:check`, and
+`npm run test:consumer`. The root test script skips this suite. A `preview`
+install is evaluation, not a supported install.
+
+## Kernel Documentation
+
+- [`docs/SUBSCRIPTION_ENGINE.md`](docs/SUBSCRIPTION_ENGINE.md) — what the
+  `./subscription` kernel owns, its deterministic-clock contract, the
+  late-payment cycle-shift rule and its monotonic clamp, and how a host
+  application consumes it.

package/SECURITY.md

@@ -0,0 +1,29 @@
+# Security Policy
+
+## Release Support
+
+No package version is supported. A `0.<n>.0` version on the `preview`
+dist-tag is development-preview evaluation, not a supported public release. A
+future support policy belongs to phase-5 public platform governance, not to a
+separate package release channel.
+
+## Vulnerability Reporting
+
+Use GitHub Private Vulnerability Reporting for the repository named by this
+package's source metadata. It is the primary route for suspected vulnerabilities.
+If that private route is unavailable, use the fallback named by the canonical
+[repository security policy](https://github.com/openlup/openlup/security/policy).
+Never use a public issue, pull request, or discussion for a vulnerability report.
+Packages do not define separate reporting routes.
+
+## Safe Handling
+
+Never include credentials, access tokens, private keys, personal data, or live
+service payloads in an issue, pull request, test fixture, or reproduction.
+Sanitize logs and use synthetic identifiers. If a secret is exposed, revoke or
+rotate it at the system that issued it before sharing any follow-up evidence.
+
+Security changes should include the smallest non-sensitive regression test that
+demonstrates the repaired boundary. Public disclosure belongs after affected
+users can obtain a fix and must follow the reporting policy established before
+launch.

package/dist/bundle/contracts.d.ts

@@ -0,0 +1,9 @@
+import type { BundleLineRef, CompositionConstraint } from "./ports.js";
+/** @beta */
+export type { BundleLineRef, CompositionConstraint, CompositionRulesPort, } from "./ports.js";
+/** @beta */
+export interface Bundle {
+    coreLines: BundleLineRef[];
+    addonLines: BundleLineRef[];
+    constraint: CompositionConstraint;
+}

package/dist/bundle/contracts.js

@@ -0,0 +1 @@
+export {};

package/dist/bundle/ports.d.ts

@@ -0,0 +1,41 @@
+/** Opaque, adopter-defined sizing anchor with a minimal discriminator. */
+/** @beta */
+export interface CompositionConstraint {
+    /** Adapter-owned constraint family, for example "fixed.catalog". */
+    kind: string;
+    /** Adapter-owned schema version for data. */
+    version: number;
+    /** Adapter-owned payload; core passes it through without inspecting it. */
+    data: Record<string, unknown>;
+}
+/** @beta */
+export interface BundleLineRef {
+    variantId: string;
+    qty: number;
+    isAddon: boolean;
+}
+/** @beta */
+export interface CompositionRulesPort {
+    validateComposition(input: {
+        coreLines: BundleLineRef[];
+        addonLines: BundleLineRef[];
+        constraint: CompositionConstraint;
+    }): Promise<{
+        ok: true;
+    } | {
+        ok: false;
+        code: string;
+        details?: Record<string, unknown>;
+    }>;
+    resizeComposition(input: {
+        coreLines: BundleLineRef[];
+        constraint: CompositionConstraint;
+        lever: {
+            kind: string;
+            value: unknown;
+        };
+    }): Promise<{
+        coreLines: BundleLineRef[];
+        constraint: CompositionConstraint;
+    } | null>;
+}

package/dist/bundle/ports.js

@@ -0,0 +1 @@
+export {};