Fix error handling in VuMark database deletion

[adamtheturtle]

Summary

Add error handling to the delete_vumark_database endpoint to return a 404 instead of crashing with a 500 error when no matching VuMark database exists. The endpoint was missing the try/except ValueError pattern already present in delete_cloud_database.

Changes

• Fixed delete_vumark_database to catch ValueError from unpacking when no database matches the provided name
• Added test test_vumark_not_found to verify 404 is returned for missing databases
• Added test test_delete_vumark_database to verify successful deletion and subsequent 404

Test Plan

• All existing tests pass
• New tests verify VuMark database deletion behavior matches cloud database deletion

---

Note

Low Risk
Small change limited to mock Flask endpoint error handling plus tests; behavior now matches existing cloud database deletion and should only reduce 500s.

Overview
Prevents the DELETE /vumark_databases/<database_name> endpoint from erroring when the requested database doesn’t exist by catching the unpacking ValueError and returning HTTPStatus.NOT_FOUND.

Adds integration tests to verify VuMark deletion succeeds once and then returns 404 on subsequent deletes, and that deleting a nonexistent VuMark database returns 404.

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

ValueError conflates not-found and duplicates

Low Severity

delete_vumark_database catches any ValueError from the single-item unpack, so both “no matches” and “multiple matches” return HTTPStatus.NOT_FOUND. If duplicate database_names ever exist (e.g., due to state corruption or future changes), the endpoint silently reports 404 instead of surfacing the invariant violation.