Repository navigation
Conversation
Contributor
Author
Executed dependency-backed verificationThe focused Integration perception workflow passed on implementation commit The actual The full repository CI remains queued. This does not prove a complete navigation encounter, GPU/native/Android behavior or an improvement over direct gameplay code. Those acceptance gates remain open and this PR stays draft. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementation
Commit
a899a82ea304b6eacdd074ff2318233fc09feaa0adds actual Yuka Vision integration, caller-owned occlusion queries, immutable last-seen memory, simulation-time expiry and executable regression tests.Code:
examples/integrations/perception/. This is editable, opt-in game source. Yuka answers the view cone, the existing world answers occlusion, and existing navigation/physics remain the only movement owner. No EntityManager, second loop or mandatory core AI dependency is introduced.Verified repair — 2026-09-26
Commit
38dde724ddd74e7737efb78de5c0dc3cd4cde883fixes a real validation bug: sparse position arrays bypassed Array.some and could corrupt last-seen memory or advance its clock. All three coordinate slots are now validated before state mutation. Two added regressions failed on the old validator and pass after the fix. They cover missing coordinates, sparse arrays, null and undefined. Package lint repairs preserve existing rules; the concurrent develop merge is retained.Executed: complete
npm testpasses the pinned TypeScript 5.9.3 strict build, 12 policy contracts and 3 real Yuka/Three integration tests: 15 passed, 0 failed. Biome 1.9.4 andgit diff --checkpass. Dedicated Integration perception rerun is green: https://github.com/ThreeNativeHQ/threenative/actions/runs/36214585234 . This supersedes the earlier local dependency limitation.Remaining: playable navigation/replay integration, direct-baseline comparison, browser/native/Android traces, complete repository checks and independent review. Keep draft/experimental; no unexecuted platform requirement is marked complete.
Run
npm install --ignore-scripts && npm testin the example directory. PRD:docs/PRDs/threejs-integrations/PRD-threejs-yuka-perception.md.Checklist — mirrors PRD
Phase 1 — baseline and dependency admission
Phase 2 — optional perception example
Three real Yuka/Three integration tests now pass, including occlusion, authored-axis transforms and unchanged movement ownership.
Phase 3 — playable platform proof
Phase 4 — ship as game source
Acceptance criteria