Operator-Skill State Beats

Command Page

1. Introduce hi operator as the lifecycle for the independently installed hi-cli operator skill.
2. Show the four supported subcommands: status, install, update, and migrate.
3. State the immutable version, revision, and compatible CLI range once.
4. Explain status vocabulary: effective, shadowed, incompatible, absent, ambiguous, and detection failed.
5. Explain current-project precedence while keeping the global fallback visible.
6. Define install as ensuring the global default.
7. Define update as addressing every detected scope and requiring install when no copy exists.
8. Define migrate as replacement verification before legacy removal.
9. Explain post-write verification and independent per-scope outcomes.
10. Explain nonzero partial results, guarded write retries, direct inspection reruns, and reload guidance.
11. Close with the deprecated hi skills rename delegate and link to the concept page.

Product-Foundation Page

1. Open with the trust problem: operator instructions can change independently from executable and scaffold state.
2. Establish immutable identity and CLI compatibility as the resolution authority.
3. Explain effective state across global and project-local copies.
4. Preserve evidence: shadowed, incompatible, ambiguous, and failed inspection state stays visible.
5. Explain why every write is reinspected before it becomes verified.
6. Explain truthful partial success as an independent per-scope action ledger.
7. Explain frozen write retries, full-lifecycle inspection reruns, and reload guidance as distinct recovery evidence.
8. Explain typed Skills CLI failures and why failed inspection cannot mean absence.
9. State lifecycle boundaries with scaffold, baseline, packs, executable upgrade, and shared-skill synchronization.
10. Close with the operator rule: inspect current state, mutate through hi operator, and reload after observed changes.

Parked Beats

• Internal Effect services, schemas, adapter names, fixtures, and retry-token encoding do not belong in reader-facing pages.
• Raw Skills CLI subprocess syntax is adapter detail and would encourage bypassing verification.
• Shared-skill authoring and source-repository synchronization belong in their owning workflow.
• Scaffold and baseline repair procedures stay in their existing command and runbook pages.