ScriptRunner Connect

This file answers theory. Before touching the CLI read references/cli-workflow.md. Before writing a script read references/scripting.md. Read references/testing.md only when the user asks for tests.

Before the first CLI call

Settle which command to invoke, once per session, ahead of every other CLI step.

command -v sr-connect. A hit means the CLI is installed and on PATH: call it as sr-connect <group> <verb> everywhere, including in commands handed to the user. No hit: call it as npx @sr-connect/cli <group> <verb>, and pin the session's first call to npx @sr-connect/cli@latest so the cached copy is current.
<cli> cli check-updates --agent --raw. The document carries updateAvailable, current and latest, plus command when there is an update. Exit 1 is a registry it could not read and exit 4 is a registry publishing no release; neither blocks the work, so say so and carry on with the version in hand.
When updateAvailable is true, name both versions and ask whether the user upgrades it or you do. Never upgrade without that answer.

The command field is the upgrade line derived from how this copy was installed, and it is right for npm, pnpm, bun and npx. It is wrong for two installs the CLI reads as npm, so check for them before quoting it: resolve sr-connect to its real path, or run yarn global bin and volta which sr-connect.