1.9.0

Every toolkit workflow now reports product telemetry, not only app creation, and a host-side hook makes sure a session is counted even when the agent forgets to. Edit, migration, mobile-conversion and branding runs were invisible to usage analytics; this release makes them countable with the same opt-in consent, the same privacy rules and no change to how you work. It requires clio 8.1.0.119 or newer (dotnet tool update clio -g).

📊 Telemetry for every flow

• One stage vocabulary for all workflows (#96). Agents report the same stages for every flow (workflow_started, plan_approved, build_started, work_item_completed, workflow_completed, ...) plus a workflow field naming the flow, so app maintenance, Classic to Freedom migration, mobile page conversion and branding land in the same funnel as app creation. The vocabulary is owned by clio (get-guidance name=product-telemetry); the toolkit only says where each flow emits and what counts as a unit of work.
• A guaranteed floor on Claude Code. A small hook runs after the first clio MCP call of a session, records one session-start event and reminds the agent which session id and toolkit version to report. It is also registered for the prompt and response events, which Claude Code fires in every project; in a session that never calls clio it returns at once and writes nothing. Cursor gets the same rules through an always-applied rule the installer writes, Codex through AGENTS.md; Copilot CLI has the skills only.
• Session cost is reported from the host's own transcript, once per response, as the real total rather than a guess made inside the run.
• Consent and privacy are unchanged. Nothing is sent before you grant telemetry consent, the hook never answers that question for you, events carry no prompts, generated content or credentials, and withdraw-telemetry-consent turns everything off at any time.

🛠️ Fixes

• clio installed under C:\Program Files is found again (#96). A CLIO_CMD path with spaces was split at the space and clio was reported as missing on the default Windows install location.
• An older clio degrades quietly. If the installed clio does not accept the new vocabulary, the toolkit reports nothing for that run and writes one diagnostic line naming the cause; upgrading clio restores reporting.

---