Execution data redaction now explicit in API

When pulling execution data via the n8n public API, callers previously had no way to explicitly request redacted or revealed output — the system applied workflow-level redaction policies with no override. This left developers in a bind when they needed predictable behavior, especially for automation pipelines or compliance audits where data visibility must be consistent.

The public API now accepts a redactExecutionData query parameter on both GET /executions and GET /executions/:id. Passing true forces redaction, false requests revealed data (and fails with a 403 if the caller lacks the execution:reveal scope), and omitting the parameter falls back to workflow policy. The response now includes a redactionInfo object when data has been redacted, exposing whether the data is redacted, the reason, and whether the current user can reveal it.

This matters for developers building integrations that need deterministic output handling — automation scripts can now reliably get redacted data without surprises, and authorized users can pull revealed data without guessing at policy defaults.