v2026.7.9

fortemi-react v2026.7.9 release notes.

fortemi-react v2026.7.9

fortemi-react v2026.7.9 publishes the canonical Knowledge Shard work that landed after the `2026.7.8` packages were built. The new package version makes source and registry behavior unambiguous for cross-repository consumers.

This release introduces isolated Fortemi React signing authority. Release tags use `Fortemi React Release Signing` (`26CB074F65E89E5F4DFD7C71F410C8C763C90CC9`), while commits use the separate `Fortemi React Commit Signing` key (`CD2CD155A057B212A525E1C2A7E29DCA3E39B9B8`). Retired release authorities remain published for historical tag verification.

Highlights

  • Current contract authority (#354): `@fortemi/core` pins Fortemi contract

revision 19 and the complete schema 1.2.0 bundle. The validator accepts the authority's signed 33-component `full-v1` fixture and rejects component, topology, count, checksum, signature-shape, embedding-lineage, and mandatory blob-sidecar drift. Historical schema 1.1 archives remain readable without inventing missing embedding lineage.

  • Honest profile scope (#354, #355): authority support and backend support

are reported separately. PGlite advertises `core-v1`; RecordStore advertises `record-v1`; neither claims `full-v1` production or persistence.

  • Canonical AIWG producer (#355): the AIWG v2 converter emits deterministic,

self-validating `core-v1` archives without consumer-side manifest repair. Complete AIWG source records and relationship details remain losslessly available in canonical metadata.

  • Fail-closed rich conversion (#355): the former partial SKOS/provenance

projection is rejected until a complete `full-v1` converter exists. Unscored asserted AIWG relationships use canonical link score `1` while retaining the source relationship in metadata.

Published Packages

Compatibility

Existing legacy, `core-v1`, and `record-v1` APIs remain available. The new `full-v1` validator is a contract-consumption surface, not an advertisement that a React backend can produce or restore the full profile.

The already published `2026.7.8` packages are unchanged and must not be treated as containing the later canonical converter or revision-19 authority.

Verification

  • GitHub and Gitea release tarballs are covered by each release's

`SHA256SUMS` manifest; verify after downloading all four assets with `sha256sum -c SHA256SUMS`.

  • Full Core test suite
  • Blocking portable-contract suite
  • Core typecheck, lint, and build
  • Packed and clean-installed `@fortemi/core` package behavior
  • Gitea PR CI: typecheck, lint, unit-test, portable-contract, examples,

examples-e2e, e2e, and build