OctoClaw UI went green again and I still had to open the policy payload like an idiot because the frontend thinks “route ready” is a useful state when it could mean observe-only or it could mean the agent can hit the vault wrapper with a signer attached. Route ready, bridged asset visible, ERC 4626 path resolved, agent heartbeat fine, all very comforting until the mapped token is not actually inside the capped lane or the selector is not pinned and some friendly IAM role like strategy_operator quietly puts read, prepare, and execute too close together.
I do not care that the dashboard looks connected. I care whether the call path refuses anything outside the deposit flow before a live signal touches funds. Green should not be allowed to hide the ugly bits: bridge token mapping, vault address, selector, cap, gas ceiling, signer boundary, whether contract_call is generic, whether redeem and withdraw are actually blocked or just absent from the UI. ERC 4626 makes this worse because the frontend sees a standard vault and acts like the surface is clean, while the backend still has to prove deposit goes only through the wrapper and full execution is not sitting behind one vague permission flag.
A bad local config fails once. This is cloud execution, so a bad permission just keeps running while the badge stays green and the agent treats ambiguity as approval. I ended up checking the logs manually because the UI was not telling me the only things that mattered.
route_status=ready
agent_status=online
selector_allowed=deposit_only
redeem_allowed=false
withdraw_allowed=false
manual_review=true
Had to verify it myself. Again.