feat(pbs): add linked collections and bidirectional snapshots

Implement SDK linked<T> with forward and reverse Cursor snapshots, trusted compiler integration, and neutral FIELDS_PUBLISH producer support. Pin the tested runtime revision and include specs, editor and installed knowledge coverage, conformance fixtures, and DSC-0091 lessons and evidence.
This commit is contained in:
2026-10-23 10:28:44 +01:00
parent c410e35001
commit 77aada6259
38 changed files with 3040 additions and 57 deletions
+30
View File
@@ -264,3 +264,33 @@ Evidence prints compiler/provider source hashes, exact provider revision and dir
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.
## SDK Linked and multi-object publication
```sh
./gradlew :prometeu-compiler:prometeu-build-pipeline:test :prometeu-architecture-tests:test :prometeu-app:installedKnowledgeTest
python3 tools/pbx-conformance/run.py --runtime ../runtime --linked-only
```
The full harness requires this corpus too. Ordinary and optimized source programs
exercise the complete Linked API, both snapshot orders, empty/single/multiple
states, reciprocal links, identities and full native/tuple/contract/Fn groups,
logical and long bounds, contextual construction and source/named evaluation.
Neutral common-IR fixtures execute FIELDS_PUBLISH without PBS or collection types.
Ten explicit mutation boundaries qualify every mutation and both captures. The
harness lowers resource ceilings around measured setup/success peaks and compares
all prior Linked roots, optional-link carriers, nodes and complete groups after
each refusal. Node allocation, optional removed-value preparation, snapshot-node
allocation and frame/operand preparation must all produce observed refusals.
Publication itself uses no allocation or scratch; provider tests prove it succeeds
at already exhausted allocation ceilings and rejects late invalid groups before
any write, including for null destinations and aliased targets.
Normal GC safepoints qualify removal/clear without snapshots (1,200 → 1,197 → 0
nodes and payloads), and snapshot traversal (1,200 → 1 → 1 → 0). Fixtures introduce
ordinary garbage pressure so every asserted round performs an actual collection.
Snapshots retain no editable Linked nodes. Source imports/reexports and a separately
compiled installed-JAR example must execute; its forward/reverse traversals retain
final values 22/20 after later replacement and clear. Missing fixtures are failures.