feat xr v2 workspace runtime hardening - #711
Draft
huijoohwee wants to merge 18 commits into
Draft
Conversation
![knowgrph-lifecycle[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Align the TypeScript type with the existing runtime validation so the XR behavior graph contract compiles cleanly in integration.
Keep the canvas app entry chunk below the hygiene budget by deferring the main Canvas route into its own lazy bundle. This preserves the XR v2 workspace-seed smoke path while avoiding the integration gate bundle regression.
…k-pro.local/xr-v2-workspace-runtime-release
Prefer the synchronous Three renderer compile path in CI so the XR v2 workspace browser smoke does not stall on headless runners, and cover the selection logic with focused tests.
Expose the CI flag to the browser renderer selection path and stop the mounted authoring evidence from latching invalid before the particle buffer has produced an observed frame. This keeps the workspace-seed smoke on the PR candidate path aligned with the review-ready proof instead of timing out on stale deterministic evidence.
Poll the XR v2 workspace-seed readiness attributes directly so the browser smoke converges reliably on fresh CI starts and reports the last observed readiness state when it fails.
Force a fresh synchronize event on PR #706 so GitHub Actions creates a new Integration check suite for the current head revision.
Create a fresh user-pushed commit for PR #706 so GitHub Actions schedules Integration on the current branch head instead of suppressing the automation-generated synchronize event.
Create a unique head commit for PR #709 so GitHub Actions schedules Integration on the replacement PR instead of reusing the prior suppressed commit state.
Create a user-authored head commit for PR #709 so GitHub Actions sees a normal branch update instead of another bot-authored synchronize event.
5 tasks
Create a distinct user-authored head commit for PR #711 so GitHub schedules Integration against a new commit SHA instead of reusing the prior queued check-suite state.
Create an explicit human-authored head commit for PR #711 so GitHub Actions evaluates the replacement PR through the normal pull_request scheduling path.
Owner
Author
|
Blocked on GitHub Actions scheduling, not on code mergeability. Latest tested head: Observed on this PR:
We already retried with:
Support-ready evidence has been updated locally in: |
Owner
Author
|
Correction: previous comment was malformed by shell interpolation. Use this as the accurate blocker note. Blocked on GitHub Actions scheduling, not on code mergeability. Latest tested head SHA: d5f36fe Observed on this PR:
Retries already attempted:
Updated local evidence:
|
huijoohwee
marked this pull request as draft
August 6, 2026 10:48
huijoohwee
marked this pull request as ready for review
August 6, 2026 10:48
Owner
Author
|
Release coordination request — exact scope observed 2026-08-06T17:18Z. This PR remains OPEN/non-draft at head d5f36fe and still changes This release coordinator will not close, rewrite, or impersonate the Katrina-owned 66-path lane: PR #712 overlaps only 57 paths and does not prove complete supersession. Please perform one owner action: remove/release only The needed successor will be a fresh registered, leased, cloud-admitted one-path pin lane after the final ACOS protected SHA stabilizes. No deployment is requested by this note. |
Collaborator
|
Parking this conflicted XR lane as a draft under operator authorization so its branch, commits, and registered worktree remain preserved while the release-path lane proceeds. No code is being merged, closed, deleted, or rewritten. |
katrinateh-dotcom
marked this pull request as draft
August 10, 2026 14:23
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
2 participants
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.
Summary
mainstorage-sync durability change before release verificationTest plan