Please provide the authoritative response contract and interpretation rules for the inner payload returned by Test an Action. We need evidence-backed fields proving terminal completion of the appointed Action, distinguishing expected api.access.deny from throws/timeouts/engine failures, covering the complete emitted access-token claim/effect set, and attributing console denial records to the tested deployed Action/version rather than echoed input. HTTP 200 or an empty payload cannot establish these properties. If the API cannot provide complete proof, please identify the officially supported mechanism that can.