Stateman 0.2.0

Public @godoo-dev/stateman@0.2.0 is available from npm. It adopts client 0.8.0 and introspection 0.2.4, with one shared client and no older nested runtime supplier.

Changes since 0.1.0 include exact relation ownership, company-dependent values, multilingual HTML convergence, bounded read batching, computed-field and multi-company MIS helpers, and Odoo Reference fields. Node 24+ and Odoo 18 remain the baseline. LGPL notices and corresponding TypeScript source ship in the archive; reference Python remains preserved.

The release tag identifies the original candidate source ee5739ca5020af09c03bb0f0b1e1a8016dbcc12b, integrated through PR #19. Original qualification run 41146741948, attempt 1 passed offline, installed package and disposable Odoo18 checks, including owned-resource cleanup, before its publication failed with npm E404.

After trusted-publisher repair, recovery run 41182221755, attempt 1 successfully published those original artifacts without rebuilding or changing version. Its publisher source 3a42fe30befb71a412db61795cbbbc6ce51330e6 is separate from the released source. The original failure and recovery history remain in issue #18.

Production registry readback on 2026-10-31 verified the 172,074-byte archive against the tested candidate:

SHA256 d608e7e1402e46e2ad6dde58d3af99c1b67d680da944eacdb02c8b58aab239f6

A fresh isolated registry-name/version install passed TypeScript checking, maintained public API/CLI plan/apply/drift and recovery checks, offline content/children, computed-field/MIS acceptance, supplier constructors and typed lifecycle/addon adapters. All shipped files matched the qualified package; npm dependency-tree checks confirmed client 0.8.0 and introspection 0.2.4 without older nested suppliers. The disposable consumer was removed.

Registry propagation initially returned metadata with a 404 tarball; bounded observation established availability before acceptance. Original Odoo18 qualification remains applicable to the identical bytes; no new Docker suite was run. Synthetic consumer checks do not establish application business acceptance, live managed-addon lifecycle acceptance or Odoo19 qualification.

Stateman 0.1.0 — first public npm baseline

First public npm baseline for the standalone TypeScript package.
Registry bytes and installed API/CLI consumers have been verified.

• Author resources and bounded portable fixtures, compose reusable seeds, and
  preview explicit addon stages through the API and installed CLI.
• Review deterministic plans, apply with durable recovery receipts, and check
  fresh drift. Preserve explicit adoption, scoped removals and XML-ID aliases.
• Include full parent/child readiness before dependent work, pause managed crons
  before changes, and activate only after successful reconciliation.
• Require Node 24+ and Odoo 18 as the disposable integration baseline; later
  majors require explicit same-candidate qualification after 18.
• Retain LGPL-3.0-only, predecessor attribution and corresponding TypeScript
  source. Python remains a preserved reference implementation.
• Prepare manual npm promotion of the same installed and Odoo18-tested tarball,
  with source/hash/consumer-lock checks and exact-byte publication recovery.

Package: public @godoo-dev/stateman@0.1.0, LGPL-3.0-only with corresponding TypeScript source. Node 24+ required. This redesign requires migration from @marcfargas/odoo-state-manager; it is not a drop-in replacement.

Qualified source: 9ff36580da66e3167b5ea1acdb783296b33e7738.

Native qualification and exact-byte recovery/promotion: https://github.com/godoo-dev/godoo-stateman/actions/runs/40235199652. The first public package was bootstrapped from the qualified tarball using npm owner authentication; subsequent publication uses the configured GitHub trusted publisher. This initial bootstrap has no GitHub provenance attestation.