Files
prometeu-studio/tools/pbx-conformance

Studio PBX producer conformance

Owner: compiler/general. This harness uses the production runtime loader and VM; it does not implement a Java approximation of runtime admission.

From the Studio root:

./gradlew :prometeu-compiler:prometeu-build-pipeline:test --tests '*LinkedRegistryTest' --tests '*PbxRegistryConformanceTest' --tests '*TypedCommonPipelineTest'
python3 tools/pbx-conformance/run.py --runtime ../runtime

The Java tests generate PBX in the build-pipeline module's build/registry-conformance. run.py creates a temporary Cargo project, copies the runtime lockfile and references its bytecode/hal/vm/system crates by path. It never modifies the runtime checkout. Add --online for an uncached machine; by default Cargo uses only cached dependencies. Java 25, Rust and the runtime checkout's dependencies are required.

The output identifies runtime revision, OS/architecture and load configuration. Positive fixtures distinguish loading from execution. The vec2 signature fixture is deliberately load-only because its entry requires arguments. Native binding uses SYSTEM for the positive case and NONE for missing-capability rejection; all other cases use NONE. Resource tests explicitly lower default limits.

Negative fixtures mutate Java-produced bytes independently of the writer to exercise malformed input that the writer correctly refuses to construct. Initialization JSON comes from prometeu_system::CrashReport, and is checked against the runtime's published headless schema. Saved JSON files remain under the generated fixture directory. Studio process tests replay selected observed payloads from prometeu-app/src/test/resources/runtime and assert unchanged MCP projection, including null executed PC and nested verifier context.

Known upstream schema defect

At runtime f7d7c167531bb662a1af9d73fc326bb476bf8aa7, the LoadReason Rust enum includes LifecycleRole, LifecycleSignature, DuplicateLifecycleRole and NonFiniteValue, absent from the published JSON schema enum. This corpus observes LifecycleRole and NonFiniteValue. The harness prints an explicit UPSTREAM SCHEMA GAP for those two reasons and verifies that adding exactly the missing enum value makes the original payload valid. It never alters the payload or reports those cases as conforming to the unmodified schema. Any other schema failure remains fatal. Track the runtime correction in AGD75; remove the exception once the schema is corrected.

This corpus qualifies common backend production, not PBS lowering, lifecycle selection, memcard persistence or installed-runtime deployment.