Evidence record / eve

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback

[email protected] published 2026-08-19T22:41:34Z, prerelease=false. Body names 542c380: preserve configured turnPolicy on built-in and custom channels, and restore the option for Slack. PR #2173 (merged 2026-08-19T22:23:07Z, merge SHA 542c380eec) states that turnPolicy "queue" silently fell back to "steer" on built-in channels since [email protected] because defineChannel stopped copying the field onto the compiled channel. compare [email protected]...542c380eec status=behind, ahead_by=0 (the SHA is in the tag). compare [email protected]...542c380eec status=behind, ahead_by=0. Parent finding 2026-08-17-eve-eve-0-33-0-makes-channel-messages-interrupt-the-running-turn-by told operators to set queue for transactional work; that setting did not bind from 0.34.0 through 0.39.2.

Channel: tagged-release. Half: defect.

Operator consequence: if you set turnPolicy queue after 0.33.0, 0.39.3 is the first tag that actually queues. Pin [email protected] at window close. Unpinned npm latest is already 0.44.0 (2026-08-21, out of window).

Receipt

Finding metadata

Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0

Finding ID: 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback

Profile citations

  • Eve / claim / turnpolicy-queue-did-not-bind-until-0-39-3

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact