TranscriptTrouble

A refusal the reader gets as a page rather than as data.

The rendering path answers a refusal the way it answers a transcript — in the cc-* vocabulary, ready to insert — so what crosses the wire is a status and some markup, and nothing else. That is what this is.

A TranscriptFailure would be the wrong type here. It cannot be read back off this wire: a status and a page of HTML do not say which case produced them, and inventing one — a SessionNotFound with an empty subject — would tell a client something the host never said. So the reading side gets what arrived, and a consumer that wants the failure as data reads it off SessionApi.history, whose refusals stay JSON.