claude.md: switch notification mechanism to notify.sh shell script

The Telegram-via-PushNotification-tool path is replaced with a
direct ~/.claude/notify.sh "Text" invocation. Same payload
discipline (actionable one-liner, skip 'hi, I' framing); the
delivery channel is now under the user's control. Tested in the
previous session.

CLAUDE.md

@@ -119,29 +119,17 @@ question.
 
 ### Notifications
 
-The user has push notifications wired (Telegram). Use
+When the user is away, notify him when you're done and there
-`PushNotification` ONLY when there is something I genuinely
+is nothing left to do.
-want from them — i.e. exactly the bounce-back triggers above:
 
-- A real design judgement I have not made myself (architectural
+~/.claude/notify.sh "Text" 
-  fork, multiple substantive options none clearly default).
-- A genuinely unexpected event that changes the project's
-  direction (fundamental design flaw, dependency failure,
-  invariant violation, refuting bench result).
-- An explicit checkpoint the user asked for.
-
-**Do NOT notify** for: shipping iters that completed cleanly,
-routine progress, "just FYI" status, or summaries when nothing
-needs their input. The Telegram message is a poke; an
-unnecessary one accumulates as noise. Err toward not sending.
 
 When notifying, the message body should be the actionable
 summary: what I need from them, in one short line. Skip the
 "hi, I" framing — just the gist. The user will see it on phone
-and likely respond either via Telegram or by returning to the
+and likely respond by returning to the session.
-session.
 
-The default mode is autonomous. The notification is the
+By default, you act autonomous. The notification is the
 exception, not the rule.
 
 ## Bug fixes — TDD, always