# Web CommandTest boundary

Batch: `922a097adeab1383ccbd1bfa`

The selected commands remain unsupported; this change does not claim completion
of their requested Worker/Facade implementation.

- `Web:desktop:Std_Test1`: `src/Gui/CommandTest.cpp:131` only discards its argument; availability is unconditional.
- `Web:desktop:Std_Test2`: `src/Gui/CommandTest.cpp:159` only discards its argument; availability requires a document.
- `Web:desktop:Std_Test3`: `src/Gui/CommandTest.cpp:185` retrieves the document and returns if absent, with no subsequent operation; availability requires a document.
- `Web:desktop:Std_Test4`: `src/Gui/CommandTest.cpp:217` retrieves the document and returns if absent, with no subsequent operation; availability requires a document.

The Web adapter previously dispatched all four to `Test/test.inspectRegistry`
with `src/Mod/Test/Init.py` as the source. That operation is unrelated to these
desktop commands. The adapter now returns `unsupported_command` through the
existing application dispatcher and removes those false endpoint mappings.
Native sources and registrations are unchanged. No successful no-op, fixed
result, or substitute business operation has been introduced.

Remaining boundary: the supplied native activation bodies contain no business
operation to port. Implementing new functionality requires an actual operation
specified for these commands or native sources that implement one. Adding a
Worker route or native registration alone would not resolve this boundary.

No tests, builds, browser validation, benchmarks, or acceptance runs were performed.
Incremental build, sync, and route receipts remain with the outer pipeline.