feat(diagnostics): preserve Registry and resource fault context for PLN-0176 step 28
This commit is contained in:
@@ -94,6 +94,19 @@ exact round-trippable string (including non-finite values). Faults expose kind,
|
||||
pc, summary and structural trap code/opcode/message/source span or init-error code.
|
||||
No client must parse a summary to distinguish trap, panic or initialization failure.
|
||||
|
||||
Resource traps include a nullable `trap.resource` object with `resource`, `reason`,
|
||||
`requested` and `limit`; resource and reason are enumerated machine values.
|
||||
`initError` is discriminated by `code`: `registry_load_failed` includes `load`,
|
||||
`runtime_resource_limit` includes `resource`, `entrypoint_arguments_invalid`
|
||||
includes `entry`, and `loader_patch_failed` includes `binding`. Other initialization
|
||||
codes carry only their code and human message. `load.code` uses the stable
|
||||
`LOAD_*` tag and retains typed reason, section/offset, record/member, ID domain,
|
||||
referenced ID, function/PC and quota context, with null for unavailable fields.
|
||||
Binding context preserves canonical native identity, version, capabilities or
|
||||
declared/expected ABI counts as applicable. A load-relative PC remains nested
|
||||
inside its diagnostic; initialization failure does not invent a runtime PC.
|
||||
The published response schema rejects unknown fields and invalid contexts.
|
||||
|
||||
## Ordering, cancellation and lifecycle
|
||||
|
||||
Only one host operation is admitted at a time. Conflicting work, including state
|
||||
|
||||
Reference in New Issue
Block a user