feat(studio): improve compiler reliability and AI diagnostics
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/pr-master There was a failure building this commit

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:
2026-11-10 12:36:25 +00:00
parent 38f201a9c9
commit ea1cc26fe3
1216 changed files with 168017 additions and 354 deletions
@@ -873,3 +873,13 @@ Its requirements apply in addition to this chapter; pause/resume remain independ
Factory-only admission uses trusted canonical declaration origin, never visible spelling or slot count. Reject external positional/named construction and forged metadata; omit prohibited constructors from completion/signature help and expose public factories. Result error identity is nominal through imports and aliases; a result-effect function cannot be converted to plain Fn.
See [Core Sprite and Animation](27.%20Core%20Sprite%20and%20Animation%20Specification.md) for the complete API, ranges, state table and conformance obligations.
## Production expression and module conformance
Expected result types constrain the expression node that owns the expectation. A returned bool comparison MUST NOT force an int-returning operand call to return bool. Operand inference/resolution MUST retain its own type and use the opposite operand's known type when contextual disambiguation is required. This does not remove legitimate expected-return overload selection. Receiver/argument evaluation count and order remain those of [Dynamic Semantics](9.%20Dynamic%20Semantics%20Specification.md).
Sibling-file callable/global/service surfaces MUST use declaration/signature-level admission from mod.barrel. Both mod and pub entries admit same-module access; omission leaves the declaration file-private. Publishing one overload MUST NOT publish every overload sharing its name. Caller-visible names and definition-scoped private dependencies are different surfaces. The existing [syntax visibility contract](3.%20Core%20Syntax%20Specification.md) and [resolution contract](5.%20Manifest%2C%20Stdlib%2C%20and%20SDK%20Resolution%20Specification.md) remain authoritative.
Nominal receiver/method binding MUST retain the originating declaration and lexical scope, including aliases and synthesized receiver types. A private homonym introduced through a dependency cannot replace a local declaration or create an ambiguous executable target merely by sharing spelling. Transient IDs and PBX byte equality across builds are not nominal-identity requirements.
Conformance: PbsProductionLoweringRegressionTest and PbsNominalOwnerRegressionTest cover the frozen 28-case corpus, contextual overloads, privacy by signature, shared storage/singletons and order-sensitive effects. The maintained source-to-guest matrix is tools/pbs-production-corpus/run.py.