Align Phase 2R-B subordinate source audit rows

This commit is contained in:
axiomlogicnexus 2026-05-27 23:44:05 +02:00
parent 22b76a48c5
commit 01ae3abfa3
2 changed files with 117 additions and 25 deletions

View file

@ -0,0 +1,92 @@
# HyperTwist Phase 2R-B Subordinate Source Audit Alignment - 2026-05-27
## Status
This document is the row-source audit alignment note for the already-closed
`Phase 2R-B` subordinate permissive rows in HyperTwist.
It answers one narrow question:
- after the later subordinate-stack reconciliations landed, do the `v6.3`
source-audit rows still speak about these repos like open "determine whether
it should remain active" candidates instead of already-closed bounded
sidecars beneath landed anchors
Result:
- yes, the source-audit layer was still using open-evaluation posture for both
subordinate browser-support rows and subordinate analytics/viewer rows
- the state board and later subordinate-stack reconciliation notes were
already correct
- the needed fix is source-audit alignment only
- no product code, live ownership, or roadmap routing changed from this pass
## Affected closed subordinate rows
### Browser-spatial support stack
- `pmndrs/postprocessing`
- `pmndrs/react-postprocessing`
- `pmndrs/drei`
- `pmndrs/three-stdlib`
- `pmndrs/maath`
- `pmndrs/uikit`
- `pmndrs/zustand`
- `pmndrs/leva`
- `pmndrs/use-gesture`
- `pmndrs/react-spring`
- `@react-spring/core`
- `@react-spring/shared`
- `@react-spring/types`
- `@react-spring/parallax`
- `@react-spring/rafz`
- `@react-spring/animated`
### Analytics and browser-viewer support stack
- `ecomfe/zrender`
- `ecomfe/echarts-gl`
- `google/model-viewer/packages/model-viewer-effects`
- `google/model-viewer/packages/modelviewer.dev`
- `google/model-viewer/packages/render-fidelity-tools`
- `google/model-viewer/packages/space-opera`
- `KhronosGroup/glTF-Sample-Renderer`
- `KhronosGroup/glTF-Sample-Viewer`
## Required source-audit posture
For these rows the source-audit pack must now say:
- the row is already closed as a bounded subordinate sidecar beneath a landed
anchor
- the task is owner-boundary confirmation and narrower sidecar-gap reopen
criteria only
- no default widening packet is open
- do not frame the row as a fresh implementation candidate or standalone owner
lane
## Source basis
- `C:\HyperTwist\docs\HYPERTWIST_BROWSER_SPATIAL_SUPPORT_SUBORDINATE_STACK_SOURCE_TRUTH_RECONCILIATION_2026-05-27.md`
- `C:\HyperTwist\docs\HYPERTWIST_ANALYTICS_AND_BROWSER_VIEWER_SUBORDINATE_STACK_SOURCE_TRUTH_RECONCILIATION_2026-05-27.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md`
- `C:\HyperTwist\docs\repo_portfolio_unified_source_audit_v6_3.csv`
## Alignment rule
For each affected row:
- replace open "determine whether it should remain active" goals with explicit
closed subordinate-boundary validation goals
- replace deliverables that imply fresh activation with subordinate-boundary
notes and narrower reopen criteria only
- replace candidate-style coding instructions with closed bounded-sidecar
instructions
- keep current live-state and reset-lane values unchanged
## Final call
These rows are not waiting for a generic permissive implementation decision.
They already sit in canon as closed subordinate sidecars beneath landed anchors,
and the source-audit pack must now describe them that way.

View file

@ -1,4 +1,4 @@
"repo","primary_url","project","phase_g_bucket","stack_layer","audit_tier","tier_queue_order","global_order","wave_number","portfolio_priority_score","execution_priority_score_v3","current_confidence","modification_scope_detail_v3","recommended_action_v2","repurposing_potential_v2","audit_goal","inspect_emphasis","source_code_audit_targets","source_inspection_questions","integration_realization_detail","consolidation_detail","repurpose_detail","merger_partner_1","merger_type_1","merger_rationale_1","merger_partner_2","merger_type_2","merger_rationale_2","merger_partner_3","merger_type_3","merger_rationale_3","cross_project_transfer_targets","cross_project_transfer_rationale","reclassify_up_if","reclassify_down_if","deliverable_expected","session_note_template","recommended_context_packet","phase_g_master_list_rationale","phase_g_bucket_reason","coding_model_instruction_v3","source_audit_packet_id","cluster_tag","_repo_norm","v5_runtime_project","v5_scriptorium_override_status","v5_scriptorium_bucket","v5_scriptorium_stack_layer","v5_scriptorium_current_reality_status","v5_scriptorium_supersedes_prior_assessment","v5_source_of_truth","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","v6_supplemental_intake_present","v6_supplemental_source_groups","v6_supplemental_source_sections","v6_supplemental_source_files","v6_reference_material_position","v6_kali_agent_access_relevance","v6_branch_seed_prompt_included","v6_branch_seed_scope","v6_intake_wave","v6_notes","v6_source_of_truth","project_rank_num","tier_rank_num","priority_num","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","preferred_boundary_model_v6_1","open_compliance_if_used_as_is_v6_1","reverse_engineer_if_proprietary_core_needed_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","as_is_incorporation_sensible_v6_1","v6_2_sre_layer","v6_2_sre_stratum","v6_2_sre_role","v6_2_sre_family","v6_2_related_kali_package","v6_2_related_upstream_repo","v6_2_kali_package_suffices_for_tool_execution","v6_2_upstream_repo_preferred_for_deep_eval","v6_2_index_page_followup_useful","v6_2_index_page_followup_reason","v6_2_sre_notes","v6_2_dnspy_ilspy_relevance","v6_3_source_of_truth","v6_3_merge_note","v6_3_live_state_2026_05_11","v6_3_reset_lane_2026_05_11","v6_3_reset_next_step_2026_05_11"
"repo","primary_url","project","phase_g_bucket","stack_layer","audit_tier","tier_queue_order","global_order","wave_number","portfolio_priority_score","execution_priority_score_v3","current_confidence","modification_scope_detail_v3","recommended_action_v2","repurposing_potential_v2","audit_goal","inspect_emphasis","source_code_audit_targets","source_inspection_questions","integration_realization_detail","consolidation_detail","repurpose_detail","merger_partner_1","merger_type_1","merger_rationale_1","merger_partner_2","merger_type_2","merger_rationale_2","merger_partner_3","merger_type_3","merger_rationale_3","cross_project_transfer_targets","cross_project_transfer_rationale","reclassify_up_if","reclassify_down_if","deliverable_expected","session_note_template","recommended_context_packet","phase_g_master_list_rationale","phase_g_bucket_reason","coding_model_instruction_v3","source_audit_packet_id","cluster_tag","_repo_norm","v5_runtime_project","v5_scriptorium_override_status","v5_scriptorium_bucket","v5_scriptorium_stack_layer","v5_scriptorium_current_reality_status","v5_scriptorium_supersedes_prior_assessment","v5_source_of_truth","v6_license_annotation","v6_license_annotation_status","v6_license_annotation_source","v6_supplemental_intake_present","v6_supplemental_source_groups","v6_supplemental_source_sections","v6_supplemental_source_files","v6_reference_material_position","v6_kali_agent_access_relevance","v6_branch_seed_prompt_included","v6_branch_seed_scope","v6_intake_wave","v6_notes","v6_source_of_truth","project_rank_num","tier_rank_num","priority_num","copyleft_relevance_v6_1","copyleft_strategy_v6_1","copyleft_rationale_v6_1","preferred_boundary_model_v6_1","open_compliance_if_used_as_is_v6_1","reverse_engineer_if_proprietary_core_needed_v6_1","copyleft_strategy_confidence_v6_1","copyleft_manual_review_trigger_v6_1","as_is_incorporation_sensible_v6_1","v6_2_sre_layer","v6_2_sre_stratum","v6_2_sre_role","v6_2_sre_family","v6_2_related_kali_package","v6_2_related_upstream_repo","v6_2_kali_package_suffices_for_tool_execution","v6_2_upstream_repo_preferred_for_deep_eval","v6_2_index_page_followup_useful","v6_2_index_page_followup_reason","v6_2_sre_notes","v6_2_dnspy_ilspy_relevance","v6_3_source_of_truth","v6_3_merge_note","v6_3_live_state_2026_05_11","v6_3_reset_lane_2026_05_11","v6_3_reset_next_step_2026_05_11"
"HactarCE/Hyperspeedcube","https://github.com/HactarCE/Hyperspeedcube","HyperTwist","Locked Foundation","nD / hypercubing simulation substrate","P0","20","9203","2.0","160.0","193.0","high","This row is already live for its current justified slices. Preserve the landed hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring boundaries, and widen only through owned HyperTwist work.","integrate","direct","Validate the current first-party owner boundaries for HactarCE/Hyperspeedcube and record any narrower owned widening targets that remain after the landed Phase 6R-A/K/L/M/N slice.","Landed hyper catalog, notation, replay-log, replay verification, stats-shape, solve-record, and puzzle-DSL owner boundaries as live first-party material.","Inspect current first-party owner boundaries, landed packet scope, retained adjacent hyper/runtime families, and unresolved owned widening targets only.","Which remaining hyper owner gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-A/K/L/M/N packets?","Preserve as the landed first-party hyper owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-A/K/L/M/N packets; do not route work through donor-extraction framing.","Treat current first-party HyperTwist code as the owner. Keep MagicTile, Magic120Cell, MagicCube5D, and retained benchmark rows as adjacent families or references, not donor merge targets for the already landed slice.","Repurpose here means: ordinary owned enhancement of the landed hyper owner lane, not subsystem harvesting from an external candidate queue.","","","","","","","","","","Owned widening only","The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing.","Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals.","Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection.","Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture.","1) Which landed hyper owner boundaries are already closed
2) Which narrower owned widening targets, if any, remain
3) Which adjacent retained rows stay reference-only or family-adjacent","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","Keep in canon as an already-landed first-party hyper owner lane and route all future work through owned widening.","Already-landed hyper owner row for bounded puzzle catalog, notation, replay, stats, and DSL families; no donor thesis remains for the current slice.","Audit HactarCE/Hyperspeedcube only as an already-landed permissive owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate.","HT_hyper_engine_0001","HT_hyper_engine","hactarce/hyperspeedcube","","","","","","","Original global P0-P3 source audit retained","MIT","known_from_reference_material","uploaded_reference_docs","yes","hypertwist_and_scriptoriumai","HyperTwist","HyperTwist & ScriptoriumAI.txt","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Usually indirect","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","Existing v5 row reaffirmed or widened by v6 supplemental intake.","v6_unified_source_of_truth_pack","2","1","160.0","permissive_or_noncopyleft_known","direct_incorporation_ok","This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.","Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.","high","strategic-or-implemented-component","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Later Phase 6R-A/K/L/M/N preserve sequence closed. Preserve as the landed first-party hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, not from the old candidate queue wording."
@ -223,36 +223,36 @@
9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.","MU_misc_0004","MU_misc","rhasspy/piper","","","","","","","Original global P0-P3 source audit retained","MIT code; voice artifacts reviewed separately","known_from_reference_material","uploaded_reference_docs","no","","","","Supplemental intake references are advisory only; v6 adjudication remains the source of truth.","Potentially relevant","yes","v6 unified all-project source-of-truth pack","v5_carry_forward","","v6_unified_source_of_truth_pack","4","3","71.0","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.","Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.","Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.","Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.","high","voice-artifact-review-required","yes","","","","","","","","","","","","","v6.3_final_source_of_truth","Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.","implemented_live_permissive","landed_permissive_preserve","Phase 6R-G is closed. Preserve as the landed bounded local narration sidecar lane; keep broad voice-model and payload review separate."
"met4citizen/TalkingHead","https://github.com/met4citizen/TalkingHead","HyperTwist","Donor Bench","Browser embodied coach surface","P2","","","","","","medium","Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.","repurpose","moderate modification","Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.","avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.","","Repurpose here means: turn it into a browser-side embodied coach or companion layer.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.","HT_browser_surface_0001","HT_browser_surface","met4citizen/talkinghead","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.","Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md."
"apache/echarts","https://github.com/apache/echarts","HyperTwist","Donor Bench","Browser analytics and reporting surface","P2","","","","","","medium","Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.","repurpose","moderate modification","Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.","option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.","","Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.","HT_browser_surface_0002","HT_browser_surface","apache/echarts","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.","Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md."
"ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","Merge Bench","Browser 3D analytics and explainer surface","P3","","","","","","medium","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","integrate","moderate modification","Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.","3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.","HT_browser_surface_0003","HT_browser_surface","ecomfe/echarts-gl","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_analytics_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; no default widening packet is open."
"KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","Donor Bench","Browser asset validation and viewer surface","P3","","","","","","medium","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","repurpose","moderate modification","Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.","validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.","HT_browser_surface_0004","HT_browser_surface","khronosgroup/gltf-sample-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; no default widening packet is open."
"ecomfe/echarts-gl","https://github.com/ecomfe/echarts-gl","HyperTwist","Merge Bench","Browser 3D analytics and explainer surface","P3","","","","","","medium","Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.","integrate","moderate modification","Confirm that ecomfe/echarts-gl remains a closed subordinate optional 3D analytics and explainer sidecar beneath the landed apache/echarts anchor, and record only narrower sidecar-gap reopen criteria, if any.","3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect the retained optional 3D analytics and explainer sidecar slice only in relation to the landed apache/echarts anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.","","Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl only as a closed subordinate optional 3D analytics and explainer sidecar row for HyperTwist. Validate that it remains bounded beneath the landed apache/echarts anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0003","HT_browser_surface","ecomfe/echarts-gl","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.","Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_analytics_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; no default widening packet is open."
"KhronosGroup/glTF-Sample-Viewer","https://github.com/KhronosGroup/glTF-Sample-Viewer","HyperTwist","Donor Bench","Browser asset validation and viewer surface","P3","","","","","","medium","Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.","repurpose","moderate modification","Confirm that KhronosGroup/glTF-Sample-Viewer remains a closed subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect the retained standards-aware asset QA and validation sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.","","Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer only as a closed subordinate standards-aware asset QA and validation sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0004","HT_browser_surface","khronosgroup/gltf-sample-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.","Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer","https://github.com/google/model-viewer","HyperTwist","Donor Bench","Browser 3D presentation and inspection surface","P2","","","","","","medium","Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.","repurpose","moderate modification","Determine whether model-viewer should remain the primary browser presentation and inspection donor for HyperTwist companion surfaces.","custom element runtime, annotations, AR and controls, scene graph access, space-opera/editor package, render fidelity tools","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.","","Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.","HT_browser_surface_0005","HT_browser_surface","google/model-viewer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.","Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.","Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md."
"mrdoob/three.js","https://github.com/mrdoob/three.js","HyperTwist","Donor Bench","Browser 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.","repurpose","moderate modification","Determine whether three.js should remain the default browser 3D substrate beneath HyperTwist companion surfaces.","renderer, scene, camera, math core, loaders, WebXR manager, addons, editor","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.","","Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.","HT_browser_surface_0006","HT_browser_surface","mrdoob/three.js","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.","Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser `3D` substrate lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
"pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","Merge Bench","Browser post-processing substrate","P3","","","","","","medium","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","integrate","moderate modification","Determine whether postprocessing should remain the bounded browser effect-composer substrate beneath the companion stack.","EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.","HT_browser_surface_0007","HT_browser_surface","pmndrs/postprocessing","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser post-effect substrate beneath the landed browser-spatial owner trio; no default widening packet is open."
"pmndrs/postprocessing","https://github.com/pmndrs/postprocessing","HyperTwist","Merge Bench","Browser post-processing substrate","P3","","","","","","medium","Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.","integrate","moderate modification","Confirm that pmndrs/postprocessing remains a closed subordinate browser post-effect substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","EffectComposer, EffectPass, outline, SSAO, effect catalog, performance assumptions","Inspect the retained browser post-effect substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.","","Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.","Audit pmndrs/postprocessing only as a closed subordinate browser post-effect substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0007","HT_browser_surface","pmndrs/postprocessing","","","","","","","","Zlib","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.","Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser post-effect substrate beneath the landed browser-spatial owner trio; no default widening packet is open."
"pmndrs/react-three-fiber","https://github.com/pmndrs/react-three-fiber","HyperTwist","Donor Bench","Browser React 3D substrate","P2","","","","","","medium","Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.","repurpose","moderate modification","Determine whether react-three-fiber should remain the default React renderer substrate for browser companion scenes.","Canvas, createRoot, reconciler runtime, event system, hooks, native path","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.","","Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.","HT_browser_surface_0008","HT_browser_surface","pmndrs/react-three-fiber","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.","Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party React-side browser renderer lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
"pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","Merge Bench","Browser 3D helper and abstraction layer","P3","","","","","","medium","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","integrate","moderate modification","Determine which drei helpers should remain active merge candidates for browser companion surfaces and which should be ignored as generic convenience.","Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.","HT_browser_surface_0009","HT_browser_surface","pmndrs/drei","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/drei","https://github.com/pmndrs/drei","HyperTwist","Merge Bench","Browser 3D helper and abstraction layer","P3","","","","","","medium","Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.","integrate","moderate modification","Confirm that pmndrs/drei remains a closed subordinate browser helper and abstraction shelf beneath the landed browser-spatial owner trio and pmndrs/react-three-fiber, and record only narrower sidecar-gap reopen criteria, if any.","Html overlays, View split rendering, TransformControls, Environment, Gltf helper behavior","Inspect the retained browser helper and abstraction shelf slice only in relation to the landed browser-spatial owner trio and pmndrs/react-three-fiber, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.","","Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.","Audit pmndrs/drei only as a closed subordinate browser helper and abstraction shelf row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and pmndrs/react-three-fiber and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0009","HT_browser_surface","pmndrs/drei","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.","Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate helper and abstraction layer above pmndrs/react-three-fiber inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/xr","https://github.com/pmndrs/xr","HyperTwist","Donor Bench","Browser XR and immersive UI substrate","P2","","","","","","medium","Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.","repurpose","moderate modification","Determine whether pmndrs/xr should remain the default browser XR interaction donor for companion immersive surfaces.","XR store and runtime, dom overlay, controller locomotion, pointer-events, handle and manipulation layer","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.","","Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.","HT_browser_surface_0010","HT_browser_surface","pmndrs/xr","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.","Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","implemented_live_permissive","landed_permissive_preserve","Phase 3R-F closed. Preserve as the landed first-party browser XR session and immersive interaction lane; start future widening from the live-lane audit, then the 3R-F implementation packet, then REPO_LICENSE_TRACKING.md."
"pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","Donor Bench","Browser spatial UI surface","P2","","","","","","medium","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","repurpose","moderate modification","Determine whether pmndrs/uikit should remain the default browser spatial UI donor for HyperTwist companion surfaces.","flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.","HT_browser_surface_0011","HT_browser_surface","pmndrs/uikit","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser spatial-UI layer beside pmndrs/xr inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","Merge Bench","Browser motion and animation layer","P3","","","","","","medium","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","integrate","moderate modification","Determine which react-spring motion surfaces should remain active merge candidates for browser companion views.","Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.","HT_browser_surface_0012","HT_browser_surface","pmndrs/react-spring","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser-side motion substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/uikit","https://github.com/pmndrs/uikit","HyperTwist","Donor Bench","Browser spatial UI surface","P2","","","","","","medium","Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.","repurpose","moderate modification","Confirm that pmndrs/uikit remains a closed subordinate browser spatial-UI sidecar beneath the landed browser-spatial owner trio and pmndrs/xr, and record only narrower sidecar-gap reopen criteria, if any.","flex and yoga layout, clipping, scrolling, text and media components, Fullscreen and Container behavior","Inspect the retained browser spatial-UI sidecar slice only in relation to the landed browser-spatial owner trio and pmndrs/xr, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.","","Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.","Audit pmndrs/uikit only as a closed subordinate browser spatial-UI sidecar row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and pmndrs/xr and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0011","HT_browser_surface","pmndrs/uikit","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser spatial-UI layer beside pmndrs/xr inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/react-spring","https://github.com/pmndrs/react-spring","HyperTwist","Merge Bench","Browser motion and animation layer","P3","","","","","","medium","Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.","integrate","moderate modification","Confirm that pmndrs/react-spring remains a closed subordinate browser-side motion substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","Controller and SpringValue runtime, scheduler, layered explainer behavior, browser motion ergonomics","Inspect the retained browser-side motion substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.","","Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.","","","","","","","","","","","","Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.","Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.","pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.","Audit pmndrs/react-spring only as a closed subordinate browser-side motion substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_surface_0012","HT_browser_surface","pmndrs/react-spring","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.","Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-24.","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser-side motion substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"screenpipe/screenpipe","https://github.com/screenpipe/screenpipe","HyperTwist","Donor Bench","Support-plane capture, history, and replay sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether screenpipe/screenpipe should remain active in the Support-plane capture, history, and replay sidecar lane and which seams should stay bounded.","capture lifecycle, local engine seams, permission middleware, vault storage, timeline UX, notification surfaces","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0001","HT_support_sidecars","screenpipe/screenpipe","","","","","","","","MIT OR Apache-2.0 core; enterprise-restricted ee/","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.","Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.","Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.","Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.","high","mixed-license-path-review-required","no","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-E closed. Preserve as the landed first-party capture/history/replay, deterministic-permission, persistence, vault-lifecycle, timeline-review, and explicit permissive-core-versus-ee/ subtree-compliance lane; start future widening from the live-lane audit, then Phase 4R-E, then REPO_LICENSE_TRACKING.md."
"remotion-dev/remotion","https://github.com/remotion-dev/remotion","HyperTwist","Donor Bench","Commercially licensed media-export and explainer sidecar","P2","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether remotion-dev/remotion should remain active in the Media export and explainer sidecar lane and which seams should stay bounded.","player shell, renderer pipeline, studio/editor package, media parser, export workflow","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_support_sidecars cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_support_sidecars_0002","HT_support_sidecars","remotion-dev/remotion","","","","","","","","Custom two-tier commercial license","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.","Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.","Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.","Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.","high","commercial-license-sidecar-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-F closed. Preserve as the landed first-party media-export, embedded playback, parser, explainer-studio, and package-split commercial-compliance lane; start future widening from the live-lane audit, then Phase 4R-F, then REPO_LICENSE_TRACKING.md; keep the explicit company-license and package-split boundary visible."
"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether ecomfe/zrender should remain active in the Browser 2D render substrate lane and which seams should stay bounded.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_analytics_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate 2D render substrate beneath the landed apache/echarts lane; no default widening packet is open."
"ecomfe/zrender","https://github.com/ecomfe/zrender","HyperTwist","Merge Bench","Browser 2D render substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that ecomfe/zrender remains a closed subordinate lower-level 2D painter and event substrate beneath the landed apache/echarts anchor, and record only narrower sidecar-gap reopen criteria, if any.","scene graph, canvas and SVG painters, event handling, animation primitives","Inspect the retained lower-level 2D painter and event substrate slice only in relation to the landed apache/echarts anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.","Audit ecomfe/zrender only as a closed subordinate lower-level 2D painter and event substrate row for HyperTwist. Validate that it remains bounded beneath the landed apache/echarts anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0001","HT_browser_support","ecomfe/zrender","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.","Use directly as a bounded browser-side dependency beneath analytics and reporting layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_analytics_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate 2D render substrate beneath the landed apache/echarts lane; no default widening packet is open."
"pissang/claygl","https://github.com/pissang/claygl","HyperTwist","Merge Bench","Retained alternative browser 3D comparison substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser 3D comparison thesis for pissang/claygl in HyperTwist: what exact narrow infrastructure value survives, how it compares against the landed browser spatial stack, and whether any later sidecar-gap reopening is actually justified.","renderer, scene graph, cameras and controls, picking, compositor, loaders","Inspect renderer and scene infrastructure, camera and control patterns, picking and compositor behavior, and bounded browser-side comparison value against the landed browser spatial stack.","Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns; sidecar-only value; reasons it should stay subordinate to the landed browser spatial stack.","Do not integrate as a primary browser spatial runtime. Retain only as an optional comparison substrate beneath the landed three.js, react-three-fiber, and xr stack. Any later use should surface bounded lower-level browser-side 3D control or explainer sidecars only if a real gap remains.","Keep subordinate to the landed browser spatial stack and do not form a separate WebGL runtime silo. Use only for optional comparison or bounded sidecar support.","Repurpose here means: optional lower-level browser 3D comparison or explainer substrate only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.","Audit pissang/claygl only as a retained alternative browser 3D comparison substrate for HyperTwist. Inspect renderer, scene, camera, control, picking, compositor, and App3D patterns. Do not reopen it as a primary browser spatial runtime or puzzle-renderer owner. Compare only against the landed three.js, react-three-fiber, and xr stack and report whether any narrower sidecar gap remains.","HT_browser_support_0002","HT_browser_support","pissang/claygl","","","","","","","","BSD-style permissive (see LICENSE)","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.","Use directly as a bounded browser-side dependency after preserving the upstream license text.","Preserve the exact upstream LICENSE text and notices when redistributed or vendored.","Usually unnecessary unless you later replace a narrow low-level utility layer.","medium","license-text-normalization-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser 3D comparison lane subordinate to the landed three.js, react-three-fiber, and xr stack; keep 3R-G deferred unless a real sidecar gap remains."
"pissang/clay-viewer","https://github.com/pissang/clay-viewer","HyperTwist","Merge Bench","Retained alternative browser viewer/editor comparison sidecar","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm the retained browser viewer/editor comparison thesis for pissang/clay-viewer in HyperTwist: what exact narrow sidecar value survives, how it compares against the landed browser viewer and spatial stack, and whether any later sidecar-gap reopening is actually justified.","viewer shell, hotspot manager, environment and lighting config, post-effects, animation preview","Inspect viewer shell, hotspot and animation-preview behavior, environment or lighting presets, compact inspection surfaces, and bounded browser comparison value against google/model-viewer and the landed browser spatial stack.","Inspect hotspot, camera, animation-preview, environment or post-effect preset, and inspection-shell patterns; sidecar-only value; reasons it should stay subordinate to google/model-viewer and the landed browser spatial stack.","Do not integrate as a primary browser viewer or editor runtime. Retain only as an optional comparison sidecar behind the landed google/model-viewer and browser spatial owners. Any later use should surface bounded preview, inspection, or explainer behaviors only if a real gap remains.","Keep subordinate to google/model-viewer and the landed browser spatial stack. Use only for optional comparison or bounded preview or editor sidecars.","Repurpose here means: optional viewer/editor comparison, preview, or inspection sidecar only, not a runtime foundation.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.","Audit pissang/clay-viewer only as a retained alternative browser viewer/editor comparison sidecar for HyperTwist. Inspect hotspot, animation-preview, environment or post-effect preset, and compact inspection-shell behavior. Do not reopen it as a primary browser viewer, editor, gameplay, or runtime owner. Compare only against the landed google/model-viewer and browser spatial stack and report whether any narrower sidecar gap remains.","HT_browser_support_0003","HT_browser_support","pissang/clay-viewer","","","","","","","","BSD-3-Clause","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.","Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rc_browser_comparison_gap_eval_only","Phase 2R-C plus the 2026-05-27 symbolic-XR and alternative-browser hierarchy clarification are closed. Retain only as an optional browser viewer/editor comparison lane subordinate to the landed google/model-viewer and browser spatial stack; keep 3R-G deferred unless a real sidecar gap remains."
"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether KhronosGroup/glTF-Sample-Renderer should remain active in the Browser asset renderer substrate lane and which seams should stay bounded.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; no default widening packet is open."
"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/space-opera should remain active in the Browser asset editor and inspection surface lane and which seams should stay bounded.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/render-fidelity-tools should remain active in the Browser fidelity QA harness lane and which seams should stay bounded.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","Merge Bench","Browser emphasis and post-processing extension","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/model-viewer-effects should remain active in the Browser emphasis and post-processing extension lane and which seams should stay bounded.","effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0007","HT_browser_support","google/model-viewer/packages/model-viewer-effects","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate emphasis and effects package beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","Merge Bench","Browser docs and demo surface","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether google/model-viewer/packages/modelviewer.dev should remain active in the Browser docs and demo surface lane and which seams should stay bounded.","live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0008","HT_browser_support","google/model-viewer/packages/modelviewer.dev","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; no default widening packet is open."
"KhronosGroup/glTF-Sample-Renderer","https://github.com/KhronosGroup/glTF-Sample-Renderer","HyperTwist","Merge Bench","Browser asset renderer substrate","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that KhronosGroup/glTF-Sample-Renderer remains a closed subordinate renderer and reference substrate beneath the landed google/model-viewer asset-QA lane, and record only narrower sidecar-gap reopen criteria, if any.","GltfView, GltfState, resource loader, user camera, renderer core","Inspect the retained renderer and reference substrate slice only in relation to the landed google/model-viewer asset-QA lane, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.","Audit KhronosGroup/glTF-Sample-Renderer only as a closed subordinate renderer and reference substrate row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer asset-QA lane and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0004","HT_browser_support","khronosgroup/gltf-sample-renderer","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.","Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; no default widening packet is open."
"google/model-viewer/packages/space-opera","https://github.com/google/model-viewer/tree/main/packages/space-opera","HyperTwist","Merge Bench","Browser asset editor and inspection surface","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/space-opera remains a closed subordinate browser editor and inspection sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","editor shell, reducer and state structure, hotspot editing, snippet export, inspector surfaces","Inspect the retained browser editor and inspection sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/space-opera only as a closed subordinate browser editor and inspection sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0005","HT_browser_support","google/model-viewer/packages/space-opera","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/render-fidelity-tools","https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools","HyperTwist","Merge Bench","Browser fidelity QA harness","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/render-fidelity-tools remains a closed subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","golden rendering, fidelity workflows, harness configuration, image comparison worker","Inspect the retained fidelity-oracle and regression sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/render-fidelity-tools only as a closed subordinate fidelity-oracle and regression sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0006","HT_browser_support","google/model-viewer/packages/render-fidelity-tools","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.","Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/model-viewer-effects","https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects","HyperTwist","Merge Bench","Browser emphasis and post-processing extension","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/model-viewer-effects remains a closed subordinate emphasis and effects sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","effect composer integration, outline, SSAO, emphasis behavior, custom-element surface","Inspect the retained emphasis and effects sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.","Audit google/model-viewer/packages/model-viewer-effects only as a closed subordinate emphasis and effects sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0007","HT_browser_support","google/model-viewer/packages/model-viewer-effects","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.","Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate emphasis and effects package beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/modelviewer.dev","https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev","HyperTwist","Merge Bench","Browser docs and demo surface","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that google/model-viewer/packages/modelviewer.dev remains a closed subordinate docs and demo infrastructure sidecar beneath the landed google/model-viewer anchor, and record only narrower sidecar-gap reopen criteria, if any.","live docs generation, snippet-to-demo coupling, sidebar and HTML generation","Inspect the retained docs and demo infrastructure sidecar slice only in relation to the landed google/model-viewer anchor, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.","Audit google/model-viewer/packages/modelviewer.dev only as a closed subordinate docs and demo infrastructure sidecar row for HyperTwist. Validate that it remains bounded beneath the landed google/model-viewer anchor and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0008","HT_browser_support","google/model-viewer/packages/modelviewer.dev","","","","","","","","Apache-2.0","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.","Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.","Preserve LICENSE and NOTICE materials where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","notice-file-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_viewer_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 analytics and browser-viewer subordinate-stack clarification are closed. Retain only as the subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; no default widening packet is open."
"google/model-viewer/packages/shared-assets","https://github.com/google/model-viewer/tree/main/packages/shared-assets","HyperTwist","Donor Bench","Boundary-sensitive sample-asset and test-fixture pack","P3","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","repurpose","architecture only","Determine whether google/model-viewer/packages/shared-assets should remain active in the Browser sample-asset and fixture pack lane and which seams should stay bounded.","asset provenance, attribution terms, environment fixtures, sample models, fetch script behavior","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.","Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0009","HT_browser_support","google/model-viewer/packages/shared-assets","","","","","","","","Apache-2.0 container; mixed per-asset terms","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","mixed_or_boundary_sensitive_known","bounded_sidecar_or_selective_reimplementation","The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.","Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.","Preserve container notices and review each selected asset attribution or usage condition separately before shipping.","Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.","high","mixed-asset-whitelist-review","no","","","","","","","","","","","","","v6.3_markdown_backfill","Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.","implemented_live_boundary_sensitive","landed_boundary_sensitive_preserve","Phase 4R-C closed. Preserve as the landed first-party shared-assets allowlist, provenance-boundary, and fixture-refresh lane; keep per-asset shipping allowlists plus review-only and local-only boundaries explicit."
"pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","Merge Bench","Browser React effect-wrapper layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/react-postprocessing should remain active in the Browser React effect-wrapper layer lane and which seams should stay bounded.","React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0010","HT_browser_support","pmndrs/react-postprocessing","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate React wrapper above pmndrs/postprocessing inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","Merge Bench","Browser 3D utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/three-stdlib should remain active in the Browser 3D utility substrate lane and which seams should stay bounded.","controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0011","HT_browser_support","pmndrs/three-stdlib","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate shared utility shelf beneath the landed browser-spatial owner trio; no default widening packet is open."
"pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","Merge Bench","Browser math-helper substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/maath should remain active in the Browser math-helper substrate lane and which seams should stay bounded.","easing and damp functions, random helpers, geometry utilities","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0012","HT_browser_support","pmndrs/maath","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate math-helper substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","Donor Bench","Browser state-management substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/zustand should remain active in the Browser state-management substrate lane and which seams should stay bounded.","vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0013","HT_browser_support","pmndrs/zustand","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser-side state substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","Merge Bench","Browser control-panel and parameter UI layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether pmndrs/leva should remain active in the Browser control-panel and parameter UI layer lane and which seams should stay bounded.","control store, schema parsing, useControls, plugin system, headless mode","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0014","HT_browser_support","pmndrs/leva","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the bounded authoring and debug sidecar inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","Donor Bench","Browser gesture and pointer-input substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether pmndrs/use-gesture should remain active in the Browser gesture and pointer-input substrate lane and which seams should stay bounded.","gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0015","HT_browser_support","pmndrs/use-gesture","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate gesture and pointer-input substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","Merge Bench","Browser layered-motion and explainer sidecar","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/parallax should remain active in the Browser layered-motion and explainer sidecar lane and which seams should stay bounded.","layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0016","HT_browser_support","@react-spring/parallax","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the bounded layered-motion sidecar beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","Merge Bench","Browser frame-loop and scheduling utility","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/rafz should remain active in the Browser frame-loop and scheduling utility lane and which seams should stay bounded.","phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0017","HT_browser_support","@react-spring/rafz","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","Merge Bench","Browser animatable-component substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/animated should remain active in the Browser animatable-component substrate lane and which seams should stay bounded.","host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0018","HT_browser_support","@react-spring/animated","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate animated-props package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","Donor Bench","Browser spring-runtime core","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Determine whether @react-spring/core should remain active in the Browser spring-runtime core lane and which seams should stay bounded.","controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0019","HT_browser_support","@react-spring/core","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate spring-runtime core package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","Merge Bench","Browser motion utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/shared should remain active in the Browser motion utility substrate lane and which seams should stay bounded.","globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0020","HT_browser_support","@react-spring/shared","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","Merge Bench","Browser motion type-contract substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Determine whether @react-spring/types should remain active in the Browser motion type-contract substrate lane and which seams should stay bounded.","shared type contracts, animatable types, interpolation types, utility types","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Capability inventory + salvage targets + donor-tier verdict","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.","HT_browser_support_0021","HT_browser_support","@react-spring/types","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate type-contract package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/react-postprocessing","https://github.com/pmndrs/react-postprocessing","HyperTwist","Merge Bench","Browser React effect-wrapper layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that pmndrs/react-postprocessing remains a closed subordinate React wrapper above the browser post-effect substrate beneath the landed browser-spatial owner trio and the bounded postprocessing substrate, and record only narrower sidecar-gap reopen criteria, if any.","React EffectComposer orchestration, selection model, wrapper ergonomics","Inspect the retained React wrapper above the browser post-effect substrate slice only in relation to the landed browser-spatial owner trio and the bounded postprocessing substrate, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.","Audit pmndrs/react-postprocessing only as a closed subordinate React wrapper above the browser post-effect substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and the bounded postprocessing substrate and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0010","HT_browser_support","pmndrs/react-postprocessing","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.","Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate React wrapper above pmndrs/postprocessing inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/three-stdlib","https://github.com/pmndrs/three-stdlib","HyperTwist","Merge Bench","Browser 3D utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that pmndrs/three-stdlib remains a closed subordinate shared browser utility shelf beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","controls, loaders, WebXR helpers, post-processing helpers, utility exports","Inspect the retained shared browser utility shelf slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.","Audit pmndrs/three-stdlib only as a closed subordinate shared browser utility shelf row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0011","HT_browser_support","pmndrs/three-stdlib","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.","Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate shared utility shelf beneath the landed browser-spatial owner trio; no default widening packet is open."
"pmndrs/maath","https://github.com/pmndrs/maath","HyperTwist","Merge Bench","Browser math-helper substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that pmndrs/maath remains a closed subordinate browser math-helper substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","easing and damp functions, random helpers, geometry utilities","Inspect the retained browser math-helper substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.","Audit pmndrs/maath only as a closed subordinate browser math-helper substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0012","HT_browser_support","pmndrs/maath","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.","Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate math-helper substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/zustand","https://github.com/pmndrs/zustand","HyperTwist","Donor Bench","Browser state-management substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Confirm that pmndrs/zustand remains a closed subordinate browser-side local state substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","vanilla store kernel, React bridge, selector subscriptions, persist and devtools middleware","Inspect the retained browser-side local state substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.","Audit pmndrs/zustand only as a closed subordinate browser-side local state substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0013","HT_browser_support","pmndrs/zustand","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.","Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate browser-side state substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/leva","https://github.com/pmndrs/leva","HyperTwist","Merge Bench","Browser control-panel and parameter UI layer","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that pmndrs/leva remains a closed subordinate authoring and debug control sidecar beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","control store, schema parsing, useControls, plugin system, headless mode","Inspect the retained authoring and debug control sidecar slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.","Audit pmndrs/leva only as a closed subordinate authoring and debug control sidecar row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0014","HT_browser_support","pmndrs/leva","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.","Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the bounded authoring and debug sidecar inside the landed Phase 3R-F stack; no default widening packet is open."
"pmndrs/use-gesture","https://github.com/pmndrs/use-gesture","HyperTwist","Donor Bench","Browser gesture and pointer-input substrate","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Confirm that pmndrs/use-gesture remains a closed subordinate gesture and pointer-input substrate beneath the landed browser-spatial owner trio, and record only narrower sidecar-gap reopen criteria, if any.","gesture controller, drag engine, pointer capture, scroll prevention, React and vanilla bindings","Inspect the retained gesture and pointer-input substrate slice only in relation to the landed browser-spatial owner trio, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.","Audit pmndrs/use-gesture only as a closed subordinate gesture and pointer-input substrate row for HyperTwist. Validate that it remains bounded beneath the landed browser-spatial owner trio and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0015","HT_browser_support","pmndrs/use-gesture","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.","Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate gesture and pointer-input substrate inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/parallax","https://github.com/pmndrs/react-spring/tree/main/packages/parallax","HyperTwist","Merge Bench","Browser layered-motion and explainer sidecar","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that @react-spring/parallax remains a closed subordinate layered-motion and explainer sidecar beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","layered page-space runtime, sticky layers, scroll-driven spring behavior, scrollTo","Inspect the retained layered-motion and explainer sidecar slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.","Audit @react-spring/parallax only as a closed subordinate layered-motion and explainer sidecar row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0016","HT_browser_support","@react-spring/parallax","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.","Use directly as a bounded browser-side dependency for explainer and narrative surfaces.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the bounded layered-motion sidecar beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/rafz","https://github.com/pmndrs/react-spring/tree/main/packages/rafz","HyperTwist","Merge Bench","Browser frame-loop and scheduling utility","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that @react-spring/rafz remains a closed subordinate frame-loop and scheduling package beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","phased queues, timeout scheduling, throttling, demand versus always loop control","Inspect the retained frame-loop and scheduling package slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.","Audit @react-spring/rafz only as a closed subordinate frame-loop and scheduling package row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0017","HT_browser_support","@react-spring/rafz","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.","Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate frame-loop and scheduling package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/animated","https://github.com/pmndrs/react-spring/tree/main/packages/animated","HyperTwist","Merge Bench","Browser animatable-component substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that @react-spring/animated remains a closed subordinate animatable-component package beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","host creation, animated wrapper behavior, dependency observation, native-update fallback","Inspect the retained animatable-component package slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.","Audit @react-spring/animated only as a closed subordinate animatable-component package row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0018","HT_browser_support","@react-spring/animated","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate animated-props package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/core","https://github.com/pmndrs/react-spring/tree/main/packages/core","HyperTwist","Donor Bench","Browser spring-runtime core","P3","","","","","","medium","Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.","repurpose","moderate modification","Confirm that @react-spring/core remains a closed subordinate lower-level spring-runtime core package beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","controller orchestration, SpringValue runtime, useSprings lifecycle, frame advancement","Inspect the retained lower-level spring-runtime core package slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.","Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.","Audit @react-spring/core only as a closed subordinate lower-level spring-runtime core package row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0019","HT_browser_support","@react-spring/core","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.","Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate spring-runtime core package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/shared","https://github.com/pmndrs/react-spring/tree/main/packages/shared","HyperTwist","Merge Bench","Browser motion utility substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that @react-spring/shared remains a closed subordinate lower-level motion-utility and fluid-observer package beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","globals customization, frame loop, interpolation helpers, fluid observer substrate","Inspect the retained lower-level motion-utility and fluid-observer package slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.","Audit @react-spring/shared only as a closed subordinate lower-level motion-utility and fluid-observer package row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0020","HT_browser_support","@react-spring/shared","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.","Use directly as a bounded browser-side dependency beneath higher-level motion layers.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate motion-utility package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."
"@react-spring/types","https://github.com/pmndrs/react-spring/tree/main/packages/types","HyperTwist","Merge Bench","Browser motion type-contract substrate","P4","","","","","","medium","Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.","integrate","moderate modification","Confirm that @react-spring/types remains a closed subordinate type-contract package beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, and record only narrower sidecar-gap reopen criteria, if any.","shared type contracts, animatable types, interpolation types, utility types","Inspect the retained type-contract package slice only in relation to the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack, existing first-party reference-grounded support surfaces, and any unresolved narrower sidecar gaps.","the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.","","Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.","","","","","","","","","","","","Upgrade if source reveals unusually reusable internal seams, clean adapters, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos.","Closed subordinate-boundary note + explicit no-default-widening posture + narrower sidecar-gap reopen criteria.","1) Confirmed source-backed capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended dependency or merge posture; 5) Risks or licensing notes.","Primary: HT_browser_support cluster packet plus the repo-specific Markdown dossier. Optional: neighboring browser/support rows in the same cluster.","@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.","Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.","Audit @react-spring/types only as a closed subordinate type-contract package row for HyperTwist. Validate that it remains bounded beneath the bounded pmndrs/react-spring parent row inside the landed browser-spatial stack and identify narrower sidecar-gap reopen criteria only; do not frame it as a fresh implementation candidate or standalone owner lane.","HT_browser_support_0021","HT_browser_support","@react-spring/types","","","","","","","","MIT","known_from_reference_material","uploaded_reference_docs","","","","","","","","","","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","v6_unified_source_of_truth_pack","","","","permissive_or_noncopyleft_known","direct_incorporation_ok","The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.","Use directly as a bounded browser-side dependency where those contracts are actually needed.","Typically preserve notices, attribution, and license text where required.","Usually unnecessary unless later product-shaping concerns make selective replacement attractive.","high","standard-notice-review","yes","","","","","","","","","","","","","v6.3_markdown_backfill","Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md","selected_not_live_permissive_candidate","phase2rb_browser_support_subordinate_gap_eval_only","Phase 2R-B plus the 2026-05-27 browser-support subordinate-stack clarification are closed. Retain only as the subordinate type-contract package beneath pmndrs/react-spring inside the landed Phase 3R-F stack; no default widening packet is open."

1 repo primary_url project phase_g_bucket stack_layer audit_tier tier_queue_order global_order wave_number portfolio_priority_score execution_priority_score_v3 current_confidence modification_scope_detail_v3 recommended_action_v2 repurposing_potential_v2 audit_goal inspect_emphasis source_code_audit_targets source_inspection_questions integration_realization_detail consolidation_detail repurpose_detail merger_partner_1 merger_type_1 merger_rationale_1 merger_partner_2 merger_type_2 merger_rationale_2 merger_partner_3 merger_type_3 merger_rationale_3 cross_project_transfer_targets cross_project_transfer_rationale reclassify_up_if reclassify_down_if deliverable_expected session_note_template recommended_context_packet phase_g_master_list_rationale phase_g_bucket_reason coding_model_instruction_v3 source_audit_packet_id cluster_tag _repo_norm v5_runtime_project v5_scriptorium_override_status v5_scriptorium_bucket v5_scriptorium_stack_layer v5_scriptorium_current_reality_status v5_scriptorium_supersedes_prior_assessment v5_source_of_truth v6_license_annotation v6_license_annotation_status v6_license_annotation_source v6_supplemental_intake_present v6_supplemental_source_groups v6_supplemental_source_sections v6_supplemental_source_files v6_reference_material_position v6_kali_agent_access_relevance v6_branch_seed_prompt_included v6_branch_seed_scope v6_intake_wave v6_notes v6_source_of_truth project_rank_num tier_rank_num priority_num copyleft_relevance_v6_1 copyleft_strategy_v6_1 copyleft_rationale_v6_1 preferred_boundary_model_v6_1 open_compliance_if_used_as_is_v6_1 reverse_engineer_if_proprietary_core_needed_v6_1 copyleft_strategy_confidence_v6_1 copyleft_manual_review_trigger_v6_1 as_is_incorporation_sensible_v6_1 v6_2_sre_layer v6_2_sre_stratum v6_2_sre_role v6_2_sre_family v6_2_related_kali_package v6_2_related_upstream_repo v6_2_kali_package_suffices_for_tool_execution v6_2_upstream_repo_preferred_for_deep_eval v6_2_index_page_followup_useful v6_2_index_page_followup_reason v6_2_sre_notes v6_2_dnspy_ilspy_relevance v6_3_source_of_truth v6_3_merge_note v6_3_live_state_2026_05_11 v6_3_reset_lane_2026_05_11 v6_3_reset_next_step_2026_05_11
2 HactarCE/Hyperspeedcube https://github.com/HactarCE/Hyperspeedcube HyperTwist Locked Foundation nD / hypercubing simulation substrate P0 20 9203 2.0 160.0 193.0 high This row is already live for its current justified slices. Preserve the landed hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring boundaries, and widen only through owned HyperTwist work. integrate direct Validate the current first-party owner boundaries for HactarCE/Hyperspeedcube and record any narrower owned widening targets that remain after the landed Phase 6R-A/K/L/M/N slice. Landed hyper catalog, notation, replay-log, replay verification, stats-shape, solve-record, and puzzle-DSL owner boundaries as live first-party material. Inspect current first-party owner boundaries, landed packet scope, retained adjacent hyper/runtime families, and unresolved owned widening targets only. Which remaining hyper owner gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-A/K/L/M/N packets? Preserve as the landed first-party hyper owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-A/K/L/M/N packets; do not route work through donor-extraction framing. Treat current first-party HyperTwist code as the owner. Keep MagicTile, Magic120Cell, MagicCube5D, and retained benchmark rows as adjacent families or references, not donor merge targets for the already landed slice. Repurpose here means: ordinary owned enhancement of the landed hyper owner lane, not subsystem harvesting from an external candidate queue. Owned widening only The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing. Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals. Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection. Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture. 1) Which landed hyper owner boundaries are already closed 2) Which narrower owned widening targets, if any, remain 3) Which adjacent retained rows stay reference-only or family-adjacent Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as an already-landed first-party hyper owner lane and route all future work through owned widening. Already-landed hyper owner row for bounded puzzle catalog, notation, replay, stats, and DSL families; no donor thesis remains for the current slice. Audit HactarCE/Hyperspeedcube only as an already-landed permissive owner lane for HyperTwist. Validate current owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate. HT_hyper_engine_0001 HT_hyper_engine hactarce/hyperspeedcube Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs yes hypertwist_and_scriptoriumai HyperTwist HyperTwist & ScriptoriumAI.txt Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward Existing v5 row reaffirmed or widened by v6 supplemental intake. v6_unified_source_of_truth_pack 2 1 160.0 permissive_or_noncopyleft_known direct_incorporation_ok This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness. Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing. Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed. Usually unnecessary unless you later decide the existing implementation is too constraining architecturally. high strategic-or-implemented-component yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_permissive landed_permissive_preserve Later Phase 6R-A/K/L/M/N preserve sequence closed. Preserve as the landed first-party hyper puzzle catalog, notation, replay-log serialization, replay verification, stats-shape, solve-record, and puzzle-DSL authoring lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, not from the old candidate queue wording.
3 kkoomen/qbr https://github.com/kkoomen/qbr HyperTwist Locked Foundation Live cube-recognition substrate P0 21 9204 4.0 158.0 191.0 high This row is already live for its current justified slices. Preserve the landed recognition calibration, ordered face-observation, and webcam-shell boundaries, and widen only through owned HyperTwist work while keeping deferred multilingual and broader solve-shell ownership explicit. integrate direct Validate the current first-party owner boundaries for kkoomen/qbr and record any narrower owned widening targets that remain after the landed Phase 6R-B/O slice. Landed recognition calibration, ordered face-observation, webcam shell, and adjacent deferred remainder boundaries as live first-party material. Inspect current first-party recognition owner boundaries, landed packet scope, retained adjacent recognition rows, and unresolved owned widening targets only. Which remaining recognition or webcam-shell gaps, if any, are not already covered by the landed HyperTwist code and the bounded Phase 6R-B/O packets? Preserve as the landed first-party recognition calibration and webcam-shell owner lane. Start any future widening from owned HyperTwist surfaces, FEATURE_REGISTRY, ROADMAP, REPO_LICENSE_TRACKING, and the landed Phase 6R-B/O packets; do not route work through donor-extraction framing. Treat current first-party HyperTwist code as the owner. Keep rubix-cube-solver, the retained recognition-comparison adjunct rows, and the multilingual guidance remainder as adjacent retained or deferred families, not donor merge targets for the already landed slice. Repurpose here means: ordinary owned enhancement of the landed recognition and webcam-shell owner lane, not external donor harvesting. Owned widening only The row is already live inside HyperTwist. Further work should start from first-party owner surfaces, feature registry, roadmap, license tracking, and landed packet authority rather than donor-transfer or merger-thesis framing. Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals. Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection. Owner-boundary note + owned widening criteria + explicit no-donor-thesis posture. 1) Which landed recognition and webcam-shell owner boundaries are already closed 2) Which narrower owned widening targets, if any, remain 3) Which adjacent retained or deferred rows stay outside the landed slice Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. Keep in canon as an already-landed first-party recognition owner lane and route all future work through owned widening. Already-landed recognition owner row for bounded calibration, ordered observation, and webcam-shell families; no donor thesis remains for the current slice. Audit kkoomen/qbr only as an already-landed permissive owner lane for HyperTwist. Validate current recognition and webcam-shell owner boundaries and identify owned widening targets only; do not frame it as a donor-merge candidate. HT_cube_vision_0001 HT_cube_vision kkoomen/qbr Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 1 158.0 permissive_or_noncopyleft_known direct_incorporation_ok This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness. Already landed: start from first-party owner surfaces and landed packet authority, not donor-transfer framing. Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed. Usually unnecessary unless you later decide the existing implementation is too constraining architecturally. high strategic-or-implemented-component yes v6.3_final_source_of_truth Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff. implemented_live_permissive landed_permissive_preserve Later Phase 6R-B/O preserve sequence closed for the currently justified slice. Preserve as the landed first-party recognition calibration, ordered face-observation, and webcam-shell lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while keeping multilingual/font redistribution and broader solve-shell ownership deferred.
4 vivaansinghvi07/rubix-cube-solver https://github.com/vivaansinghvi07/rubix-cube-solver HyperTwist Locked Parallel Foundation Vision / reconstruction donor layer P0 22 9205 8.0 158.0 191.0 high Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces. integrate direct Validate whether vivaansinghvi07/rubix-cube-solver truly deserves its current foundation-tier role for HyperTwist; extract the irreducible core abstractions, extension points, and transplantable subsystems. image pipeline, detection heuristics/models, cube-state reconstruction, calibration, temporal smoothing, replay model, solver handoff, AR/overlay hooks Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations. Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange. Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube. Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist. kkoomen/qbr foundation + perception donor Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization. cubing/cubing.js state/render backend Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top. cross-project transfer candidate future merger Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell. VectorShell | ScriptoriumAI VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine. Keep current tier unless source audit reveals architectural shallowness, hard-coded assumptions, missing extension points, or brittle internals. Downgrade if core capabilities are thinner than claimed, architecture is too brittle or narrow, maintenance reality is poor, or the differentiating thesis collapses under code inspection. Architecture note + salvage map + integration recipe + reclassification verdict 1) Confirmed visible capabilities 2) Hidden capabilities found only in source 3) Best salvageable modules/files/packages 4) Integration path into target project 5) Repurpose path outside the original thesis 6) Best merge partners and exact coupling seam 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo; Relevant project-locked board sheet. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration. vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths. Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr. Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell. HT_cube_vision_0002 HT_cube_vision vivaansinghvi07/rubix-cube-solver Original global P0-P3 source audit retained MIT known_from_reference_material uploaded_reference_docs no Supplemental intake references are advisory only; v6 adjudication remains the source of truth. Usually indirect yes v6 unified all-project source-of-truth pack v5_carry_forward v6_unified_source_of_truth_pack 2 1 158.0 permissive_or_noncopyleft_known direct_incorporation_ok This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness. Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires. Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed. Usually unnecessary unless you later decide the existing implementation is too constraining architecturally. high strategic-or-implemented-component yes v6.3_final_source_of_truth Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25. implemented_live_permissive landed_permissive_preserve Later Phase 6R-C/P/Q preserve sequence closed for the currently justified slice. Preserve as the landed first-party committed-face reconstruction, browser/webcam shell, and bounded solve-explanation/recommendation lane; start future widening from ROADMAP.md, FEATURE_REGISTRY.md, REPO_LICENSE_TRACKING.md, and the repo-specific landed Phase 6R packets, while broad solver-backend ownership and bundled twistysim.min.js redistribution stay deferred.
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258