diff --git a/artifacts/ToolboxStack/toolbox-base/PROMPT b/artifacts/ToolboxStack/toolbox-base/PROMPT
index fe8bc13..1957c92 100644
--- a/artifacts/ToolboxStack/toolbox-base/PROMPT
+++ b/artifacts/ToolboxStack/toolbox-base/PROMPT
@@ -7,8 +7,8 @@ Context snapshot (toolbox-base):
 - Mounted workspace: current repo at /workspace (rw)
 
 Current state:
-- Dockerfile installs shell tooling (zsh/bash/fish with Starship & oh-my-zsh), core CLI utilities (curl, wget, git, tmux, screen, etc.), build-essential + headers, aqua, and mise; aqua now provisions gh, tea, lazygit, direnv, git-delta, and zoxide, with direnv/zoxide hooks enabled for all shells (direnv logging muted).
-- aqua manages CLIs (gh, tea, lazygit) via docs/TOOLS.md inventory.
+- Dockerfile installs shell tooling (zsh/bash/fish with Starship & oh-my-zsh), core CLI utilities (curl, wget, git, tmux, screen, httpie, bc, etc.), build-essential + headers, aqua, and mise; aqua now provisions gh, tea, lazygit, direnv, git-delta, zoxide, just, yq, xh, curlie, chezmoi, shfmt, shellcheck, and hadolint, with direnv/zoxide hooks enabled for all shells (direnv logging muted).
+- aqua-managed CLI inventory lives in README.md alongside usage notes.
 - mise handles language/tool runtimes; activation wired into zsh, bash, and fish.
 - docker-compose.yml runs container with host UID/GID, `sleep infinity`, and docker socket mount; run via run.sh/build.sh.
 - Devcontainer config ( .devcontainer/devcontainer.json ) references the compose service.
diff --git a/collab/SupportStack/BuildTheStack b/collab/SupportStack/BuildTheStack
index 58373dc..3ea9ed0 100644
--- a/collab/SupportStack/BuildTheStack
+++ b/collab/SupportStack/BuildTheStack
@@ -187,6 +187,9 @@ Create a proof of concept with docker-socket-proxy, homepage, and wakaapi compon
 - Maintain running status reports in collab/SupportStack/STATUS.md
 - Use git commit heavily to track progress
 - Push to remote repository whenever a component is fully working/tested/validated
+- Check Docker logs for all containers during startup and health checks to identify issues
+- Monitor container logs continuously for error patterns and failure indicators
+- Implement log analysis for common failure signatures and automatic remediation
 
 ## Autonomous Operation Requirements
 - Project must be capable of running unattended for 1-2 days without manual intervention