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' --tests '*RuntimeCatalogPipelineTest' --tests '*PbsRuntimeAlignmentTest'
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.
The original registry/catalog fixtures qualify common backend production. The PBS fixtures below additionally qualify source lowering; this harness does not claim installed-runtime deployment or memcard persistence.
Runtime catalog consumer fixtures
The catalog corpus adds common-IR Random calls with an aliased handle, a discarded
first result, mixed next/nextf/range calls and a subsequent next. The VM checks the
independent seed-42 handoff vector and identical charged work before/after
optimization. Constants are compared slot-by-slot against runtime materialization,
including exact Float bits and both slots of vec2.zero. Pool deduplication may
share a value but cannot omit a group component.
A known zero-argument touch query loads and traps TRAP_UNAVAILABLE without a
hardware context. A removed endpoint ID is rejected even after an unreachable
HALT. color.html_rgba executes with a String value and rejects a proven null
at load time, matching the runtime verifier's stricter rule despite the
dispatcher's nullable String carrier. These are distinct outcomes. Run the separate provider-export check with
python3 tools/runtime-catalog/verify.py --runtime ../runtime to compare the
selected source revision, imported CSV bytes and exporter output as well.
PBS source and input qualification
PbsRuntimeAlignmentTest compiles actual SDK declarations and source programs
through the PBS frontend, production common IR, typed Registry and PBX writer.
Its 114 fixtures execute on the selected runtime: all 48 Pad combinations with
both literal Button arguments and enum locals passed through a typed function,
six Touch queries, numeric boundaries/conversions/faults, builtin groups,
String, fixed multiple returns and named application with observable Y,X effects.
The controlled input platform asserts the exact button/coordinate reader and one read per public query. Each query is also executed without a platform to prove TRAP_UNAVAILABLE. The loaded PBS registries are checked for the defaults of all eight existing value types, including null String, positive Float zero and complete vec2/pixel groups. No source constructors or new collection API are introduced to test storage defaults.
The harness requires the complete fixture count. It must not pass by skipping missing PBS fixtures. Integer arithmetic wrapping is distinct from checked Int64-to-Int32 narrowing and Float numeric-range faults. The full installed knowledge gate remains separate and mandatory for SDK resource/producer integration.