After a successful human-output create/show/list/ready, bd may append a "💡 Tip:" line chosen by a probability roll whose RNG is clock-seeded unless BEADS_TIP_SEED is set. run_scenario env_clear()s and passes only PATH/HOME/TMPDIR + BEADS_TEST_MODE=1, so on a host with ~/.claude (claude_setup tip eligible, p=0.6) every bd process rolled independently and out-of-scope human-output scenarios (create_human_readable_output, show_short_mode_text, show_multiple_short, ready_empty_no_issues_plain, ...) diverged main-vs-main. Pass BEADS_TIP_SEED=1214 to every step for both reference and candidate. Go math/rand's first Float64() for that seed is 0.0000159, so the highest-priority eligible tip always wins its roll. Where the host makes a tip eligible, it stays visible and lands on a deterministic step, so a change to which tip prints, on which step, or to its text (including a tip leaking into --json) still diverges instead of being normalized away. Where no tip is eligible (no ~/.claude, beads plugin enabled, or a `bd prime` hook) none prints and tip changes go unobserved; the README now says so. The new unit test spawns printenv through run_scenario. That races the existing stub-bd test, which writes its stub with std::fs::write and then execs it: a fork while the write fd is open makes the exec fail with ETXTBSY (rust-lang/rust#114554). Serialize both spawning tests on a SPAWN mutex. Agent-Signature: claude-code-claude-opus-5-5-unknown-reasoning on behalf of Julian Knutsen Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| hook_timeout_backends | ||
| integration | ||
| migration | ||
| oracle-a | ||
| regression | ||
| upgrade_smoke | ||