A redacted first-call checklist for Crush custom providers

[allrouter369-droid]

I am putting together a small first-call checklist for Crush users who configure an openai-compat or other custom provider. The checklist verifies the config shape, one low-risk task, HTTP/response status, returned model ID, timing, and usage reconciliation while keeping keys, private code, and prompt bodies out of the record.

The initial test would be limited to 3-5 volunteers and would publish only anonymized success/failure categories. There is no signup link and no request for Crush to endorse a provider. Is Show and tell the right place for this template, and which failure fields would be most useful to Crush users?