feat(pbs): align typed values and Pad input facade
Test / Build occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/pr-master There was a failure building this commit
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit

This commit is contained in:
2026-10-15 15:48:50 +01:00
parent 603ed01227
commit 13c0ababbb
48 changed files with 1251 additions and 354 deletions
+27 -3
View File
@@ -6,7 +6,7 @@ it does not implement a Java approximation of runtime admission.
From the Studio root:
```sh
./gradlew :prometeu-compiler:prometeu-build-pipeline:test --tests '*LinkedRegistryTest' --tests '*PbxRegistryConformanceTest' --tests '*TypedCommonPipelineTest' --tests '*RuntimeCatalogPipelineTest'
./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
```
@@ -43,8 +43,9 @@ 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.
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
@@ -62,3 +63,26 @@ 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.