fortemi-react v2026.7.10

fortemi-react v2026.7.10 corrects two standard PGlite `core-v1` portability paths found during the cross-repository Fortemi conformance audit. It preserves the profile boundaries and contract authority published in `2026.7.9`.

Highlights

• Canonical unscored links (#355): note and URL links without an optional

PGlite confidence value now emit canonical score `1`. Metadata records the absent source value so a clean PGlite import restores `confidence: null` instead of inventing source confidence.

• Nested collection imports (#355): clean imports order collections

parent-first even when an archive lists a child before its parent. Missing parents and cycles fail before any PGlite mutation.

• Executable portability evidence: the standard PGlite exporter now creates

a self-validating schema 1.2.0 `core-v1` archive containing an unscored link and a child-before-parent hierarchy, imports it into a fresh database, and validates the semantic re-export.

Published Packages

• `@fortemi/[email protected]`
• `@fortemi/[email protected]`
• `@fortemi/[email protected]`

Compatibility

Contract revision 19 and Knowledge Shard schema 1.2.0 are unchanged. PGlite continues to advertise `core-v1`, RecordStore continues to advertise `record-v1`, and neither backend advertises `full-v1` production or persistence.

The already published `2026.7.9` artifacts remain immutable and do not contain these standard PGlite corrections.

Verification

• Full Core test suite
• Blocking portable-contract suite, including clean hierarchy and link

round-trips plus zero-mutation malformed-hierarchy cases

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

examples-e2e, e2e, and build