Coverage and verification

This wiki was checked against the BitCadence source snapshot on November 13, 2026. It separates everyday walkthroughs from exact references, and shipped routes from proposed designs.

CLI coverage

The complete CLI reference maps 93 command/group paths and 301 arguments and options across the shared bitcadence / mco tree. It includes nested groups, defaults, required arguments, option aliases, repeatable values, hidden compatibility options and synthesized help/completion options. Each command has a purpose, safe example, expected result and recovery notes.

The machine-readable inventory binds every path and parameter to a documentation anchor and source metadata. The checker compares the actual Typer command tree without invoking operational callbacks. Unknown commands/options, changed defaults and missing anchors are failures. Negative-control checks also verified that the checker rejects missing/stale commands and parameters.

The desktop executable is separate and is covered under Windows Local Control and tray.

GUI coverage

The GUI reference covers the twelve console navigation pages, Score and detail views, the five-page technical dashboard, model-connection/lock/modal flows, Windows manager/tray actions and all 33 server-driven settings. Its 279 grouped control/workflow mappings link instructions to source locations.

This is a manually grouped feature inventory, not a claim that every possible dynamic server record or option value was enumerated. Defined-but-unreachable legacy components and pending local changes are explicitly identified; they are not presented as released controls.

Source hashes make interface drift visible. A changed GUI source file requires reviewing/updating the inventory before strict coverage passes again. Hash checks prove the source baseline, not rendered behavior or successful effects.

What was checked safely

Recursive command/parameter coverage, required documentation anchors and parser-valid examples.
Every local documentation link, image and fragment in the generated website.
The help site's section search, keyboard access, copy controls and narrow-screen navigation.
Regression tests for technical-dashboard prompt cancellation: pressing Cancel submits no abort or batch-cancel request; an intentional blank confirmation still follows the supported behavior.
Legacy-domain redirects for both old hostnames, HTTP/HTTPS, root and path/query requests; removal of the obsolete site project.

No real jobs were approved, cancelled, retried, reassigned or published to perform these checks. No live helper was stopped and no production token/configuration was changed. Provider calls and destructive product controls require disposable fixtures or separate operational authorization, not a documentation test against someone's live work.

Current limits and known issues

The usability review contains source-confirmed issues and concrete acceptance checks. Product GUI behavior is source-reviewed; this refresh does not claim that every backend integration was exercised on every operating system. Existing screenshots illustrate the workflow and may precede small label changes.

The Cancel-prompt fix is included in this source branch. An already-running gateway does not acquire a code patch just because the public help site was published. The live product needs its normal reviewed release/update before that fix can be assumed installed.

Keep the wiki complete

From a source checkout, using the project's Python environment:

python docs/wiki/_review/verify_cli_coverage.py --repo .
python docs/wiki/_review/verify_gui_coverage.py --repo . --strict-hashes
python docs/wiki/_review/verify_cli_examples.py docs/wiki
python scripts/build_wiki.py

CI runs the coverage checkers and site build alongside the tests. When a feature changes, update its steps, expected result, failure/recovery guidance and inventory entry, then rebuild. Keep credentials and household/machine-specific data out of public documentation.