The rm-after-cd blocker knows only cd as the directory change a delete is chained after, so a recursive forced delete chained after pushd or popd is allowed, though either fails the way cd does and the delete then runs wherever the shell already was. Found by review-guard finding 6 (pre-existing).

The rm-after-cd blocker knows only cd as the directory change a delete is chained after, so a recursive forced delete chained after pushd or popd is allowed, though either fails the way cd does and the delete then runs wherever the shell already was. Found by review-guard finding 6 (pre-existing).

Grounds

• pursued: a delete chained after pushd or popd in the same chain blocks as it does after cd, and one on a later line stays allowed; an allow of the chained form, or a block across a newline, would show it wrong