fix(workflows): redact run and export secrets

[TheodoreSpeaks]

Summary

• project run outputs through the secret-safe display materializer
• apply fail-closed credential redaction to workflow exports
• add regression coverage for both leak paths

Type of Change

• Bug fix

Testing

• 31 targeted tests
• TypeScript type-check
• lint and block-registry validation
• 25 repo audits

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 12, 2026 4:25am

[cursor]

PR Summary

High Risk
Touches secret-handling paths for execution status outputs and public workflow exports. Fail-closed behavior is safer, but incorrect projection could still leak secrets or drop legitimate outputs.

Overview
Closes two secret-leak paths by making run status and workflow export fail closed on unproven credential data.

Run outputs now go through a new materializeExecutionDataForDisplayWithBlockOutputs path instead of raw collectFunctionalBlockOutputs. Selected block outputs are projected only from authoritative execution-state values with usable secret provenance; legacy/trace fallbacks and unproven state are omitted, and raw executionState never crosses the display boundary.

Workflow export enables redactOpaqueCredentialInputs, so nested tool-input credentials and opaque credential-bearing fields are nulled in the public export payload. Regression coverage covers both leak paths.

^{Reviewed by Cursor Bugbot for commit 08c27c3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

The PR routes selected run outputs through provenance-aware display projection and applies fail-closed credential sanitization to workflow exports.

• Materializes requested functional outputs from authoritative execution-state block data without exposing raw execution state.
• Prevents trace-only or unproven values from becoming public block outputs.
• Enables opaque credential redaction for exported workflows and adds regression coverage for both leak paths.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains in the fixes covered by the previous review threads.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/lib/logs/execution/trace-store.ts	Adds a display-boundary materializer that projects requested authoritative block-state outputs and excludes raw execution state and trace fallbacks.
apps/sim/lib/workflows/executor/execution-status.ts	Uses the secret-safe materializer for final and selected block outputs, resolving the previously reported state-only output loss.
apps/sim/lib/workflows/sanitization/json-sanitizer.ts	Enables fail-closed redaction of opaque credential-bearing inputs during public workflow export.
apps/sim/lib/workflows/operations/export-workflow.test.ts	Verifies nested tool credential and password parameters are removed while ordinary parameters remain intact.
apps/sim/lib/logs/execution/trace-store.test.ts	Covers authoritative state-only projection, provenance failures, partial state, legacy traces, and nonmutation of persisted execution state.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
State[Persisted execution state] --> Materialize[Materialize execution data]
Materialize --> Project[Project requested block outputs using secret provenance]
Project --> Status[Workflow status response]
Trace[Trace spans] -. Not used as functional output fallback .-> Project
Workflow[Normalized workflow state] --> Sanitize[Fail-closed export sanitization]
Sanitize --> Export[Public workflow export]

Loading

_{Reviews (5): Last reviewed commit: "fix(workflows): stop deriving outputs fr..." | Re-trigger Greptile}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit e92b6ab. Configure here.}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 08c27c3. Configure here.}

[TheodoreSpeaks]

@greptile