HardwareControlFabric skill uses unavailable cs launcher on this host.

Reported (UTC): 2026-07-15 11:56

What was being attempted: perform the read-only production process check required by watch-build after build-watchman reported growing build.log with zero test events.

What went wrong: the skill's Quick Usage and process examples invoke 'cs launch', but this execution host provides 'coursier' and no 'cs'; the exact failure was '/bin/bash: line 1: cs: command not found'.

Impact: the preferred HardwareControlFabric ground-truth check could not run verbatim and briefly delayed CI monitoring.

Workaround used: invoke the same artifact and arguments with 'coursier launch' instead.

Suggested durable fix: update hardware-fabric-processes/SKILL.md to use 'coursier launch' consistently or document a portable launcher-detection snippet that selects cs or coursier.

Production verification — 2026-07-17

Status: STILL EXISTS. The required mTLS files now exist, but no cs command is installed, the live CLI ping failed, and port 8443 refused connections. Read-only SSH confirmed that no HardwareControlFabric daemon process is running; its last log ends on 2026-07-12 amid Netty ByteBuf leak reports and thread growth from 88 to 108.

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.