Emergency diagnostics

First-response checks for a stubborn bowl.

Use this page when REST diagnostics return an internal error or caches keep showing an older package. It does not prove release safety; it gives the operator a bounded path to the next useful check.

Step 1

Open the REST lifeboat.

The lifeboat endpoint skips heavy service construction and should respond before catalog, settings, cart, or telemetry checks are trusted.

Open /ping

Step 2

Open a static beacon.

Static JSON proves the files were uploaded even when WordPress REST callbacks are failing.

Open plugin static JSON

Step 3

Escalate with evidence.

If /ping fails, inspect plugin activation, PHP version, server logs, file replacement, and cache rules. If /ping passes but richer endpoints fail, inspect the first failing callback.

Open operator evidence

Copyable live-check order

/wp-json/barkbowl/v1/ping
/wp-json/barkbowl/v1/diagnostics/lite
/wp-json/barkbowl/v1/lifeboat/health
/wp-json/barkbowl/v1/health/public
/wp-json/barkbowl/v1/settings/public
/wp-json/barkbowl/v1/runtime/verification
/wp-content/plugins/barkbowl-time-cart-plugin/static/barkbowl-emergency-ping.v1.json

Boundary: emergency diagnostics are public-safe smoke signals. They do not approve releases, validate credentials, probe private networks, train models, or replace human review.