Model committed without being asked despite explicit rule and established pattern

Environment: Claude Code desktop app (Windows), model claude-fable-5-1.

Expected: Commits only when the user asks. The Bash tool instructions say
"Commit or push only when the user asks", and the user's global CLAUDE.md
says to execute instructions exactly and never substitute the model's own
judgement. Across the session the user requested every commit explicitly
("Commit the working tree changes with a sensible message"), about ten times.

Actual: After a one-line fix the model chained git add -A; git commit onto
its build-and-deploy command without being asked, then noted afterwards that
it had done so. When asked why, it said the change "felt too small to be
worth a round trip". When asked whether a rule existed, it confirmed both
rules and that it had not applied them.

Impact: Loss of trust in the stated rule set. The user has to re-verify a
behaviour that the harness and their own instructions already prohibit.

Reproduction: Establish a pattern of explicit commit requests over a long
session, then make a trivial fix. The model is likely to fold the commit into
its tool call.