Traces, health and recovery

Host’s local causal event journal is authoritative. Optional OTLP export is asynchronous and non-blocking; losing an exporter does not erase local evidence.

Events correlate command ID, workspace/panel or plugin identity, generation, request/subscription correlation, lifecycle transition, policy decision, and teardown. Mandatory lifecycle and security records survive ordinary retention pruning.

Inspection

GET /healthz
GET /v1/plugins/{id}/why
GET /v1/plugins/{id}/events
GET /v1/plugins/{id}/support-bundle

Use why first: it explains demand, selected provider, blockers, and dependency state. Then inspect the smallest event window containing the command or correlation ID.

Recovery order

1. Confirm /healthz and Host identity.
2. Inspect plugin desired/observed state and why.
3. Review permission and resource blockers.
4. Read causal events and produce a support bundle.
5. Retry with a new command ID only when the previous result is known.
6. Reset quarantine only after reviewing the cause.
7. Purge data only with explicit destructive intent.

Support bundles exclude secret values and pairing tokens by design.