ReadonlyapplicationThe wired application.
ReadonlycommandsThe fake command capability the plan bound to.
ReadonlydiagnosticsLifecycle and operation diagnostics, in order.
ReadonlyeditorsThe fake in-memory document behind the Editors service.
ReadonlyenvironmentThe fake host environment runtime preflight reads.
ReadonlyeventsDiagnostic event names, in order. Convenient for ordering assertions.
ReadonlyfileThe fake native watchers the plan's file watchers subscribe to.
ReadonlylanguageThe fake language status area the plan's items render on.
ReadonlylocalizationThe fake display language and bundle behind the Localization service.
ReadonlylogsEverything the application logged.
ReadonlynotificationsThe fake message surface behind the Notifications service.
ReadonlyprogressThe fake progress UI behind context.progress.
ReadonlyquickThe fake quick input the QuickInput service resolves to.
ReadonlysecretsThe fake secret storage the plan's secret definitions read and write.
ReadonlysettingsThe fake settings capability the plan bound to.
ReadonlystatusThe fake status bar the plan's items render on.
ReadonlystorageThe fake persisted state the plan's storage definitions read and write.
ReadonlytreeThe fake tree view registry the plan's views register into.
ReadonlywebviewsThe fake webview host the plan's panels and views run on.
The same ownership, named rather than counted: the scope trees, the hosted services that are up, the operations that have not settled.
leaks() answers "did anything survive stop()"; this answers "what, and
whose is it". Reach for it when a leak assertion fails, or to assert that
a specific module's scope is the one still holding something.
What the framework still owns. Assert this is empty after stop().
Activates the already statically validated plan through the production host, including runtime preflight, module binding and the same synchronous subscription failsafe.
Deactivates through the production stop path. Safe to call again after the first stop has settled; the underlying host owns idempotency.
A production plan running on observable fake capabilities.
Recording collections such as status items, tree views and panels retain disposed records so tests can inspect history. Consult each fake's documented
disposed/registeredstate; not every fake represents cleanup by removing an entry from an array.