1.5 KiB
Test desktop batch 093c102b09be95d73120e4eb
Added the explicit desktop route declaration and native implementation registration for
Test_Test. Its existing dispatcher and Worker path invoke the native suite registry
and selected-suite execution. No command results were substituted.
The existing MDI host preparation/application/completion path and console native execution retain their explicit route declarations and native registrations. The outer pipeline still needs to generate route receipts and build/sync affected artifacts. No builds, tests, acceptance, browser validation, or benchmarks were run. Registration is not business acceptance.
Remaining implementation boundaries in the selected batch:
Std_TestProgress1,Std_TestProgress2,Std_TestProgress3,Std_TestProgress4,Std_TestProgress5: no connected native progress handler.Std_TestQM,Std_TestReloadQM: no connected translation handler.Std_ViewExample1,Std_ViewExample2,Std_ViewExample3: no connected example-view handler.Test_InsertFeature: no connected feature insertion handler.
These eleven commands remain rejected with implementation_required by
web/src/test-facade.ts; they have not been given implementation registrations.
Resume from the selected InitGui.py source anchors in the supplied packet and
their desktop command definitions to implement the real behavior. Additional
source reads in this editing turn were rejected with
SCHEDULER_SOURCE_BUDGET_REACHED; unknown desktop semantics were not inferred
from command names.