Update integrations for current core releases

[rlippmann]

Summary

Update the example integrations for the current Context Compiler core releases:

• Python context-compiler 0.8.3
• TypeScript @rlippmann/context-compiler 0.8.2

This removes reliance on the deleted transcript replay APIs and updates affected integrations to use explicit authoritative continuation:

• TypeScript starter apps now use checkpoint restore plus the current input only. Historical chat messages remain downstream context and do not reconstruct compiler state.
• LiteLLM Proxy hooks now support checkpoint-backed continuity without deriving authoritative state from request history.
• LiteLLM defaults to stateless current-turn processing. Persistent mode is explicit and requires a supported session key.
• The Directive Drafter LiteLLM path restores checkpoint state first, drafts only the current turn, and bypasses drafting while a clarification is pending.
• Core dependency declarations, lockfiles, and applicable Open WebUI metadata are updated to the current released core versions.
• LiteLLM fallback decisions use the current DecisionKind.PASSTHROUGH representation.

Why

The current core releases removed transcript replay APIs in favor of explicit engine.step(...) sequencing and checkpoint-based continuation.

Several integrations still depended on the removed replay surface. Recreating transcript replay locally would continue treating host message history as authoritative state and would preserve problematic replay semantics around pending clarification.

This update aligns the integrations with the current core architecture:

• authoritative continuity comes from host-owned checkpoints;
• historical chat messages are not used to reconstruct compiler state;
• stateless integrations process only the current user turn;
• persistent LiteLLM usage restores and saves checkpoints explicitly.

Example metadata

• Enforcement point: Multiple existing integration enforcement points
• Domain: Integration compatibility and state continuity
• Technology/runtime: TypeScript starter apps, LiteLLM Proxy, Open WebUI, Python and TypeScript
• Example type: starter app / reference integration / repository maintenance
• Does this use directive drafter? yes, in existing Drafter variants
• Does this derive state from model output? no

Checklist

• Repository scaffolding / governance change
• One primary enforcement point
• Explicit authoritative state
• No model-derived state mutation
• Adversarial stub or equivalent test
• Observable runtime behavior change
• Domain vocabulary is natural
• Framework is secondary to the enforcement point
• Docs updated
• Tests/smoke checks added where practical

Notes

LiteLLM continuity modes:

• stateless is the default and processes only the latest user turn.
• persistent is explicit and requires either:
  • context_compiler_session_key
  • metadata.context_compiler_session_key
• The included in-memory checkpoint store is reference-only and is limited to a single process. It is not durable across restarts and does not provide multi-worker coordination.

Validation:

• ./scripts/validate_python.sh — passed (201 passed, 6 skipped)

• ./scripts/validate_typescript.sh — passed

• Focused LiteLLM tests — passed (25 passed, 4 skipped)

• Markdown lint — passed during the compatibility work

• OpenWebUI v0.9.2 live validation with Ollama qwen2.5:14b-instruct — passed

  • updated and loaded the published non-Drafter context_compiler_pipe
  • runtime installed context-compiler 0.8.3
  • local directive update verified with llm_called: no
  • checkpoint/state continuity verified across turns
  • downstream Ollama passthrough verified with state_injected: yes
  • clarification blocked downstream forwarding
  • no resolved and cleared pending clarification