Operator-Skill State Fragments

The operator skill changes independently from the CLI executable and the project scaffold. Operators need to know which copy is active before they trust its instructions.

The CLI recognizes one immutable target:

• skill: hi-cli
• version: 1.0.0
• revision: 45072f4721d9668177bc4dd006802935ae61e70f
• compatible CLI range: >=2.6.1 <3.0.0

The source points at that exact revision. Public instructions must not replace it with a moving branch.

hi operator status inspects global and current-project scopes for the active agent. It reports the effective copy, shadowed copies, incompatible copies, and typed detection failures.

Inside a matching project, a compatible project-local copy takes precedence. The global copy remains visible and becomes the fallback again outside that project.

Failure to inspect is unknown state. It cannot be presented as absence.

hi operator install ensures the global default even when a project-local copy is effective.

hi operator update repairs every detected hi-cli scope. With no detected copy, it exits with install guidance.

A successful process exit is provisional. The CLI reinspects source, version, revision, compatibility, scope, project root, and active-agent binding before reporting a verified action.

Scopes are independent. One scope can remain verified when another fails or cannot be verified. The result shows every action and exits nonzero for the incomplete operation.

Failed or unverified writes return a guarded retry that freezes the operation context and immutable target before re-entering inspection and verification.

An inspection failure returns a direct command rerun instead. That rerun inspects the complete current lifecycle and can reconsider the scopes now detected; it does not turn the earlier unknown state into an unconditional write.

hi operator migrate verifies a compatible replacement in every affected scope before removing an active-agent dp-cli copy. Barrier loss, target drift, or incomplete evidence refuses removal.

hi skills rename is a deprecated delegate to hi operator migrate. It has no separate rename policy.

Any observed successful write prints reload guidance, including partial-success cases.

Operator-skill state stays separate from:

• scaffold setup and update follow-through
• project baselines and baseline publishing
• pack selection
• executable update through hi upgrade
• shared-skill source editing and synchronization

The command page should answer what each subcommand does, what status means, how failures and partial results appear, and what to do after a write.

The concept page should explain why immutable identity, precedence, reinspection, and independent per-scope outcomes form one trust contract.