[Dogfood] update --check ignores --registry

[agent-kit-startup]

Summary

agent-kit update --check --json --registry <local-kit-checkout> still compares the installed consumer stamp to the public remote latest tag and reports up-to-date with registryUrl / registryRef pointing at the public storefront.

In the same session, agent-kit diff --registry <local-kit-checkout> correctly resolves the local registry and reports L0 drift. agent-kit update --registry <local-kit-checkout> applies from that tree and can leave the consumer ahead-of-public on a subsequent plain --check.

Expected

When --registry (or equivalent local source) is set, --check should compare against that source's version and surface drift / apply recommendation consistently with diff / update.

Actual

• --check ignores --registry for version comparison and status messaging
• --diff and update honor --registry
• Operators doing "check first, then refresh" get a false "nothing to do" signal

Impact

Local/factory upgrade paths (pre-public release) are hard to reason about; premature stop risk when trusting --check alone.

Local reference

Consumer dogfood note: .cursor/dogfood/cursor_update_check_ignores_registry_20260804.md

Tags

agent-kit-update, update-check, registry-flag, cli