* feat(cli): surface outdated CLI and skills to agents; add hyperframes update
Single commit of #7094 on top of main (no merge commits through the signed
GraphQL path). Includes: 2h update/skills check interval and stale-cache
recheck; `_meta.checkedAt`, `_meta.skillsOutdated`, `_meta.skillsMissing`;
`_meta.updateNotice`, one sentence for the agent to relay to the person, at
most once a day per project (brew/npx-aware command, omitted under CI, the
update-check opt-out and agent plugins); `hyperframes update [--check]
[--yes] [--json]` (CLI then skills at the installed CLI's tag; brew
version read back); doctor names the running binary and its channel; the
hyperframes-cli skill gets one line to pass the notice on, naming no
command. Keeps main's install-target skills check (#7120) in updateSkills.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): update notice names a command that moves this install
- `_meta.updateNotice` (and `update --check`'s skills command) now name a
command that moves the running install: a global npm/pnpm/bun/brew CLI
runs its own `hyperframes update` (or just its manager's command when
only the CLI is behind), since `npx hyperframes` would run a project's
copy or a fresh npx one; a project-local CLI moves with its project's
manager by lockfile (`npm install`/`pnpm add`/`bun add`/`yarn add
hyperframes@<v>`), which `update --yes` now names too instead of
`npx hyperframes@latest`.
- `update`'s confirmation hint states a fact and names no step for the
agent: "Updating is the person's call; `update --check` only reports."
- `upgrade --json`, `upgrade --project --json` and every `skills` JSON
output leave out `_meta.updateNotice` (NO_UPDATE_NOTICE), like `update`.
- dailyNotice: a null/non-object file reads as empty and is repaired; a
future timestamp is stale; writes go through a 0600 tmp file + rename;
withMeta never throws from the notice.
- Docs: --json without --yes exits 2; plugin `update` exits 1
(plugin_managed); full `_meta` sample; per-install notice commands.
`update --check` says "npm registry not reached" instead of "latest".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): init and skills update only touch HyperFrames skills; --skip-skills works
* fix(cli): init never touches installed skills and no command removes one
* fix(cli): shorten the init skills comment
* fix(cli): shorten the init skills comment
* fix(cli): the stale-skills notice reaches agents that run without a terminal
* test(cli): a run without a terminal now checks skills in the background
* fix(cli): the stale-skills notice also prints on --json runs
* fix(cli): commands exit without waiting on update checks or telemetry
The update and skills checks run in a detached child that refreshes the
caches for the next run; the parent only reads the caches. finalizeCli no
longer awaits the telemetry flush: the exit handler flushSync() delivers
what is queued. The events beacon, feedback and figma error paths stop
awaiting flush() too.
* fix(cli): retry a failed background check at most once an hour
Before starting the background worker, the CLI stamps a per-check attempt
time and skips a check it attempted within the hour, so a dead network no
longer starts a worker on every command. The stale-pin notice writes onto a
fresh read, detached spawns set windowsHide, and a test ties the worker path
to its build entry.
* fix(cli): a failed-check stamp dated in the future no longer silences update checks