feat(pbs): add mutable lists and stable snapshot cursors

Implement SDK list<T> and Cursor<T> with trusted compiler bindings and generic storage publication across IR and PBX. Pin the runtime provider and include specs, conformance coverage, installed examples, and DSC-0090 lessons.
This commit is contained in:
2026-10-23 00:46:39 +01:00
parent 76a8b074e8
commit c410e35001
46 changed files with 2683 additions and 165 deletions
+40
View File
@@ -224,3 +224,43 @@ python3 tools/pbx-conformance/run.py --runtime ../runtime --generic-contracts-on
The full harness also requires these fixtures. The driver uses an external
runtime checkout without editing its sources or changing PBX, ISA or quotas.
## SDK List, shared Cursor and generic storage
Generate the source corpus and the language-neutral storage fixtures, then run:
```sh
./gradlew :prometeu-compiler:prometeu-build-pipeline:test :prometeu-architecture-tests:test :prometeu-app:installedKnowledgeTest
python3 tools/pbx-conformance/run.py --runtime ../runtime --list-cursor-only
```
The full harness also requires this corpus. Missing ordinary, optimized, quota,
GC, import/reexport or installed-JAR fixtures fail explicitly. Two synthetic
common-IR programs execute INDEX_GUARD, ARRAY_CHECK_LENGTH, ARRAY_COPY and
STORAGE_PUBLISH through ordinary and optimized producer paths without PBS types.
List source cases cover every mutator, exact growth, logical versus physical
bounds, int/long arguments (including named application), holes, aliases,
vec2/pixel/tuple/Fn/contract/reference groups and every state of a Cursor that remains on its last node.
An independent producer distinguishes some(none) from an empty Cursor.
Four source-generated mutation fixtures expose explicit before/completed markers.
The harness lowers GuestBytes, HandleSlots, AuxiliaryBytes and TemporaryBytes from
measured setup/success peaks. After each refused attempt it independently observes
all List fields and complete backing groups, including reference generations and
presence tags. Coverage gates require refusals in no-growth publication scratch,
removeAt optional return allocation, candidate allocation, node construction and
operand/frame preparation. Read-only resource diagnostics use non-owning storage
observations outside guest execution; no observation introduces a GC root or write.
The controlled safepoint fixture expects 1,200 nodes/objects initially, one after
traversal, one after repeated next on the final node, and zero after releasing the
Cursor. It also requires no live source/snapshot array. Shared payload fields stay
observable; prefix roots and the final payload obey normal reachability and GC.
The installed fixture is compiled by the isolated installDist JVM using the actual
packaged spec/example/SDK, then loaded and executed by this production VM harness.
Evidence prints compiler/provider source hashes, exact provider revision and dirty
state, toolchain, platform/profile, capabilities, every default VM ceiling and each
explicitly lowered refusal limit. Development runs against a dirty provider are
identified as such; final catalog verification requires its clean selected commit.