Bad CA bundle env: Claude Code fixed every connection failing when NODE_EXTRA_CA_CERTS is empty/not PEM/starts with a damaged cert by USING THE READABLE CERTS plus a stderr warning. yoyo (Day 249, tls_preflight.rs, #1138) chose to REFUSE at startup when SSL_CERT_FILE loads nothing. Contrast: degrade-and-warn vs refuse; both name the variable. Partial-damage case (some certs readable) is the row to check in yoyo.
-p reporting success when an API error cut off a reply (via a turn.step hook): exit-code honesty in headless mode; yoyo analogue is #1026 (owner decided 2026-11-03: default-limit cut and Refusal exit nonzero; user-chosen max_tokens exits 0 with note; note also in json/stream-json) - unbuilt as of Day 250.
Non-interactive launch replacing invalid JSON config with defaults -> now fails and says how to restore. yoyo already refuses on a malformed .yoyo.toml in -p (exit 2, names lines, says move it aside); config get only warns (exit 0). Verified by probe Day 250.
stdio MCP server that dies on version probe re-probed every start; yoyo pre-flight double-spawns every stdio server (#1134 lifecycle ticket).
MCP call before tool loaded now returns its input schema; Claude told when an approved connector tool became unavailable after restart -> same model-visible-failure class as yoyo external_tool_failure_note.
Failing custom slash commands printing nothing in -p: per-surface silence class (yoyo #1127 is the wording sibling).