v0.3.0 — doctor preflight tool

New tier-0 doctor tool: one-pass environment preflight with a remedy for every failing check.

• Vendor toolchains: tizen/sdb and ares-* presence + versions
• Signing: classifies each Tizen certificate profile — Samsung-issued (installs on real TVs) vs the generic SDK distributor cert (emulator only, real panels reject it)
• Devices: TCP reachability per configured TV with platform-specific remediation (dev-mode/Host-PC-IP for Tizen, 50h Dev Mode expiry for webOS)
• webOS passphrase env vars and stored pairing tokens

Validated against a live environment: correctly identified the exact generic-cert and unreachable-TV failures from the original hardware test session.

v0.2.3 — prerequisites & device-setup docs

Docs release: README Prerequisites table (machine toolchains, one-time TV setup, signing, network per platform) and a new device-setup docs topic served over MCP — including the multi-homed host-IP trap from real-hardware testing. Tizen connect errors now point at it. Android TV driver on the roadmap (#1).

v0.2.2 — real-hardware fixes (Tizen 9, HG hospitality)

First real-device validation, on a Samsung HG32F800 hospitality panel (Tizen 9):

• install now uses sdb push + vd_appinstall (tizen CLI fails silently on TV firmware); certificate rejections surface the actual reason + DUID remedy
• debug launch is idempotent: kills a running instance (by pkgId — pkgcmd doesn't accept full app ids), clears stale port forwards, 30s timeout
• docs: HG hospitality panels disable the consumer IP-remote service, so remote_key uses the eval_js synthetic-KeyboardEvent fallback there (verified: app receives the keys)

Verified end-to-end on hardware: connect, package/sign, install, debug launch, CDP screenshot, console capture, eval_js, synthetic key input.

v0.2.1

Maintenance release validating the fully automated OIDC publish pipeline (npm trusted publishing + MCP Registry). CI fixes: checkout@v5, idempotent npm publish step.

v0.2.0 — remote-key pairing

Remote-control key injection now works on both platforms with one-time on-screen pairing:

• Samsung (Tizen): remote WebSocket API on :8002, token persisted to ~/.tv-mcp/state.json
• LG (webOS): SSAP register + pointer-input socket, client-key persisted
• Structured errors guide re-pairing after TV factory resets

Full capability matrix in the README.