Problem
Execution traces persist event messages, command labels, and detail fields for the local Console. A credential-shaped value reaching an event can therefore remain in the local trace and later be exposed through an operator-facing view.
Requested change
Add a focused, deterministic redaction boundary before trace persistence and regression tests covering bearer values, GitHub/Moltbook-shaped tokens, private-key blocks, and local paths. Keep the change local to trace safety; do not add network writes or change the Writer policy.
Acceptance criteria
- Persisted execution trace content contains no credential-shaped values or personal absolute paths.
- Existing phase, status, and event ordering behavior remains unchanged.
- The focused test suite passes.
Problem
Execution traces persist event messages, command labels, and detail fields for the local Console. A credential-shaped value reaching an event can therefore remain in the local trace and later be exposed through an operator-facing view.
Requested change
Add a focused, deterministic redaction boundary before trace persistence and regression tests covering bearer values, GitHub/Moltbook-shaped tokens, private-key blocks, and local paths. Keep the change local to trace safety; do not add network writes or change the Writer policy.
Acceptance criteria