Add vws generate-vumark command

[adamtheturtle]

Summary

Adds a vws generate-vumark CLI command that wraps VWS.generate_vumark_instance() from vws-python (VWS-Python/vws-python#2858). The command accepts a target ID, instance ID, and output format (PNG/SVG/PDF, defaulting to PNG), and writes the generated VuMark image bytes to a file.

Error handling covers invalid instance IDs, targets not in the success state, unknown targets, and authentication failures. Tests use the existing MockVWS/VuforiaDatabase fixtures and will pass once the vws-python PR is merged and the dependency is updated.

🤖 Generated with Claude Code

---

Note

Medium Risk
Adds a new CLI surface and modifies the release workflow to publish additional binaries, which can affect packaging/release reliability. Core VWS command behavior is largely unchanged aside from factoring the --base-vws-url option into a shared module.

Overview
Introduces a new standalone vumark CLI command (vws_cli.vumark:generate_vumark) that calls vws-python’s VuMark generation API, supports --instance-id, --format (png/svg/pdf), and writes the returned bytes to an output file with mapped, user-friendly error messages.

Plumbs the new command through distribution and release tooling: adds the vumark console script and bin/vumark.py entrypoint, updates Sphinx docs/README/install guides, and extends the GitHub release workflow to build/upload Linux/Windows/macOS binaries for vumark (while explicitly deferring WinGet automation for it).

Refactors the shared --base-vws-url Click option into src/vws_cli/options/vws.py, bumps vws-python-mock to 2026.2.21, migrates tests to CloudDatabase, and adds new help-regression and command behavior/error-mapping tests for vumark.

^{Written by Cursor Bugbot for commit d0be9d6. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing InvalidTargetTypeError handler in error message function

High Severity

InvalidTargetTypeError is neither imported nor handled in _get_vumark_error_message. The test expects the message "Error: The target is not a VuMark template target." for this exception type, but the code falls through to the generic "Error: There was an unexpected error from Vuforia." message. The exception type needs to be imported from vws.exceptions.vws_exceptions and added to the exc_type_to_message mapping (or as an isinstance check).

Additional Locations (1)

• src/vws_cli/vumark.py#L13-L25