Read a cd After an Earlier Command for Rule 6 in the Write Guard #3351

Context

Found by the local review of the backslash-newline narrowing (branch feature/guard-backslash-newline-quoting), confirmed with a classify probe on develop using constructed commands and offline seams, where a directory ending in primary reads as a primary checkout.

Gap

Requirement 6 reads a cd only where it leads the command. A cd after any earlier command is not read, so a mutating git command after it is judged against the session's own directory. Develop allows each of these:

• git status && cd /example/primary && git reset --hard
• true; cd /example/primary; git commit -m x
• cd /example/primary on one line and git commit -m x on the next, after any first line

The leading form, cd /example/primary; git commit -m x, is denied. The README states the leading-cd scope, so this may be the precision-over-recall stance rather than an oversight. An agent prefixing a harmless status check is a realistic shape, though.

Possible Direction

Track the directory through every cd in the command's top-level sequence, as the push rule already does for a cd anywhere, and fail closed where a cd sits inside a branch the guard cannot follow.