smoke-test

Run a post-restart smoke-test suite to validate container health and automatically apply fixes for known issues. This minimizes manual debugging and downtime by executing core checks and logging results to a temporary file.

You can run custom shell scripts alongside core health checks by placing them in the designated drop-in directory. This allows you to extend the smoke-test suite with user-defined validation logic without modifying the core skill.

The smoke-test suite reports validation failures by logging detailed results to a temporary file and exiting with a status code equal to the number of unfixed failures. This provides a clear count of remaining issues after auto-fixes are applied.

The best way to verify Inbrain and OpenClaw health is to execute the automated smoke-test suite, which runs 8 core tests specifically designed to check system status and apply auto-fixes after a container restart.

Yes, the post-restart health validation applies built-in auto-fixes to address known issues before reporting any failures. This reduces downtime by attempting to resolve common problems automatically during the smoke-test execution.

Invoke the post-restart smoke test by running the CLI command or by directly executing the shell script. This flexible invocation triggers the health validation, auto-fixes, and logging for your container lifecycle.