Question
How does the Run Projection carry a Turn whose history grows while it runs, instead of one replaceable preview, so assistant text settles in place and durable rows arrive mid-Turn? Decide message identity, which rows become durable when, how Steer state, Turn duration and the interrupted mark, Entry Turn authorship, and Agent-call rows reach the Projection, and which of these facts headless gains within its frozen --json shapes.
Also settle per-call live command preview budgets and coalescing, retention of supplied partial output when a Turn is interrupted or lost, reconciliation with final native output, placement of Turn-scoped cumulative diffs, and exposure of reported-only context and usage. Keep terminal facts distinct from replaceable previews and command panels bounded by default.
Question
How does the Run Projection carry a Turn whose history grows while it runs, instead of one replaceable preview, so assistant text settles in place and durable rows arrive mid-Turn? Decide message identity, which rows become durable when, how Steer state, Turn duration and the interrupted mark, Entry Turn authorship, and Agent-call rows reach the Projection, and which of these facts headless gains within its frozen
--jsonshapes.Also settle per-call live command preview budgets and coalescing, retention of supplied partial output when a Turn is interrupted or lost, reconciliation with final native output, placement of Turn-scoped cumulative diffs, and exposure of reported-only context and usage. Keep terminal facts distinct from replaceable previews and command panels bounded by default.