v2026.8.0

fortemi-react v2026.8.0 release notes.

fortemi-react v2026.8.0

fortemi-react v2026.8.0 is the August 2026 release line for the Core source identity, typed metadata, and terminal purge work.

Highlights

  • Source-addressed import (#404): `SourceUpsertRepository` and

`upsertRecordStoreSources` atomically import notes by tenant, archive, namespace, and external id. Exact replays return `unchanged` without duplicating notes, revisions, import runs, jobs, or RecordStore journal entries. Changed content is explicit `version`, `replace`, or `conflict`.

  • Scoped metadata search (#405): `SearchOptions.metadataPredicates` filters

indexed provider, model, role, event kind, sensitivity, and import-run fields before text, semantic, hybrid, or recent ranking. Search hits include safe evidence locators with source hashes and metadata paths, not raw external source keys.

  • Terminal purge receipts (#406): `LifecyclePurgeRepository` and

`purgeRecordStoreGraph` provide preview counts, atomic relational deletion, search/graph cleanup, and idempotent content-free deletion receipts.

  • Profile honesty: `core-v1` and `record-v1` Knowledge Shard exports report

omitted source identity mappings as typed `source-identity-outside-profile` loss instead of implying that operational source mappings are preserved by those profiles.

Published Packages

Compatibility

The new PGlite migration is additive. Existing note, shard, and RecordStore data remain readable. Source-addressed import creates the new source identity and import-run records only when callers opt into the new APIs.

Search predicate paths are intentionally allowlisted. Unknown or unindexed paths fail clearly instead of running unbounded scans or widening authorization scope.

Claim Scope

This release does not change Fortemi #1081's suite-level `NO-GO` audit. Source identity state, AIWG static indexes, Knowledge Shard transfer, and live Fortemi persistence remain separate planes. Knowledge Shard claims must still name the specific `core-v1`, `record-v1`, or `full-v1` profile being exercised.

Verification

  • 5 focused source-addressed import, metadata locator, and purge receipt tests
  • 1,261 Core tests
  • 283 portable-contract tests
  • Typecheck and Knowledge Shard contract verification