feat(registry): checkpoint PLN-0176 foundations and validated partial integrations

This commit is contained in:
2026-10-07 17:49:46 +01:00
parent 01fab56cc6
commit 126a9e50e7
63 changed files with 8499 additions and 1462 deletions
+21
View File
@@ -143,3 +143,24 @@ For exact immediates and stack effects, see `CoreOpCode::spec()` which is the si
- Verification notes:
- The bytecode verifier treats `FRAME_SYNC` as a normal instruction with no stack effect and no control-flow targets. It is permitted before `RET`, between basic blocks, and as the last instruction of a function. Jumps targeting the function end (`pc == end`) remain valid under the end-exclusive rule.
## Registry instruction encodings
The [Registry contract](../specs/runtime/02c-program-registry-and-pbx-v1.md#dynamic-and-reference-instructions)
defines opcodes 0x0090–0x0096. Tooling recognizes their u32 TypeId immediates:
```text
DYN_PACK 0
DYN_UNPACK 0
DYN_CAN_UNPACK 0
REF_IS_EXACT source=4, target=5
REF_IMPLEMENTS source=4, target=6
REF_TO_TRAIT source=4, target=6
REF_CAST source=6, target=4
```
Dynamic instructions occupy six bytes; reference instructions occupy ten bytes.
Static opcode metadata must represent Registry-dependent slot effects as unresolved,
never as zero. Resolve the semantic widths and immediate categories from the validated
Registry. Encoding/decoding support alone does not authorize execution: a slot-only
image/verifier must reject these instructions until typed-image integration is present.