Motor Block config now shows the limits actually enforced, including the burst limit

• effectiveLimits on the config response. GET /api/public/v1/motor-blocks/{id}/config (and motorical_get_config) now returns effectiveLimits with dailyVolume, hourlyRate, burstLimit and throttled: the limits that are enforced right now, which is the lower of what you configured and any reputation throttle, with defaults filled in. The existing limits field is unchanged and still shows only what was configured, so it can leave out burstLimit when you never set one. Read effectiveLimits to know what will actually bind.
• Clearer MCP tool descriptions. motorical_list_motor_blocks now says it lists every block the connection covers (id and name), while motorical_motor_block_list lists manageable production blocks with type, domain and status, so their counts can differ. motorical_send_email says its sandbox advice applies to sandbox accounts only.

Documentation changed

• Endpoints
• Hosted MCP Resource Server