[potiuk]

The public-surface scrub hook skipped a cd for directory tracking only when the separator after it was | or &.
That catches a cd that starts a pipeline, but not one in a later stage:

echo x | cd /path/to/tracker; gh issue create -t "..." -b "..."

Bash runs that cd in a subshell, so the shell stays in the upstream clone,
but the hook moved its tracked directory to the tracker and gave the bare gh the tracker exemption, skipping the scrub.
A cd inside a brace group in a pipeline did the same, whether the group came after the pipe (echo x | { true; cd /tracker; })
or was itself piped or backgrounded ({ cd /tracker; true; } | cat, where the | sits only on the group's last command).

Once a | or & has appeared on the line, any cd now marks the line as redirected,
and the splitter marks every command of a piped or backgrounded brace group so its cd does too;
a later bare git or gh then loses the cwd exemption.
This is the fail-closed rule the hook already applies to a cd after && or ||.

Tests: a new case in the per-path fixture (start upstream, piped cd into the tracker, bare gh / git commit must be scanned, four shapes),
and four shapes added to the redirect list.
Both fail on main and pass with the fix; the whole mod suite passes (tools/dev/check-claude-mods.sh --local).

Found by an automated security review of the hook after #1914.

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code (Claude Opus 5)

Generated-by: Claude Code (Claude Opus 5) following the guidelines

🤖 Generated with Claude Code