P1 backend: chat persistence, tc-llm providers, runtime loop, gateway SSE

- tc-db: sessions/messages/steps/runs/run_events repos (atomic seq assignment,
  history with ordered step traces, journal replay-from-offset); migration 0003
- tc-llm: provider-neutral ChatRequest/LlmEvent; ScriptedProvider (scenario
  TOML, word-level deltas, multi-turn tool legs — ships in production for
  e2e/air-gap smoke), AnthropicProvider (Messages SSE), OpenAiCompatProvider
  (vLLM/Ollama/llama.cpp); opt-in live tests via TC_LIVE_LLM=1
- tc-runtime: run loop with persist-before-emit event journal, real built-in
  clock.now tool, step rows on the reply message, tool-error resilience,
  broadcast channels for live attach
- tc-api: agent CRUD + settings/full (tenant-isolated, RBAC'd, audited),
  sessions create/list/history?tools=true, POST /api/gateway SSE with
  monotonic ids and exact resumeFrom journal replay (tested equal to live)
- teamclaw-server: config-driven provider factory

83 Rust tests green, all against real Postgres / real TCP.

Co-Authored-By: Claude Fable 5 <[email protected]>

crates/tc-runtime/src/lib.rs

@@ -0,0 +1,11 @@
+//! The agent run loop: takes a user message, drives the LLM provider,
+//! executes tools, and journals every event before any observer sees it
+//! (the gateway streams exactly this journal, live or replayed).
+
+mod events;
+mod runtime;
+mod tools;
+
+pub use events::{RunEventBody, RunEventEnvelope};
+pub use runtime::{Runtime, RuntimeConfig, RuntimeError, StartedRun};
+pub use tools::{ClockNow, Tool, ToolRegistry};