Hongming Wang ec78c7637b docs(workspace-runtime): clarify what the boot-smoke gate does NOT prove ... A green gate means imports are healthy enough that executor.execute() reaches its body. It does NOT prove that execute() produces the right output: adapters with real I/O inside execute() (subprocess to a gateway, httpx call upstream) time out under the 5s harness window, and the gate treats a clean timeout as success. Surfaced while running publish-image across all 8 templates: the openclaw smoke "passed" with timing-out behavior in execute() because OpenClawA2AExecutor proxies to a subprocess that doesn't exist in the smoke env. Reading the green check, future operators might over-trust it as a runtime-correctness signal — it isn't. Add a "What the gate does NOT prove" subsection so readers don't mistake the import-regression coverage for an integration test. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-30 23:54:57 -07:00
..
blog	post(blog): "Why You Need a Team of AI Agents, Not One Genius Model"	2026-04-24 18:19:28 -07:00
docs	docs(workspace-runtime): clarify what the boot-smoke gate does NOT prove	2026-04-30 23:54:57 -07:00