feat(studio): improve compiler reliability and AI diagnostics
Preserve structured diagnostics, source attribution, phase outcomes and revision context through compiler, Studio, LSP, MCP and JavaFX. Add project service discovery and resilient VS Code reconnection. Correct all eight reproduced PBS production failures in expression context, sibling executable bindings and nominal owner identity. Consolidate specs, lessons, immutable baseline evidence and the maintained source-to-guest qualification runner. Validation: required Gradle gate recorded 724 tests, with 711 passed and 13 skipped. Full corpus passed 168 compilation observations and 108 guest runs (104 successes and four deliberate faults); supplemental controls passed 42 compilations and 16 guest runs. TypeScript compilation, two Node discovery tests and discussion validation passed.
This commit is contained in:
@@ -148,6 +148,26 @@ For v1 backend/runtime diagnostics and conformance support, emitted artifacts mu
|
||||
|
||||
This minimum does not require one universal source-map format.
|
||||
|
||||
### 7.1 Compilation attribution before artifact emission
|
||||
|
||||
Compiler failures before PBX emission MUST use attribution from the program being
|
||||
checked. The IRVM function plan associates each instruction with its emission
|
||||
operation and optional source origin. Lowering and optimization MUST preserve
|
||||
that association, including recorded generated provenance, when expanding,
|
||||
removing or rewriting instructions.
|
||||
|
||||
An IRVM verification PC is a zero-based byte offset within a function in the
|
||||
checked program. It MUST be identified as `pcSpace=irvm-function`, `pcUnit=byte`,
|
||||
and accompanied by the reporting stage and validation point. It is not an emitted
|
||||
PBX offset or executed runtime PC. A validation after an optimization pass uses
|
||||
that pass's output, including its remapped instruction boundaries and origins.
|
||||
|
||||
These in-memory diagnostics do not change PBX serialization or the minimum debug
|
||||
hooks above. A missing instruction origin MUST remain explicit; neither a nearby
|
||||
instruction nor a function's first line supplies an exact fallback. The complete
|
||||
diagnostic and public-failure contract is defined in
|
||||
[Compiler 19, sections 12–13](19.%20Verification%20and%20Safety%20Checks%20Specification.md).
|
||||
|
||||
## 8. Deterministic Emitter Rejection
|
||||
|
||||
Emitter-side rejection must be deterministic for malformed or inconsistent artifact candidates, including at minimum:
|
||||
|
||||
Reference in New Issue
Block a user