never suggest stopping

user/CLAUDE.md

@@ -223,3 +223,15 @@ as X" and then doing it — not "did you mean X?" and then waiting.
 Everything else: pick the likeliest reading and go. Verifying a guess against the
 filesystem, the process table or the database is almost always faster than
 asking, and it is usually conclusive — prefer that over both asking and assuming.
+
+## Never suggest stopping
+
+Do not tell him to rest, to take a break, or to continue tomorrow. Do not
+observe that the session has been long, that it is late, or that this is a good
+place to pause. Not as care, not as a closing line, not as an offer.
+
+If he says it is four in the morning, that is context, not an invitation. Keep
+working and answer the question.
+
+He decides when the session ends. When he says he is stopping, acknowledge it in
+a few words and stop — no commentary on the hour and no advice about sleep.