test: run the full unit suite in ci and fix revealed failures

[0xKT]

Summary

CI ran make test-python over 4 hardcoded files, so ~268 of 272 top-level test files never executed on any PR. A bare uv run pytest could not stand in for it either: collection aborted with 7 errors (channel-adapter tests importing optional SDKs at module level), and testpaths pulled tests/integration/ into every run.

This makes the whole unit suite the blocking CI gate.

• Makefile: test-python runs the whole unit tree instead of a hardcoded file list.
• ci.yml: the python job splits into lint-python and a unit job running the whole suite on ubuntu / py3.12; the matrix block is kept so more versions are one list entry away.
• pyproject.toml: register integration / e2e markers, enable --strict-markers / --strict-config, exclude tests/integration via norecursedirs, and default to -m "not integration and not e2e" so a bare pytest is safe.
• Guard the 7 channel-adapter tests with pytest.importorskip; CI installs --all-extras, so they run there rather than skip.
• Relocate 9 integration / real-resource files out of the flat unit tree into tests/integration/, renaming the token_wise benchmarks to the real_llm kind required by AGENTS.md section 5.2.

Turning the suite on surfaced 44 pre-existing failures, all fixed here:

• 29 from asyncio.get_event_loop().run_until_complete() in three producer test files, which picks up a closed loop once other async tests have run; now asyncio.run().
• 2 stale run_turn stubs missing the inline_tool_stream keyword the production callers pass.
• 12 from cross-test state leaking through raven.config.loader._current_config_path, litellm's global logging handlers, and an ambient dependency on a populated ~/.raven in the TUI init-error tests.
• 1 flaky concurrency test whose timing bound left only 0.05s of margin.

The full run also recovered 38 genuine unit tests under tests/tui/autotest that a directory-level exclusion would have orphaned; they are selected normally now, with the 24 subprocess-spawning e2e tests deselected by marker.

Deliberately out of scope: an integration / nightly CI tier (real-LLM runs are hard to make meaningful in CI and cost money -- to be designed separately), and the naming and assertion debt tracked in #223.

Type

• CI / tooling

Verification

uv run --all-extras pytest -q
# 4611 passed, 24 deselected in 193s

bash .claude/scripts/preflight_ci.sh
# ALL PREFLIGHT CHECKS PASSED (commitlint, large files, pre-commit, ruff, tests)

• Relevant tests pass locally
• Relevant lint / type checks pass locally

Risk

• Security impact considered
• Backward compatibility considered
• Rollback path is clear for risky changes

No production code changes -- test files, test configuration, and CI workflow only.

The repository ruleset currently declares no required status checks, so renaming the job blocks nothing. If the unit job should become a merge gate, add unit (py3.12 / ubuntu-latest) to the ruleset separately.

Related Issues

Closes #222