Diagnostics guide

Diagnose the layer
you actually own.

Separate website-overlay health from commerce-application health so a green marketing page can never be mistaken for a healthy checkout or payment system.

01 / PUBLIC

Use diagnostics.php for the website overlay only

The endpoint returns non-sensitive version and file-readiness information for public website assets. It intentionally avoids database connections, queue calls and provider requests.

curl -fsS https://thonem.brightery.com/_thonem-site/diagnostics.php
02 / SERVER

Run the local doctor before and after release work

The server-side command can inspect the package without widening the public attack surface.

bin/thonem-cloudpanel doctor
bin/thonem-cloudpanel verify
03 / BASELINE

Protect application routes with before/after comparison

Baseline routes such as /thonem.js, selected APIs and payment callbacks before enabling a new website overlay.

bin/route-baseline snapshot https://thonem.brightery.com /tmp/thonem-v9.json /thonem.js /YOUR/API/ROUTE
bin/route-baseline compare https://thonem.brightery.com /tmp/thonem-v9.json
04 / LIMITS

Do not infer commerce health from website health

Checkout, payment, worker, database and provider tests belong to the commerce application’s own release and monitoring process.