Extract VM diagnostic handler
This commit is contained in:
@@ -728,6 +728,12 @@ do not mix mechanical moves with semantic changes.
|
||||
through guarded `StepValue`; shared operand storage, addressing, and native-string encoding remain in the
|
||||
coordinator. Runtime validation remains green.
|
||||
|
||||
The seventeenth bounded `VirtualMachine.Step` extraction moved diagnostic operand/newline accumulation and
|
||||
synchronous show-and-clear prompt dispatch into `engine/Age.Engine/Vm/VirtualMachine.Diagnostics.cs`. The
|
||||
top-level dispatcher retains all labels and aliases at their existing positions and passes the complete
|
||||
instruction through guarded `StepDiagnostic`; shared accumulator state and native-context formatting remain
|
||||
in the coordinator. Runtime validation remains green.
|
||||
|
||||
**Gate:** no externally visible behavior or command changes; generated artifacts are byte-identical where
|
||||
deterministic, and the corresponding engine, Python, Godot, and corpus validations remain green after
|
||||
each domain move.
|
||||
@@ -1101,8 +1107,8 @@ Continue step 2 of the **codebase consolidation** maintenance slice: behavior-ne
|
||||
by the tracked launcher and layered validation driver. With the planned `Main`, `GodotAdvHost`, and `GfxState`
|
||||
domains isolated and the audio, movie, surface/texture, retained-object, animation, presentation, ADV-text,
|
||||
text-history, ADV-service, input, timing, persistence, and memory/collection `VirtualMachine.Step` families routed
|
||||
through domain handlers, with control-flow/coroutine, process/root-exit/cross-script lifecycle, and scalar and
|
||||
string-value dispatch now isolated as well, extract diagnostic accumulation and prompt dispatch next without
|
||||
replacing the proven dispatcher or changing public types, commands, and generated output.
|
||||
through domain handlers, with control-flow/coroutine, process/root-exit/cross-script lifecycle, value, and
|
||||
diagnostic dispatch now isolated as well, extract message-window and system-menu runtime settings
|
||||
next without replacing the proven dispatcher or changing public types, commands, and generated output.
|
||||
Concrete playthrough blockers may still preempt this bounded maintenance work; the consolidation effort does
|
||||
not replace Phase B gameplay validation or the open cross-platform gates.
|
||||
|
||||
Reference in New Issue
Block a user