Problem
The WFL-io.md documentation contains contradictory statements about whether subprocess commands execute via the system shell by default.
Contradicting Sections
Cross-Platform Execution section (lines ~415-426):
States that commands execute "through the system shell by default" (cmd.exe on Windows, sh on Unix).
Subprocess Security section (lines ~505-514):
States that commands execute directly (non-shell) by default, and shell execution must be explicitly enabled.
Impact
This contradiction creates confusion about:
- The actual default behavior of subprocess execution
- Security implications and expectations
- Whether
using shell is required or optional
- Example code correctness in both sections
Context
Flagged in PR #185 review: #185 (comment)
The sections need to be aligned to consistently reflect the repository's actual policy on subprocess execution.
Related
Problem
The WFL-io.md documentation contains contradictory statements about whether subprocess commands execute via the system shell by default.
Contradicting Sections
Cross-Platform Execution section (lines ~415-426):
States that commands execute "through the system shell by default" (cmd.exe on Windows, sh on Unix).
Subprocess Security section (lines ~505-514):
States that commands execute directly (non-shell) by default, and shell execution must be explicitly enabled.
Impact
This contradiction creates confusion about:
using shellis required or optionalContext
Flagged in PR #185 review: #185 (comment)
The sections need to be aligned to consistently reflect the repository's actual policy on subprocess execution.
Related