verify real MCP runtime and DEV framebuffer parity
This commit is contained in:
@@ -425,8 +425,8 @@ compression/padding. Logical and render frame counters are independent.
|
||||
|
||||
The adapter MUST NOT invent a frame when none exists or substitute another
|
||||
session's image. The same neutral capture feeds DEV and MCP. Real runtime
|
||||
production/cross-language equality remain phase 4 gates; encoding test pixels in
|
||||
contract tests does not satisfy that integration requirement.
|
||||
production/cross-language equality is verified by the phase 4 desktop integration
|
||||
gate below; encoding test pixels in contract tests alone does not satisfy it.
|
||||
|
||||
## 7. Conformance and Delivery Boundary
|
||||
|
||||
@@ -448,7 +448,25 @@ build/runtime ports; a separate HTTP test uses the real compiler/packer. This
|
||||
completes MCP-phase conformance. The packaged-runtime gate additionally exercises
|
||||
actual app composition, project LSP, compiler/packer, saved edits, explicit
|
||||
reset/reboot, build identity invalidation and corrective loops after compile
|
||||
errors/guest faults. Full HTTP/visual and external-agent acceptance remain
|
||||
subsequent integration gates, not implied by this service-composition gate.
|
||||
API/Core and
|
||||
JavaFX MUST NOT import MCP/HTTP implementations; architecture tests enforce it.
|
||||
errors/guest faults.
|
||||
|
||||
Step 24 adds `headlessMcpDesktopTest`: a real HTTP client drives the composed app,
|
||||
installed compiler/packer/LSP and packaged Rust runtime, while the actual JavaFX
|
||||
DEV view observes the shared session. An independent test-only JSONL client runs
|
||||
the same saved cartridge and input timeline in another real process, without the
|
||||
Studio process adapter or capture DTOs. Raw PNG bytes and each capture metadata
|
||||
field match MCP; all decoded framebuffer pixels and the visible identity/stale
|
||||
labels match DEV. State/fault and deterministic reset/fresh-session repetitions
|
||||
are also checked. Rebuilding changes pixels/build identity and visibly marks the
|
||||
old capture stale. Images remain in memory; window screenshots are not evidence.
|
||||
|
||||
The fixture uses supported project-source LSP definition/symbol navigation and
|
||||
indexed SDK reads. A probe of the installed SDK's `Input.pad()` definition returns
|
||||
an empty result with the current language service; the gate does not claim SDK
|
||||
symbol navigation where no location is returned. This is a language tooling
|
||||
limitation, not a headless or MCP execution fallback.
|
||||
|
||||
The automated client is not an external coding agent. Adversarial integrated
|
||||
lifecycle, real-agent compatibility and final packaging acceptance remain later
|
||||
gates. API/Core and JavaFX MUST NOT import MCP/HTTP implementations; architecture
|
||||
tests enforce it.
|
||||
|
||||
Reference in New Issue
Block a user