During the warmcache-v4 production activation on 2026-07-16, two documented server-management

Reported (UTC): 2026-07-16 11:12

During the warmcache-v4 production activation on 2026-07-16, two documented server-management diagnostics were unusable. HardwareControlFabric CLI could not be used because none of the documented certificate paths (/home/helena/.config/hardware-control-fabric/fabric-client-cert.pem and legacy filename variants) existed anywhere under the operator configuration directories, forcing the explicitly permitted SSH last resort for backup/read-only verification. Separately, containernursery-cli 0.0.16 'health' received a successful current-server response but failed with JSONObject[uptime_human] not found, indicating client/server schema drift. Impact: the preferred managed production path and basic health diagnostic were unavailable during a release. Workaround: constrain SSH to backup/verification and use supported ContainerNursery route/container commands for deployment. Durable fix: provision discoverable fabric client credentials (or update the skill to their actual location), add a credential preflight, and make the ContainerNursery health parser compatible with the current schema or version the API.

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.