Gamelayer

[3a1b2c3]

Serve an application's own browser UI from the v2 runtime

Adds IWebUiProvider to api_v2. An application implementing it returns a web
root, a scene, a first frame, and the result of one page submission, and the v2
WebRTC server gains five routes for that run:

Route	Serves
GET /request_session	index.html from the application's web root
GET /<file>	any other file in that web root, resolved inside it only
GET /api/session/initial_scene	the application's scene, verbatim as JSON
GET /api/session/first_frame	the session's first frame, or 404 when there is none
POST /api/session/input	one page submission, answered with the resulting scene

Serving stays generic: it copies the scene into a JSON response and hands the
decoded request body back without inspecting either. JSON, form and multipart
bodies arrive as one flat mapping, uploads as bytes, and a ValueError becomes
a 400. Applications without the protocol are untouched — every route 404s, and
the wiring is a single isinstance check.

Lingbot is the first implementation, restoring its scene presets, live text
events and HUD on v2. Its page takes ?manual (skip auto-connect), ?preset=
(open on a scene) and ?director (environment events instead of player ones).

63 CPU tests (20 serving, 43 scene rules)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Summary

The PR adds an application-owned browser UI protocol to runtime-v2 and implements it for Lingbot.

• Adds generic WebRTC routes for application assets, initial scenes, first frames, and session input.
• Adds Lingbot scene presets, uploads, text events, HUD behavior, documentation, and CPU tests.
• Wires IWebUiProvider applications into the WebRTC client-window lifecycle.

Confidence Score: 3/5

The PR does not appear safe to merge because installed Lingbot packages still lack required UI files and concurrent scene access remains unsynchronized.

Installed-wheel launches still resolve the browser page from package files that are not declared as package data, while HTTP handlers continue mutating shared scene state without synchronizing concurrent readers and model activity.

Files Needing Attention: integrations_v2/lingbot/pyproject.toml and integrations_v2/lingbot/apps/cam2v/adapter.py

Important Files Changed

Filename	Overview
flashdreams/flashdreams/runtime_v2/serving/webrtc_server.py	Adds generic application UI routing, asset containment, request decoding, and scene/frame endpoints.
flashdreams/flashdreams/api_v2/web_ui.py	Defines the runtime-checkable application protocol for browser UI assets and scene operations.
integrations_v2/lingbot/apps/cam2v/adapter.py	Implements Lingbot’s web UI provider and live scene updates, while the previously reported shared-state synchronization defect remains.
integrations_v2/lingbot/apps/cam2v/scene.py	Restores scene presets, prompt and event updates, image selection, and serialized page state.
integrations_v2/lingbot/pyproject.toml	Adds package-data declarations, but the previously reported required UI asset omissions remain.
flashdreams/test_v2/test_webrtc_web_ui.py	Exercises application route registration, request decoding, asset containment, first-frame behavior, and errors.

Sequence Diagram

sequenceDiagram
    participant B as Browser
    participant S as WebRTC server
    participant A as IWebUiProvider
    participant M as Model/UI loops
    B->>S: GET /request_session
    S-->>B: Application index.html
    B->>S: GET /api/session/initial_scene
    S->>A: initial_scene()
    A-->>S: Scene mapping
    S-->>B: JSON scene
    B->>S: POST /api/session/input
    S->>A: apply_session_input(payload)
    A->>M: Queue prompt or replacement session
    A-->>S: Updated scene
    S-->>B: JSON scene

Loading

_{Reviews (2): Last reviewed commit: "Merge branch 'NVIDIA:main' into gamelaye..." | Re-trigger Greptile}

[greptile-apps]

Package omits required UI assets

When Lingbot runs from an installed wheel, this package-data list excludes index.html, request_session.js, and request_session.css, causing /request_session or its required assets to return 404 instead of loading the application UI.

Knowledge Base Used: Packaging and launch configuration

[greptile-apps]

Scene mutations are not synchronized

If scene requests overlap each other or model generation, HTTP workers mutate the shared SceneState while other threads read it, causing responses and rollout conditioning to combine inconsistent prompt, event, or image state.

Knowledge Base Used:

• Runtime-v2 application execution
• Cam2V application