v2026.9.1

fortemi-react v2026.9.1 release notes.

fortemi-react v2026.9.1

fortemi-react v2026.9.1 publishes the browser consumer side of Fortemi's `source-note-upsert/1.0.0` live persistence contract.

Highlights

  • `@fortemi/core` now consumes the Fortemi authority-owned source-addressed

note upsert contract for both PGlite and RecordStore.

  • Exact batch replay is scoped by `(tenant, memory, source_namespace,

external_id)` plus request digest and `batch_id`, returning `duplicate` or `unchanged` without duplicating notes, revisions, journals, or events.

  • Changed content follows the explicit `version`, `replace`, or `conflict`

policy from the producer contract instead of a consumer-defined mutation model.

  • The consumer pins the shared executable fixture and exact producer receipt in

`packages/core/schemas/source-note-upsert/contract.receipt.json`.

Packages

Publication verification

Each registry workflow packs each package once, publishes that exact tarball, and checks the registry SHA512 integrity against it. The workflow also verifies the downloaded release tarballs and SHA256SUMS manifest against the local artifacts. The public npm workflow retains provenance publication.

Signed-tag publication and the resulting registry, release-asset and provenance receipts are pending. Source-level verification does not establish publication.

Compatibility

This release qualifies one live persistence contract only: `source-note-upsert/1.0.0`.

Source identities remain outside the current Knowledge Shard profiles. When PGlite or RecordStore export a shard that omits that live-only state, they keep returning the typed `source-identity-outside-profile` loss report rather than claiming portable source identity.

The exact current consumer receipt is bound to fortemi-react commit `10099c603e2f465730d2500eb95d112ace07e0ea`, green PR run 51975, and green `origin/main` run 51991. The upstream authority remains Fortemi ADR-106 and `contracts/source-note-upsert/contract.json`.

Claim Scope

This release does not change Fortemi #1081's suite-level `NO-GO` audit. The AIWG static index, Knowledge Shard state transfer, and live Fortemi persistence remain separate planes. Knowledge Shard claims still require a named `core-v1`, `record-v1`, or `full-v1` profile and its executable receipt matrix.

Verification

  • Shared source-upsert conformance fixture on clean PGlite and RecordStore

destinations

  • Fortemi producer receipt pinned in `contract.receipt.json`
  • Green Gitea CI on PR run 51975 and `origin/main` run 51991
  • Publication workflow source: signed commit `f64662bd2c6f2f62f39a92da6f4247cf8454a7bc`,

green Gitea CI run 54367, and seven focused artifact/workflow tests