test: cover raven 1.0 acceptance cases across session/providers/logging/tui

[JasonJarvan]

Summary

Automated test coverage for the automatable rows of the Raven 1.0 acceptance test set (Confluence page "Raven1.0 special test"). Tests only — no product code changed.

Python:

• Session: fork empty-source CLI nonzero exit; live-task cancel via SubagentManager.cancel_by_session; /stop dual-dispatch pin (scheduler + subagents); tui_rpc stub absence pins (no per-task progress endpoint, no single-task stop).
• Providers: registry count (19) + pinned name set + 4 backend classes; anthropic wire-format keys; codex responses-endpoint shape; bedrock warning-suppress stub with no converse path.
• Logging: no logs subcommand pin; no opentelemetry dependency pin.

ui-tui:

• TodoPanel render / completed-total count / status glyph / collapse; input-history store; @-path completion.

Rows describing superseded behaviour are deliberately not asserted, because current main refutes them and existing tests already pin the corrected behaviour:

• session lock-free write / data loss (writes take a cross-process advisory lock and append),
• single global lock serializing all sessions (per-conversation lanes + independent semaphore pools),
• tui_rpc todo server-push (no todo tool is emitted by the RPC server),
• external-editor fill-back (editor content is submitted directly on exit).

Type

• Fix
• Feature
• Docs
• CI / tooling
• Refactor
• Other (tests only)

Verification

Ran in a clean worktree built with uv sync --extra channels --extra tools and a real npm ci + hermes-ink/ui-tui builds:

• uv run pytest <10 touched files> -> 169 passed

• uv run ruff check <10 touched files> -> all checks passed

• ui-tui npx vitest run <3 touched files> -> 42 passed

• ui-tui tsc --noEmit -> clean

• Re-run green after rebase onto latest origin/main.

• Relevant tests pass locally

• Relevant lint / type checks pass locally

• User-facing docs or screenshots are updated when needed

Risk

• Security impact considered (tests only, no runtime or dependency change)
• Backward compatibility considered (no product code touched)
• Rollback path is clear for risky changes (revert the single test commit)

Related Issues

N/A