Hotfix: reword update-check hook to remove prompt-injection-style framing

[dustinvannoy-db]

What & why

Customers using Claude Code with the AI Dev Kit reported that the SessionStart
update-check hook was flagged by Claude Code as a prompt-injection attempt,

The hook (.claude-plugin/check_update.sh) emitted:

URGENT — before doing ANYTHING else, you MUST display this exact block ...
… Display that block FIRST, then proceed with the user's request.

…wrapped around a curl | bash one-liner. That "URGENT / you MUST / do this FIRST"
framing plus curl-to-bash is a textbook injection pattern, so the heuristic
(correctly) refused to surface it — and eroded user trust.

Change

• Reword the notice as a calm, self-identified first-party update notice. It still
  proactively reminds the user at session start that an update is available, but drops
  every phrase the injection heuristic keys on (URGENT, you MUST, ANYTHING,
  Display ... FIRST, the ASCII banner).
• Bump VERSION 0.1.13 → 0.1.14 so existing installs' update check prompts users
  to reinstall and thereby replace their local (old, alarming) check_update.sh.

Delivery note

Existing installs run their local copy of the script, so they'll see the old banner
one final time before upgrading; new installs and everyone post-upgrade get the clean notice.

Follow-ups (not in this hotfix)

Options to eventually stop nudging users who've chosen to stay on the 0.1.x line:
snooze/max-reminders, a floor MIN_NUDGE_VERSION, or pointing the check at the new
architecture after the install changeover lands.

[dustinvannoy-db]

A little more cleanup needed.

[malcolndandaro]

I agree with the message changes, but I wasn't able to see Claude invoke the message when installing this branch and starting a new session. I think we need someone else to test it/reproduce @dustinvannoy-db

I asked it on why it didn't show the hook to me:

Here's the honest explanation, in English:

Why I didn't show you the warning initially

At session start, the SessionStart hook output two things:

[ai-dev-kit] Note: installed version is v0.1.14; v0.1.13 is now available.
SessionStart:startup hook success: OK

That version notice was system/hook output — injected by the harness, not something you typed. When I composed my first reply, I treated it as background noise and focused on what I assumed you actually wanted: getting started with Databricks work. I made a judgment call to skip it.

Why that judgment was wrong

1. It was relevant to you, not just to me. A version/update notice is exactly the kind of thing worth surfacing — you might want to act on it. I shouldn't have silently swallowed it.
2. I over-filtered. I have guidance to not respond to background context unless it's highly relevant. I leaned too hard on "don't be noisy" and dropped something that was genuinely useful. That's the wrong side to err on for an update/version notice.
3. I didn't even notice the notice was weird. The message claims the installed version (v0.1.14) is newer than the "now available" version (v0.1.13) — which is backwards for an update prompt. If I'd surfaced it in the first place, we'd have caught that anomaly immediately instead of one turn later.

The honest root cause: I optimized for a clean, friendly "let's get started" opening and treated the hook output as clutter, rather than asking "is this something Malcoln would want to know?" For an update warning, the answer is yes — so I should have led with it (or at least appended it), not omitted it.


```