DigitalPuddle-specific orchestration and inspection routes will live under
/_digitalpuddle. The current baseline exposes:
GET /_digitalpuddle/capabilitiesfor the machine-readable capability legend and operation rows.src/openapi/digitalocean.openapi.jsonplussrc/openapi/digitalocean.openapi.provenance.json, which provide the pinned contract snapshot and source metadata used by maintainers and reviewers.
Planned routes still include health, version, state, journal, leak reports,
reset, scenario loading, clock advancement, and queue drain. The pinned
DigitalOcean OpenAPI contract is already available as checked-in artefact,
while full /v2 behaviour remains a later roadmap task.
These routes are for local harnesses and debugging. They are not part of the DigitalOcean API contract.