The cited update behavior is reachable and does fetch and stage newer CLI releases; it is not a false alarm. However, this is the package updating itself from npm and it provides the OPENCRAWL_NO_UPDATE=1 off-switch, which the current self-update rule classifies as suspicious, even when undisclosed, so the earlier publish block does not apply.
Static reason
One or more suspicious static signals were detected.
Trigger
A normal eligible CLI invocation schedules an update; the check runs in the background when due. OPENCRAWL_NO_UPDATE=1 disables it.
Impact
The CLI updates itself without a separate update command. Because this is an update of the same package from npm with an off-switch, current policy calls for a warning rather than a publish block.
Mechanism
The npm-installed CLI checks registry.npmjs.org for the latest version, fetches metadata and release packages, verifies integrity, and stores the release in the user cache. A later invocation can select the cached version.
Evidence
runtime/opencrawl.jsbin/opencrawl.cjsREADME.mduser cache: opencrawl/update.jsonuser cache: opencrawl/update.lockuser cache: opencrawl/releases/<version>/