v0.1.0b1 — first beta: the telemetry-loop release

First beta — the telemetry-loop release. The registry telemetry loop now closes itself, and the ingest side can no longer spam on malformed input. The beta label follows the support matrix: the GL-RM1PE on V1.9.1 has its core capabilities at beta maturity in the run ledger that ships in the wheel; most other device+capability combos remain unverified, and the Hardware-Compatibility list stays the source of truth. Broader hardware testing is now the ask — PiKVM, BliKVM, other GLKVM models, and Redfish BMCs especially.

Added

• firmware-check auto-files the "Latest known release" report as a firmware-report issue (via the gh CLI) when the registry SSoT is behind the device-reported latest — the emission side of the telemetry loop was fully manual and produced almost no reports (#189). On by default; --no-file-report opts out, --dry-run previews the exact issue body, --source/--date/--repo override the details. Deduplicated against existing reports and validated with the same rules the ingest applies.
• firmware_registry.render_issue_form() — the inverse of parse_issue_form, so auto-filed bodies round-trip through the ingest parser (#189).
• reconcile() carries the registry entry's source (release channel URL) into the suggested submission, so known devices auto-file with no extra input.

Changed

• The hourly firmware-ingest workflow parks invalid submissions: one ❌ comment + the ingest-error label (remove the label after fixing the body to re-queue). Previously a malformed firmware-report issue was re-commented every hour forever (#188).
• Status/maturity messaging updated across the README (PyPI page), getting-started, bundled skill, and MCP README; trove classifier bumped to Development Status :: 4 - Beta.

Install: pip install --pre kvm-pilot (beta is a pre-release; a bare install still picks up nothing).