BMFF interpretation batch

  OpenMeta/src/openmeta/bmff_fields_decode.cc:1722 now exposes component roles, ordered member IDs, semantic node composition, isolation state, and typed relation counts. Per-component policies also flow directly into container_graph concept resolution and transfer diagnostics.

  Validation passed:

  - Six focused BMFF/concept/transfer/compatibility tests.
  - Full openmeta_tests: 100% passed.
  - CMake-generated Sphinx documentation build succeeded. It reported four unrelated existing documentation warnings.
  - git diff --check: clean.
  - Public Markdown and Sphinx documentation synchronized.
  - BMFF interpretation coverage increased from 88–92% to approximately 90–93%; overall Interpretation remains about 97%.

Author: ssh4net

CHANGES.md

@@ -1,5 +1,27 @@
 # OpenMeta Changes
 
+## 0.4.67 - 2026-07-10
+
+Changes compared with `0.4.66`.
+
+### Added
+
+- Added bounded BMFF component role and membership rows, including ordered
+  member item IDs, known/unknown and semantic node counts, isolated-state,
+  and typed auxiliary, derived-image, thumbnail, content-description, alpha,
+  depth, disparity, matte, and other relation-edge counts.
+- Added independent-image component coverage and direct `container_graph`
+  concept/transfer-diagnostic routing for per-component metadata and
+  multi-image policy fields.
+- Added compatibility-dump coverage for BMFF component role and membership
+  fields.
+
+### Changed
+
+- Updated public BMFF interpretation, support, compatibility, API stability,
+  and development documentation for component membership and typed relation
+  summaries.
+
 ## 0.4.66 - 2026-07-09
 
 Changes compared with `0.4.65`.

VERSION

@@ -1 +1 @@
-0.4.66
+0.4.67

docs/api_stability.md

@@ -47,10 +47,12 @@ entry index=0 name="Make" key_kind="exif_tag" value_kind="text" ...
 Each emitted entry is based on `visit_metadata(...)`, so ordering, duplicate
 handling, and naming follow the selected `ExportNameStyle`. By default the
 dump uses the stable `FlatHost` contract.
-BMFF derived policy fields such as `bmff:scene.component.metadata_policy` and
+BMFF component membership, role, and policy fields such as
+`bmff:scene.component.item_id`, `bmff:scene.component.role`,
+`bmff:scene.component.metadata_policy`, and
 `bmff:scene.component.multi_image_policy` are emitted as normal `bmff_field`
-entries, so host baselines can verify container-graph transfer policy evidence
-without a separate decoder-specific dump format.
+entries, so host baselines can verify container-graph evidence without a
+separate decoder-specific dump format.
 
 Metadata entry lines include:
 

docs/compatibility_dump.md

@@ -17,7 +17,7 @@ model should stay compact:
 | Area | Purpose | Readiness |
 | --- | --- | --- |
 | Decoding | Find metadata carriers and decode EXIF, XMP, IPTC, ICC, Photoshop IRB, JUMBF/C2PA, EXR, and related blocks into `MetaStore` entries. | High, about 98-100% for the current target scope. |
-| Interpretation | Normalize names and values, group entries by meaning, and classify source-bound data such as RAW crop, exposure adjustment, color/profile/source-color-transform evidence, RAW curves/linearity metadata with descriptor-backed compressed-storage applicability, lens-correction, sensor, BMFF brand/item-property associations and rollups including `avio` AVIF brands, item groups, item semantic counts, whole-scene policy hints, graph-component and per-component summaries, `container_graph` concepts, primary item properties, primary metadata-carrier flags, primary sidecar and scene summaries, and display-transform summaries, JUMBF labels, Photoshop IRB embedded carriers plus fixed-layout, XML/text, working-path and numbered clipping-path records, byte-count, descriptor-header, simple descriptor-item, enum, and bounded nested list/object summaries, EXIF 3.1 correction/noise labels, version/firmware-style value formatting for selected EXIF/Nikon/Olympus/native RAF contexts, selected Sony ILCE-7RM6 correction-offset routing, Fujifilm flash white-balance naming, Apple/FLIR/JVC/GE/Reconyx/Microsoft/Nintendo/Sanyo scalar MakerNote labels, current Canon RF/Nikon Z lens labels, an ambiguous Pentax Sigma/Samsung/Tokina lens-family label, EXIF/XMP GPS timestamp composites, computational, thermal, stitch/panorama capture state, and vendor-private fields. | Medium-high, about 97%. |
+| Interpretation | Normalize names and values, group entries by meaning, and classify source-bound data such as RAW crop, exposure adjustment, color/profile/source-color-transform evidence, RAW curves/linearity metadata with descriptor-backed compressed-storage applicability, lens-correction, sensor, BMFF brand/item-property associations and rollups including `avio` AVIF brands, item groups, item semantic counts, whole-scene policy hints, graph-component summaries with per-component roles, member item IDs, semantic composition and typed relation counts, `container_graph` concepts, primary item properties, primary metadata-carrier flags, primary sidecar and scene summaries, and display-transform summaries, JUMBF labels, Photoshop IRB embedded carriers plus fixed-layout, XML/text, working-path and numbered clipping-path records, byte-count, descriptor-header, simple descriptor-item, enum, and bounded nested list/object summaries, EXIF 3.1 correction/noise labels, version/firmware-style value formatting for selected EXIF/Nikon/Olympus/native RAF contexts, selected Sony ILCE-7RM6 correction-offset routing, Fujifilm flash white-balance naming, Apple/FLIR/JVC/GE/Reconyx/Microsoft/Nintendo/Sanyo scalar MakerNote labels, current Canon RF/Nikon Z lens labels, an ambiguous Pentax Sigma/Samsung/Tokina lens-family label, EXIF/XMP GPS timestamp composites, computational, thermal, stitch/panorama capture state, and vendor-private fields. | Medium-high, about 97%. |
 | Query | Find entries by name, fuzzy term, or semantic group, then expose normalized query candidates, structured interpretation records, bounded cross-family concept resolutions, transfer hints, and conflict flags for crop/border/active-area, exposure/gain, color/WB/profile/source-color-transform, orientation, date/time, GPS, lens-correction, computational/thermal/stitch, and RAW/source-processing fields across standard and vendor metadata. | Medium-high, about 88-93%. |
 | Creation | Build fresh metadata entries from host-provided values. | Medium, about 55-65%. |
 | Editing | Modify existing logical metadata entries while preserving valid surrounding structure. | Medium, about 60-70%. |
@@ -739,6 +739,11 @@ This policy surface is intentionally marked draft and may be refined.
     `scene.graph_multi_image_component_count`,
     `scene.graph_content_bound_metadata_component_count`,
     `scene.graph_observed_edge_count`,
+    per-component rows (`scene.component.index`, `scene.component.role`,
+    `scene.component.item_id`, known/unknown and semantic `*_node_count`
+    fields, `scene.component.isolated`, typed auxiliary/derived/thumbnail/
+    content-description `*_edge_count` fields, and alpha/depth/disparity/matte
+    auxiliary edge counts),
     `scene.primary_graph_component_node_count`,
     `scene.primary_graph_component_*_node_count`,
     `scene.primary_graph_component_edge_count`,