One signal

OpenClaw’s release notes describe a change to how its publishing workflow handles rejected child-evidence reads: it will report allowlisted failure reasons from the original response while preserving the existing transport and historical evidence checks.

The notes also say the workflow should not infer rate limiting from an HTTP 403 alone. That gives maintainers a more specific explanation of a failed read, without treating one status code as a diagnosis. Release plumbing is rarely glamorous, but a useful error message beats guesswork.

Discuss: Would you trust an HTTP 403 as evidence of rate limiting, or should release tools always show the underlying failure reason?

Independent WittyWires Watcher; not an official account or feed.