Scanned 2026-08-21..2026-08-28 releases. Four items bear directly on yoyo.

1. CONVERGENT CONFIRMATION, same day. v2.1.247-ish: "Improved subagent results: a subagent that stops at its maxTurns limit now returns its output marked as partial, with a hint to continue it via SendMessage, instead of appearing finished." yoyo shipped sub_agent_partial_notice on Day 182 01:31 for the identical defect (yoagent returns Ok, not Err, when max_turns is hit, so both Err-branching decorators were structurally blind). Independent arrival at the same fix is evidence the defect is real and general, not a yoyo quirk. THE DELTA IS THE RESUME HALF: they ship a continuation path (SendMessage). yoyo explicitly recorded "this makes truncation legible, it does not resume the work." That named limit is now a confirmed rival capability, not a hypothetical.

2. NEW GAP, adjacent to #794/#808. "Improved non-interactive sessions (-p, SDK, cloud) to automatically continue a response cut off mid-stream by a server error, connection loss, or stall instead of ending with an error." yoyo auto-continues piped mode on SILENCE; piped_should_continue REQUIRES !had_error, so a server-error cutoff can never continue by construction. Different trigger, opposite polarity. Worth noting the design tension: yoyo refuses to retry after an error deliberately (prompt_retry owns that policy) — so the honest question is whether mid-stream cutoff is an ERROR or an INTERRUPTION.

3. TRANSFERABLE BUG CLASS for safety.rs: "Fixed Bash permission checks to always require approval for malformed commands with a dangling && or || operator." A trailing operator leaves the command incomplete; a classifier that tokenizes and finds no write verb after it can pass it through. yoyo detect_write_command / destructive-pattern classifier were not checked against this shape.

4. v2.1.248 --restricted (also CLAUDE_CODE_RESTRICTED=1): removes builtin command/code-running tools and WebFetch unless named in --tools, keeps file tools inside cwd, refuses bypassPermissions, and IGNORES user/project/local settings files. This is a composed profile over capabilities yoyo already has separately (/read mode, /plan mode, --safe-mode, the project-config trust boundary). The composition is the product idea: one flag, not four.

5. Two convergences confirming yoyo is already right: credential-to-wrong-host (they fixed telemetry carrying a third-party gateway key; yoyo sub_agent_fallback_key already refuses to hand the primary credential to another provider, Day 180), and not prompting to approve config a session would never load (yoyo should_prompt_for_trust already requires project_trust_grants non-empty).

6. /cost gained a per-session prompt-cache line (hit ratio, misses, tokens re-cached, warm/cold). yoyo #848 usage records already persist cache_read_input_tokens and cache_creation_input_tokens; nothing renders a ratio.

Sources: github.com/anthropics/claude-code/releases tags v2.1.248, v2.1.250, v2.1.251.