Backfill three.js reference provenance

docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md

@@ -395,14 +395,16 @@ compliance reference side is now explicit too.
 The `met4citizen/TalkingHead` embodied companion and narration reference side
 is now explicit too, and the `apache/echarts` analytics and report reference
 side is now explicit too, and the `Hypercubers/hypercubing.xyz` knowledge,
-taxonomy, and leaderboard/report reference side is now explicit too.
+taxonomy, and leaderboard/report reference side is now explicit too, and the
+`mrdoob/three.js` browser scene and renderer reference side is now explicit
+too.
 
 The next clean bounded move is a source-backed pass on the remaining
 repo-backed reference-incorporation families whose hierarchy or canon
 follow-through is still only implicit in
 `hypertwist-reference-incorporation-targets.json`, starting with
-`mrdoob/three.js` if you want the adjacent browser scene, renderer, and
-render-loop reference side closed to the same standard.
+`pmndrs/react-three-fiber` if you want the adjacent React renderer and
+event-bridge reference side closed to the same standard.
 
 For the readable all-rows follow-up board that pairs this audit with the reset schedule, use:
 

docs/HYPERTWIST_THREE_JS_REFERENCE_INCORPORATION_PROVENANCE_BOARD_2026-05-27.md

@@ -0,0 +1,117 @@
+# HyperTwist three.js Reference Incorporation Provenance Board - 2026-05-27
+
+## Status
+
+This document is the source-backed provenance and hierarchy note for the live
+repo-backed reference-incorporation side currently materialized from
+`mrdoob/three.js`.
+
+It closes the source-specific reference side that remained implicit after the
+landed `Phase 3R-F` packet and the broader live-lane audit.
+
+It answers one narrow question:
+
+- does the live `mrdoob/three.js` reference target reopen already landed
+  first-party browser spatial scene, renderer, camera, render-loop, and WebXR
+  integration implementation, or does it instead need a reference-side
+  provenance-board and canon backfill
+
+Result:
+
+- no product-code reopening is required
+- yes reference-side provenance-board and feature-canon backfill is required
+
+## Source basis
+
+- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
+- `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md`
+- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
+- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
+- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
+- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\hypertwist-reference-incorporation-targets.json`
+- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\raw-extracts\browser-spatial-support-reference-pages.jsonl`
+
+## Counts confirmed from current first-party materialization
+
+Current live `mrdoob/three.js` reference-incorporation targets:
+
+- `1` total rewritten reference target
+- that target is under `Browser 3D and XR Support`
+- it stays inside the already-landed `Phase 3R-F` bounded lane
+
+Exact surface:
+
+1. `reference/browser-spatial-scene-reference-page-stack`
+   - `SurfaceType`: `browser-spatial-scene-reference`
+   - `IncorporationChannel`: `browser-spatial-scene-contract`
+   - `TargetAssetFamily`: `scene-contract-note`
+
+Important adjacent fact:
+
+- this target preserves scene and renderer lifecycle, camera and raycaster
+  binding, frameloop invalidation, and WebXR-manager integration semantics
+  already enforced by the landed lane
+- it stays subordinate to the broader landed browser spatial owner trio and
+  does not absorb the adjacent `react-three-fiber` or `xr` reference slices
+
+## Slice-local verdict
+
+| Slice | Primary authority | Secondary value kept | Result |
+|---|---|---|---|
+| First-party browser spatial scene, renderer, camera, render-loop, and WebXR-manager implementation | first-party current code plus landed `Phase 3R-F` packet | retained `mrdoob/three.js` reference target stays a subordinate provenance-grounding surface | unchanged live implementation owner |
+| Rewritten browser scene and renderer-contract grounding | `mrdoob/three.js` retained permissive lane | factual scene lifecycle, camera binding, frameloop invalidation, and WebXR-manager semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
+
+## Why no product-code reopening is required
+
+The live surface here is already a rewritten first-party target, not copied
+donor docs, donor editor shell, donor example chrome, or a silent upstream
+private fork.
+
+The checked target explicitly requires:
+
+- preserving bounded browser scene, renderer, camera, render-loop, and WebXR
+  manager semantics
+- rewriting donor docs or demo wording, donor editor-shell framing, and donor
+  example chrome
+
+That means the retained surface is provenance and factual grounding, not donor
+browser-shell ownership.
+
+So this pass does not reopen:
+
+- the closed `Phase 3R-F` first-party browser spatial lane
+- the adjacent `pmndrs/react-three-fiber` renderer-bridge slice
+- the adjacent `pmndrs/xr` XR-session slice
+- any broader browser app-shell or editor ownership posture
+
+## Current exact grounded role
+
+`mrdoob/three.js` currently grounds one live rewritten first-party
+contract/reference target for `Browser 3D and XR Support`:
+
+- browser spatial scene and renderer contract
+
+This target preserves bounded browser-scene semantics while keeping all
+surfaced prose and shell framing first-party.
+
+## Backfill result
+
+### Earlier incorporation audit reopened
+
+- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
+
+### Feature canon reopened
+
+- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
+
+## Final call
+
+The live `mrdoob/three.js` reference-incorporation side is now explicit:
+
+- `1` rewritten first-party contract/reference target
+- it remains inside the landed `Phase 3R-F` browser spatial lane
+- scene lifecycle, camera binding, frameloop, and WebXR-manager grounding stay
+  explicit
+
+This closes the `mrdoob/three.js` reference side without reopening product
+code.

docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md

@@ -139,6 +139,7 @@ Do not collapse those three tiers into one undifferentiated "features" voice.
 | Analytics/reporting surfaces | Implemented now | landed analytics/reporting packets | Reporting is real, but bounded to accepted retained slices. |
 | Rewritten training analytics and report reference grounding | Implemented now | `apache/echarts` retained permissive lane + first-party current code | Current live `Training Analytics` reference side includes four rewritten first-party targets grounded in retained `apache/echarts`: session outcome and progress reporting, analytics data-view and export, timing-trend history and overview interaction, and the optional richer explainer or sidecar boundary. This does not displace the landed `Phase 3R-C` first-party analytics/reporting owner or elevate `ecomfe/echarts-gl` and `ecomfe/zrender` beyond support-only sidecars. |
 | Browser/spatial/media adjunct surfaces | Implemented now | landed `three.js`, `react-three-fiber`, `xr`, `model-viewer`, `remotion` packets | These are implemented bounded families, not proof of unlimited browser-shell parity. |
+| Rewritten browser spatial scene and renderer reference grounding | Implemented now | `mrdoob/three.js` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `mrdoob/three.js`: the browser spatial scene and renderer contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `react-three-fiber` renderer-bridge and `xr` session slices. |
 
 ## Feature families