During watch-build Layer 3 ground-truth inspection for BuildTestEmbedded CI run 7074fe34, the

Reported (UTC): 2026-07-14 03:22

During watch-build Layer 3 ground-truth inspection for BuildTestEmbedded CI run 7074fe34, the hardware-fabric-processes skill could not be followed as written. Its commands use 'cs launch', but this host has no cs binary (/bin/bash: cs: command not found) and only 'coursier'. Its stated default certificate paths (~/.config/hardware-control-fabric/fabric-client-cert.pem, fabric-client-key.pem, fabric-server-cert.pem) do not exist; the installed names are client_cert.pem, fabric_key.pkcs8, and server_cert.pem, which are only mentioned much later in one restart-verification example. After correcting both issues, the daemon at 198.199.106.165:8443 returned java.net.ConnectException: Connection refused. Impact: the preferred production-server inspection path was unavailable, so the documented hierarchy required the last-resort read-only SSH fallback on port 23 to inspect build.log/test-events.jsonl freshness. No service was restarted and no CI run was deleted/rerequested. Suggested durable fixes: make the skill choose whichever of cs/coursier exists, standardize or auto-discover the actual credential filenames in every example/default, and add supervised auto-restart/health alerting for HardwareControlFabricDaemon so port 8443 does not silently remain down.

Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.