# Selected Test Command Boundaries

Batch: `f49f7990499af3a409baaf7b`

Status: incomplete implementation; no implementation registrations added.

The native entry point now rejects the six placeholder success responses for
`Std_TestQM`, `Std_TestReloadQM`, `Std_ViewExample1`, `Std_ViewExample2`,
`Std_ViewExample3`, and `Test_InsertFeature`.

`Std_TestProgress5` is also rejected before starting a sequencer. Its existing
mode 5 initialization creates one launcher with position zero, but advancement
falls through to mode 4 logic. At position 50 that logic removes the only
launcher and position, leaves the outer count at one, and continues with an
empty stack. This path cannot be registered as an implementation.

Remaining work requires desktop command definition anchors, not only the menu
entries in `freecad-source/src/Mod/Test/InitGui.py` at lines 43, 64, 74, and 86.
The current packet supplies only those menu entries and the Web native branches.
Its four supplemental source windows were consumed inspecting the native entry
point, sequencer lifecycle, registration list, and mounted adapter execution.
This is a source-window boundary, not evidence that desktop implementations
are absent.

Supply the desktop definitions and their helper anchors for all seven commands,
plus the selected facade dispatch and result contracts. Implement the progress
lifecycle, translation operations, Inventor examples, and feature insertion
using those sources, then connect the corresponding application operations and
register only completed behavior. Preserve document semantics and use the
existing OCCT backend wherever geometry is involved.

No tests, builds, browser validation, benchmarks, or acceptance were run.
The outer pipeline owns incremental build, synchronization, and route receipts.