Stop bash-first file I/O under --dangerously-skip-permissions fleet-wide

Under --dangerously-skip-permissions (ccs.sh fleet-wide default), the harness injects a system instruction telling agents to use Bash (cat/head/sed-n/grep/find/sed/heredocs) INSTEAD OF native Read/Edit/Write, and withholds the native Grep tool entirely (calling it errors 'Grep is not available in this session'). Elazar wants the opposite: native Read/Edit/Write for file work, bash reserved for what only the shell does (psql/git/systemctl/journalctl/find/grep/package managers) - NOT a bash ban, NOT blocking grep/find (no substitute exists while Grep tool is withheld). Verified on lezama (db02-mba-l-cc): no local hook/deny-list causes it - settings.json only has guard-unbounded-output.sh + the standard AskUserQuestion/Agent/background deny. nw-venus-cc built a partial PreToolUse(Bash) deny hook (block-bash-native-equiv.py, venus-local so far) covering cat/head/tail->Read and sed -i->Edit; grep/find/ls deliberately left alone per this finding. Root instrument question open: is a per-command deny-list even the right fix, or does this need Anthropic's newer 'auto mode' (classifier-reviewed, replaces bypassPermissions) - not established yet. pm-llmmsgsrv-cc already flagged by db02-mba-l-cc, coordinate not duplicate.