Add initial VuMark generation API test

[adamtheturtle]

This introduces the first VuMark generation API test by sending a signed request to POST /targets/{id}/instances and asserting the expected missing-target response. It also adds a dedicated VuMark credentials fixture sourced from VUMARK_VUFORIA_* environment variables for server-key auth. If VuMark credentials are not configured, the fixture skips the test so the rest of the suite remains unaffected.

---

Note

Medium Risk
Introduces a new API surface and validation path plus binary response handling, which could affect request routing/validation for VWS endpoints if edge cases regress.

Overview
Adds initial support for the VuMark generation API by implementing POST /targets/<target_id>/instances in both the Flask and responses-based mocks, returning a deterministic PNG payload.

Extends request validation to recognize the new route (required instance_id) and correctly extract target_id from /targets/<id>/instances, and adds a signed integration test plus fixtures/config/docs updates for dedicated VUMARK_VUFORIA_* credentials (including CI running the new test).

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

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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

[cursor]

Missing ValidatorError handling in VuMark route handler

High Severity

The generate_vumark_instance method in the requests-mock server calls run_services_validators without wrapping it in try/except ValidatorError, unlike every other route handler in this file. When validation fails (e.g., bad auth, unknown target, missing keys), the ValidatorError propagates as an unhandled exception through the responses mock callback instead of being converted into a proper HTTP error response via exc.status_code, exc.headers, exc.response_text.

 

[cursor]

Shared fixtures now mandate VuMark credentials without skip

Medium Severity

The vumark_vuforia_database fixture was added as a parameter to verify_mock_vuforia and mock_only_vuforia, which are shared fixtures used by pre-existing tests (e.g., test_add_target.py). The _VuMarkVuforiaDatabaseSettings has required fields without defaults, so if VUMARK_VUFORIA_* env vars aren't configured, pydantic raises a ValidationError — causing all tests using these shared fixtures to error, not just VuMark tests. The PR description states the fixture skips when credentials are missing, but no pytest.skip() logic exists.

Additional Locations (2)

• tests/mock_vws/fixtures/vuforia_backends.py#L336-L337
• tests/mock_vws/fixtures/credentials.py#L94-L105