Improve setup feedback, service integration and production guidance for 0.1.9

[overlordkim]

Long-running setup and provider failures left agents without enough information to explain progress or choose the next action. This release exposes preparation activity and log locations, preserves project and Runtime context in CLI follow-up commands, and checks the selected HypiHub model and operation before transferring references.

Changes

• Keep local program preparation, process ownership and Worker state distinct. Repeated startup observes the existing loading process; stop results report what actually happened.
• Carry provider progress, public errors and request/task identifiers through execution. Use HypiHub's canonical model identities while preserving operation-specific inputs and pricing. Availability errors do not imply a payment problem or silently select a different model.
• Add explicit hypit version --check reporting without installing updates or opening a Runtime.
• Clarify first-use choices, HypiHub and user-owned service connections, explicit mirror configuration, intermediate previews, and active agent problem-solving. Document separate updates for the executable and Skill.
• Connect empirical image direction and a new presenter-led visual explainer playbook to the complete example's craft notes and component sources. Separate public Agent entry points from execution-service partners.
• Prepare @hypit/hypit@0.1.9; existing protocol identifiers remain @1.

Validation

• Local full suite passed during integration; subsequent HypiHub changes passed 61 provider tests, 16 CLI output tests and the repository type check.
• Documentation build, Skill validation and changed-page file links passed. The final documentation pass checked 112 links.
• Prepared npm tarball inspected for distribution contents; internal design notes, credentials, logs and video media are excluded.
• Live model and pricing checks were read-only. They do not establish paid-generation behavior for every account or input combination.

Publishing the stable v0.1.9 GitHub Release after merge triggers the existing npm workflow. Updating main alone does not publish npm.