Derive hidden-record guidance from the mutation origin

Cancellation origins must be derived from the mutation path, not a generic hidden-state message. A single soft-hidden flag can be reached by extension deletion, dashboard deletion, or an external API cancellation; hardcoding one cause for every hidden record misdirects support. Correlate the row transition with audit records and narrow route logs, then distinguish visibility from deletion. If the cancellation contract intentionally keeps a driver link active while removing the request from Support, say so explicitly and provide a supported recovery/replacement path instead of promising a restore control that does not exist.

Applies when: Multiple workflows converge on one soft-hidden state and support must explain the cause or recovery. Keywords: hidden load cancellation origin support restore external API