midstream 0.2.0

Real-time LLM streaming with inflight analysis
Documentation
# NNNN — Short, declarative title

- **Status:** Proposed | Accepted | Deprecated | Superseded by [NNNN]./NNNN-…
- **Date:** YYYY-MM-DD
- **Deciders:** @name, @name
- **Tags:** workspace, transport, security, perf, … (pick 1–3)

## Context and Problem Statement

One or two paragraphs. What is the situation? What forces are in play?
What problem are we deciding how to solve? Keep it factual — link to code
or prior ADRs instead of restating them.

## Decision Drivers

- Driver 1 (e.g. "publish path to crates.io must stay open")
- Driver 2 (e.g. "compile time on a clean target/ must stay under N minutes")
- Driver 3 …

## Considered Options

1. **Option A — short name.** One paragraph describing the option.
2. **Option B — short name.**3. **Option C — short name.**
Each option must be a real alternative, not a straw man.

## Decision Outcome

**Chosen option: "Option B — …"** because <single most important reason>.

### Positive consequences

- -
### Negative consequences

- … (yes, you have to list these — every decision costs something)
-
## Implementation notes (optional)

Concrete next steps, with file paths where possible. Not a substitute for
a real implementation PR, just a hand-off pointer.

## Links

- Supersedes: <ADR or "none">
- Superseded by: <ADR or "none">
- Related: <ADRs, RFCs, issues, PRs>