fortemi-react — September 2026

fortemi-react brings Fortemi's local note storage and search into browser apps. September added checks on data imports and search results, plus fixes to shard restore and export.

TL;DR

React apps can now review an import plan and check proof that the run finished. Search keeps supported field filters in place and ties source links to checked proof. Knowledge Shard restores now feed live PGlite data, so later exports include your edits. Delete controls also gained stricter scope checks. The remote dataset adapter is still alpha. Shard support depends on the chosen profile.

By the numbers

What's public	Value
Published packages	`@fortemi/core`, `@fortemi/graph`, `@fortemi/react`
New React entry point	`@fortemi/react/dataset`
Main areas changed	Dataset runs, search citations, shard restore, delete scope
Docs	docs.fortemi.com/react

Highlights

1. Data imports have checked completion receipts. Each run stays bound to the plan you reviewed. Your import screen can show work in progress, failed work, and a checked success as distinct states.

2. Search results keep their source context. Core keeps supported field filters in place before ranking. It checks the proof behind source links. A review screen can show the source links that back a result.

3. Restored archives become working data. The PGlite `full-v1` import now writes to live storage. You can import notes, edit them, and export the current state.

4. Hard deletes respect all supplied scope limits. Note IDs must also match the chosen tenant, archive, and source rules. Shared file records stay intact when a note outside the purge still needs them.

Features shipped

Dataset Plans and Checked Runs

The new dataset workflow in `v2026.9.0` lets React apps check a source, preview data, and review a plan. It also shows run status and rejected records. Core adds checks on saved points used to resume a run. It also tracks where data came from and which steps changed it.

Core adds build profiles for text, vector, and graph indexes. Their receipts name the source, settings, and limits used.

These first contracts include sample code that runs in memory. That code does not prove that a remote service saved your data.

`v2026.9.9` adds `createMcpDatasetWorkflowApi` for the Fortemi Server dataset contract. Your app supplies the connection used to call the server. The adapter binds the preview and reviewed plan to the request. It checks the final receipt, then asks the server for a separate check.

Say an import times out. The workflow can mark the outcome as ambiguous: it has not verified that the import finished. Your app can keep that state distinct from verified completion.

Search With Source Proof

`v2026.9.6` carries field filters and source scope through the search adapters. Supported filters apply before results are ranked. Source links bind to checked proof. Search rejects malformed source proof from remote services.

For example, an app can narrow a search with a filter on an allowed field. The adapter checks whether that filter is supported. The app gets a clear error if the search goes beyond those limits.

Working With Restored Shards

A Knowledge Shard is a portable Fortemi archive. In `v2026.9.4`, PGlite restores the `2.0.0/full-v1` profile into live tables. Apps can search the restored notes and read their links. Later exports use current values, including edits made after import.

The restore checks the data before it writes. It applies the changes in one step that can roll back if it fails. Records owned outside the chosen scope stay intact. A loss report names data that cannot fit the live store.

`v2026.9.3` also fixed export filters for tags, collections, and embedding sets, which group search vectors. An export of one collection keeps that scope through the full-v1 path.

Repeat Imports and Scoped Deletes

`v2026.9.1` adopts Fortemi's source-note update contract in PGlite and RecordStore. An exact batch replay can return duplicate or unchanged without adding notes or edits. When text changes, the caller chooses version, replace, or conflict.

The delete changes carried into `v2026.9.8` reject empty or scope-only choices. Reusing an operation key with a changed choice also fails. An app can preview a purge and keep a receipt with none of the deleted text.

Model Routes and Source Links

`v2026.9.0` lets apps set model routes for search queries, documents, chat, edits, and tags. Routes can fall back through a set order. Apps can also keep one provider.

The React route hook exposes route checks and model selection previews. The note history view can read stored source links. The research-workbench example shows those links and the work that produced them.

Fixes

Remote reads now report errors when access is denied, a service is down, or a response is malformed. These errors used to appear as missing notes. The default standalone shard export names its `core-v1` profile and rejects unclear scope requests.

Note rows and search results regained keyboard controls. On small screens, save, delete, and restore have their own controls with clear names.

Performance & reliability

The release process now checks the exact packed files it uploads. A checksum handoff fix keeps the checksum manifest in place through the final check. In `v2026.9.8`, that process also waits for npm to show a package it has accepted.

Breaking changes & migrations

Apps that read source history must check its TypeScript `unknown` metadata type before they use its fields. Agent values can be null.

Live shard exports rebuild their manifest and checksums. Check the chosen profile's loss report after moving data.

Releases

• `v2026.9.0` (September 3, 2026): Dataset rules, React workflows, model routes, and source history examples.
• `v2026.9.1` (September 6, 2026): Source-note update contract and exact package upload checks.
• `v2026.9.2` (September 7, 2026): Checksum handoff fix.
• `v2026.9.3` (September 10, 2026): Scoped full-v1 export fix.
• `v2026.9.4` (September 11, 2026): Native full-v1 restore and remote response fixes.
• `v2026.9.5` (September 12, 2026): Stricter capability and version checks.
• `v2026.9.6` (September 14, 2026): Search filters and source proof checks.
• `v2026.9.7` (September 20, 2026): Purge and mobile controls; public package publication was partial.
• `v2026.9.8` (September 20, 2026): Carries those changes forward and fixes the npm visibility wait.
• `v2026.9.9` (September 20, 2026): Dataset adapter with checked run receipts.

Dependencies & security

Core now rejects unknown states and bad or unsupported versions when it checks support for a run. Dataset forms keep secret fields write-only. The September release notes name no package update tied to a security alert.

Docs & DX

The docs at docs.fortemi.com/react include the updated API reference and September release notes. The dataset workflow uses the `@fortemi/react/dataset` entry point. Apps supply the API that runs the work. The React controls handle review and status.

Tests & CI

September added tests for scoped exports, live restore, replay rules, and invalid capability inputs. Dataset browser tests cover keyboard tasks, previews, plan checks, status, and rejected records in Safari and Chromium.

Those tests do not complete a VoiceOver review. A skilled human review is still a separate step.

Cross-project impact

The React dataset adapter consumes Fortemi Server's dataset execution contract. The app must still supply the source for queries about how data changed.

Known issues & open threads

The remote dataset adapter is still alpha. It does not prove full support across servers or shards. Live source IDs still fall outside the current shard profiles. An export reports that loss.

What's next

The September release notes do not announce a dated next release.

Appendix

• Published packages: `@fortemi/core`, `@fortemi/graph`, `@fortemi/react`.
• Release dates: listed above; `v2026.9.7` retains its partial-publication caveat.
• Source / docs: github.com/Fortemi/fortemi-react · docs.fortemi.com/react.
• Window: September 1–30, 2026.