v2026.6.8

fortemi-react v2026.6.8 release notes.

fortemi-react v2026.6.8

fortemi-react v2026.6.8 adds richer static metadata to the `@fortemi/core/aiwg-index` contract for Pagenary-style documentation consumers.

Highlights

  • Rich SKOS metadata: `aiwg.fortemi.index.record.v1` records can now include optional `skos_concepts` with ids, labels, definitions, schemes, notation, URIs, alternate labels, and structured metadata.
  • SKOS relation edges: records can carry optional `skos_relations` for `broader`, `narrower`, `related`, or project-specific concept relationships.
  • W3C PROV-style event chains: records can carry optional `provenance_events` with activity, agent, timestamps, source/path, confidence/privacy, and arbitrary attributes.
  • Relationship metadata: relationship entries can include optional labels, confidence, privacy classification, and structured metadata beyond `type` and `target_id`.
  • Projection-safe static indexes: chunked indexes keep these rich fields in detail records by default, so scan/query behavior remains focused on the existing flat fields.

Published Packages

Compatibility

Existing `2026.6.7` consumers upgrade without source changes. The export schema remains `aiwg.fortemi.index.record.v1`; the new fields are optional and omitted when unavailable. Existing search, filtering, facets, and chunked scan behavior continue to use the established flat `facets`, `tags`, `concepts`, `relationships`, and `provenance` fields.

Vendored consumers such as Pagenary can migrate incrementally: keep validating and querying existing records as before, then read full records and check `skos_concepts`, `skos_relations`, `provenance_events`, or relationship metadata when rendering metadata panels.

Verification

Release preparation used the configured AIWG release flow:

  • `pnpm typecheck`
  • `pnpm lint`
  • `pnpm test:core`
  • `pnpm test:e2e`
  • `pnpm build`
  • CI green before tag publication