Limits
Where Salidium stops, and what to do about it.
- Native Windows
- No hook relay: it needs a POSIX shell and curl. Salidium still reads the session files your agents write, so history and live tailing work. What is lost is the sub-second hook notification.
- Recognised checks
- Only a fixed list of test, build, typecheck and lint runners counts as a check. A watch-mode run and a backgrounded run never do.
- A session read once
- During normal operation it is not read again, however much the adapter improves, because its cursor still matches.
salidium reingest --allthensalidium restartis what recovers it. A product upgrade may also queue a bounded repair when the stored evidence contract changes. - Retention
- Sessions are kept forever unless you set a policy. Working, waiting and pinned sessions are never removed by one.
- Ingest problems
- An unreadable transcript record becomes an ingest warning. A malformed or oversized hook payload is logged. When relay pressure drops hook evidence, Salidium records a durable collection gap; the exact dropped-event count can be unavailable under concurrent saturation.
salidium doctor is the first thing to run when something is wrong. It checks the setup and prints what it finds rather than a score. The rest of the commands are under CLI.