chore(cli): hold public hosted release behind explicit authorization

[tomdps]

Status: release authorization lock — do not start

The hosted private MVP is intentionally unpublished. This issue is outside the private-MVP implementation graph and may not be implemented, merged, or used to publish anything until a maintainer explicitly authorizes release in a new comment after reviewing Zero Cloud #28 evidence.

Future outcome

If and only if release is explicitly authorized, perform the one atomic public cutover that registers the already-certified hosted command manifest in the ordinary zeroshot CLI and allows the normal release pipeline to publish it.

Until then:

• fix(cli): hide hosted target commands until MVP certification #919's stable hosted-command suppression remains authoritative;
• the private candidate is digest-pinned, bounded-retention, and nonpublic;
• no runtime flag, environment variable, alternate binary, prerelease tag, registry, docs link, completion entry, or hidden command exposes hosted functionality;
• private MVP completion does not imply public readiness.

Preconditions for a future replan

• Explicit maintainer release authorization after Zero Cloud feat(cli): change default model ceiling to opus #28.
• Fresh audit of stable local behavior, security evidence, supported limitations, rollback/fix-forward plan, package/image provenance, and current product policy.
• A new issue-body update closing the exact public command surface and release notes. This body is not sufficient implementation authority.

Non-goals now

All code changes, command registration, packaging, documentation, publication, tagging, release creation, or changing npm dist-tags.

Blocked by

• Explicit maintainer authorization not yet granted.
• Zero Cloud feat(cli): change default model ceiling to opus #28 private certification evidence.