Task · SKT-0030

Make the clean-container deployment path executable from shipped instructions

Description

SKT-0011 scenarios A1, A2, A6, C2, H1, and H3 found that a public clean clone cannot reach the documented Compose and verification outcomes without outside knowledge. The path omits an end-to-end action, required tool names and minimum versions, numeric Grafana sink-identifier discovery, gcx/context setup, and the socket-mounted state-directory behavior; literal execution failed on missing just, unsupported just syntax, missing bash/python3/gcx, sudo absence, and state-volume permissions.

Acceptance Criteria

Definition of Done

Implementation Plan

Lane A owns the clean-container mechanism and shipped setup documentation; root applies task-surface wiring and runs Docker evidence after all lanes return.

Implementation Notes

2026-08-30 closeout: just clean-container completed from a public clone with Compose v5.4.0; final just check, just dump, just e2e, and exact rc.38 published-e2e all exited 0.

Final Summary

Delivered and executed the documented public-clone-to-healthy-Compose route, including tool discovery, identifier guidance, rootless state preparation, and the clean-container regression.

References

View the source file on GitHub