When a Cutter response exceeded the framed transport limit after the command
was sent, the client kept the structured limit error only as message prose:
the command result's `message` named the bytes and the launch seed, and the
returned failure (completion unknown) carried no limit. The client result now
keeps that error's setting limit, and the service attaches it to the failure,
so it projects as `details.limit` (`bridge.max_request_bytes` with its
effective value and source). The test asserts the fact instead of the prose.
Refs #10508