ec78c7637b
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> |
||
|---|---|---|
| .github/workflows | ||
| app | ||
| audio | ||
| content | ||
| docs/marketing | ||
| lib | ||
| marketing/demos/snapshot-scrub | ||
| .gitignore | ||
| mdx-components.tsx | ||
| next.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.mjs | ||
| source.config.ts | ||
| tsconfig.json | ||