Does rollout tracing capture which path produced a Declined exec status?

[mahirhir]

I've been reading rollout/src/policy.rs alongside rollout-trace/src/protocol_event.rs. Both exclude ExecApprovalRequest, ApplyPatchApprovalRequest, and GuardianAssessment from persistence, with a comment noting the long explicit match arms exist so new protocol variants force a deliberate choice. ExecCommandEnd still carries a Declined status, so a rollout file shows that a command didn't run. What it can't tell me is which path produced that outcome: an explicit human decision, an execpolicy amendment, or the guardian reviewer's own assessment, which carries a rationale field that isn't persisted either. Is that distinction meant to live somewhere else, like the app-server protocol layer, or is it considered out of scope for what a rollout is meant to capture?

[gitsult4n]

The distinction is in the rollout already
just as prose and not as a field

every decline funnels through ToolError::Rejected(message) and that message is copied into the item

core/src/tools/events.rs:547-558

ToolEventStage::Failure(ToolEventFailure::Rejected { message, .. }) => {
    let text = message.to_string();
    let exec_result = ExecCommandResult {
        stdout: String::new(),
        stderr: text.clone(),
        aggregated_output: text.clone(),
        exit_code: -1,
        duration: Duration::ZERO,
        formatted_output: text,
        status: ExecCommandStatus::Declined,
    };
    emit_exec_end(ctx, exec_input, exec_result).await;
}

emit_exec_end writes a TurnItem::CommandExecution and a paginated rollout persists every ItemCompleted
rollout/src/policy.rs:90-97

so the strings you can match on

guardian — core/src/guardian/review.rs:722-737

This action was rejected due to unacceptable risk.
Reason: {rationale}
{rejection_instructions}

that is the same rationale field you saw dropped with GuardianAssessment
the event is not persisted but the text survives inside the declined command item

human — app-server/src/bespoke_event_handling.rs:1964 and :2061 send rejected by user

policy or hook amendment deny — core/src/tools/approvals.rs:462-473

let rejection = match source {
    ApprovalResolutionSource::Hook => "rejected by configuration",
    ApprovalResolutionSource::Guardian => "automatic approval review denied the action",
    ApprovalResolutionSource::User => "rejected by user",
};

guardian timeout is guardian_timeout_message(model_info) :476 and a cancelled review is automatic approval review was cancelled :548-551

so it is recoverable but only by string matching
ApprovalResolutionSource itself never reaches disk so there is no typed field to key on