[0xKT]

Summary

raven.cli.commands.run hard-exited past interpreter finalization whenever lancedb's LanceDBBackgroundEventLoop thread was live. That thread cannot exist in this process: lancedb is a transitive dependency only, nothing under raven/ imports it, memory talks to everos over HTTP, and everos runs out-of-process. torch, named alongside it in the agent-loop comment, is neither declared nor imported either. The probe returned False in every configuration, so the branch was unreachable.

Removed the probe in _exit.py, the if it fed in commands.py, and the comment in agent_commands.py claiming the exit chokepoint covers that hazard.

flush_and_hard_exit stays: tests/conftest.py calls it on CI, where a fully green suite was observed exiting 139 on Linux. Its module docstring now describes that caller instead of the lancedb story, and records why the gate went.

Deleting the whole except SystemExit block is behaviour-preserving. With the probe always False it reduced to except SystemExit: raise, and the exit-code normalization inside it only ever fed the hard-exit call -- never the re-raised exception.

Type

• Others

Dead-code removal in the CLI exit path, plus the two tests that exercised the removed probe.

Verification

CliRunner invokes the Typer app directly and never reaches run(), so the console-script entry point was smoked by hand:

raven --version                 -> 0
raven skill get (missing arg)   -> 2
raven nosuchcmd                 -> 2
raven status                    -> 0
unparseable ~/.raven/config.json -> one clean warning line, no traceback

uv run --all-extras pytest -q
# 4653 passed, 13 deselected   (4655 before: the two probe tests are gone,
#                               the four covering flush_and_hard_exit remain)

bash .claude/scripts/preflight_ci.sh
# ALL PREFLIGHT CHECKS PASSED

Also grepped the whole repo, including benchmarks/ and scripts/, for lancedb_finalization_hazard and LanceDBBackgroundEventLoop: no references remain.

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

Risk

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

The change is a deletion in a path no test host reaches, so the console-script smoke above is the real verification rather than the suite. If an embedded local-lancedb mode ever lands, the guard would need reinstating -- deliberately, and against a probe that can actually fire.

Related Issues

Closes #232