TechGoblin 1.0.0 - support status and known limitations

Released for supervised homelab maintenance. Support reflects tested configurations, not certification of every platform or unattended production reliability.

CONFIRMED WORKING IN OUR TESTED HOMELAB
Central target inventory, agent connectivity and CPU/RAM reporting where provided; Windows and Ubuntu/Debian agent health, OS scans and update execution; independent server/game selections with Steam before OS when both selected; per-target results and diagnostics; separate ordinary-host and appliance maintenance lanes.
These features have local regression coverage and/or successful homelab use. Correct privileges, current compatible agents and target configuration are required. Interrupted maintenance recovery remains Beta.

BETA / BETA / STILL BEING TESTED
Proxmox Beta: cluster/node/guest visibility, health and scans have been exercised. Rolling host updates, HA handling, guest shutdown/restoration, reboots and recovery require supervised testing with backups and native console access.
TrueNAS Beta: API connectivity and health exercised on SCALE. Updates/rollback are subject to vendor safety prerequisites. CORE compatibility is not confirmed; SCALE testing does not establish CORE support.
Steam Beta: selected Windows/Linux SteamCMD setups exercised. Game-specific service lifecycle, save backup/restore and authoritative remote-build comparisons require validation. Unknown or local-only evidence is not proof a game is Current.
Recovery Beta: original job identity and saved evidence help prevent duplicate actions. Automatic continuation is not guaranteed.
Additional package builds (Linux ARM64/musl and macOS) are experimental distributions, not native-runtime certification. Windows/Linux clean install and upgrade acceptance remains incomplete.

KNOWN LIMITATIONS - READ BEFORE MAINTENANCE
An unresolved leased job can block another update, agent upgrade or reboot. A healthy machine or fresh heartbeat does not prove the earlier update ended. Save the diagnostic capture and match the original job to endpoint/native updater evidence. Do not delete receipts, clear leases by age, or retry an installation to bypass the guard. This release does NOT automatically repair legacy stuck jobs or provide an emergency-reboot bypass.
Agent activity tracking shows phases, original IDs and last signals rather than invented percentages. Stale activity is not proof work stopped. Deployment tracking survives page reloads but not controller restarts; upgrade jobs can be redisplayed from durable endpoint records. Redisplaying a job is not automatic workflow resumption.
Use backups, a maintenance window and native management access. Avoid unsupervised blanket updates on important systems while recovery is under validation.
Release manifests use the pinned StrykerLabs ECDSA key and exact installer SHA-256. This is not Windows Authenticode signing; Windows may show Unknown Publisher.

FUTURE SUPPORT
Have a platform, game, service manager or workflow you need? Tell us what you run, what you want to do and how you manage it today: hello@strykerlabs.us. We will investigate whether it can be supported safely. Requests guide development, not guaranteed features or delivery dates.
Support the workshop: https://ko-fi.com/jeffmurawski