Rename DatabaseDict to CloudDatabaseDict

[adamtheturtle]

Summary

• Renamed DatabaseDict to CloudDatabaseDict to clarify it represents a cloud database type
• Renamed VuforiaDatabase to CloudDatabase for the same reason

There are three database types in the target manager: Device, Cloud, and VuMark.

🤖 Generated with Claude Code

---

Note

Medium Risk
Public API renames (VuforiaDatabase/DatabaseDict -> CloudDatabase/CloudDatabaseDict) can break downstream imports and type references. Behavior appears unchanged, but the surface-level rename touches many modules and tests.

Overview
Renames the core database model from VuforiaDatabase to CloudDatabase and the associated TypedDict from DatabaseDict to CloudDatabaseDict to clarify these represent cloud databases.

Propagates the rename through request matchers, Flask server apps, validators, MockVWS/TargetManager APIs, docs/examples, and tests, plus updates static-analysis ignore lists in pyproject.toml.

^{Written by Cursor Bugbot for commit fef9aa3. 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]

VuMark types incorrectly renamed from Vuforia to Cloud

Low Severity

VuMarkVuforiaDatabase was renamed to VuMarkCloudDatabase, and _VuMarkVuforiaDatabaseSettings to _VuMarkCloudDatabaseSettings. The PR description explicitly states there are three separate database types: Device, Cloud, and VuMark. "Vuforia" in the original names referred to the platform, not the Cloud database type. Calling VuMark types "Cloud" is semantically misleading since VuMark is explicitly a distinct type from Cloud. The fixture name vumark_vuforia_database and env_prefix="VUMARK_VUFORIA_" were left unchanged, creating an inconsistency within the same file.

Additional Locations (1)

• tests/mock_vws/fixtures/credentials.py#L38-L51