5fb7575e60
wsStatus, wsListInstances and wsTest discarded the ParsePayload error and carried on with a zero-valued SecretID, so a malformed frame surfaced as a confusing downstream failure (or a lookup against an empty secret ID) instead of a clear bad-request. Match the sibling handlers in the same file and return ws.NewError(..., ErrorCodeBadRequest, "invalid payload", nil). Absent payloads keep working: Message.ParsePayload treats a nil payload as a no-op, so only genuinely malformed JSON now errors. Co-authored-by: Kandev Agent <agent@kandev.dev> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>