zidane 7.0.15 → 7.0.17

package/docs/HEADLESS.md

@@ -13,6 +13,11 @@ Two entry points, one contract:
 - **CLI** — `bun run headless` (`src/headless-cli.ts`). Language-agnostic; spawn
   it per rollout and parse stdout. Emits `stream-json` like `claude -p`.
 
+Contents: [In-process](#in-process) · [CLI](#cli) ·
+[Reusable output helpers](#reusable-output-helpers) ·
+[Transcript formats](#transcript-formats) · [RL rollouts](#rl-rollouts) ·
+[Known integration checks](#known-integration-checks-real-model--vllm)
+
 ## In-process
 
 ```ts

package/docs/INTERACTIONS.md

@@ -12,6 +12,12 @@ the matching `tool_result` block follows in the next user turn. There is
 no parallel store, no migration, no extra schema. Resume-from-disk is
 just `pendingInteractionsFromTurns(session.turns)`.
 
+Contents: [How it works](#how-it-works) · [`present_plan`](#present_plan) ·
+[`ask_user`](#ask_user) · [Keyboard](#keyboard) ·
+[Persistence guarantees](#persistence-guarantees) ·
+[Smoke-test checklist](#smoke-test-checklist) ·
+[Public API](#public-api-for-gui-consumers)
+
 ```
 agent calls present_plan / ask_user
         │
@@ -119,29 +125,22 @@ In the question wizard (multi-question batches):
 ### Sizing
 
 The wizard is content-sized inside a ceiling, and all three numbers come from
-the terminal rather than from percentages of a parent:
-
-- **Ceiling** — `wizardMaxRows(terminalRows)`, roughly 75% of the terminal,
-  never below 8 rows and never within 8 rows of the top so some transcript stays
-  visible. It used to be a `maxHeight: '60%'`, which resolves against the
-  parent's height; the wizard's parent is content-sized, so Yoga had nothing to
-  take 60% of and the cap silently never applied — the shell grew to whatever
-  its content estimate claimed and drew its border there, leaving questions
-  rendered below a closed frame.
+the terminal rather than from percentages of a parent (the wizard's parent is
+itself content-sized, so a percentage of it has nothing to resolve against):
+
+- **Ceiling** — `wizardMaxRows(terminalRows)`: roughly 75% of the terminal,
+  never below 8 rows, and never within 8 rows of the top so some transcript
+  stays visible.
 - **Content height** — `introRows` + `estimateQuestionRowHeight` per question,
-  both **wrap-aware** (`wrappedRows`) and both given the panel's content width.
-  They previously counted `\n` only and ignored choice descriptions, so any
-  wrapped markdown intro or wrapped description under-sized the panel.
-- **Floor** — the shell takes `minHeight` equal to the rows its content needs.
-  The shell is `flexShrink: 1` (it was `0`, which is why it could neither cap
-  nor shrink), and shrinkability alone let a `flexGrow` transcript sibling
-  squeeze the form to a fraction of its content; the floor makes the transcript
-  yield instead.
-
-The height is also **monotonic**: answering a question collapses its row to a
-one-line summary, which would otherwise shrink the panel mid-form. A high-water
-mark keyed by request id means the panel settles at the largest size it has
-needed and stays there.
+  both wrap-aware (`wrappedRows`) and given the panel's content width, so a
+  wrapped markdown intro or choice description sizes the panel correctly.
+- **Floor** — the shell's `minHeight` equals the rows its content needs, and
+  the shell is `flexShrink: 1` so a `flexGrow` transcript sibling yields to it
+  instead of squeezing the form.
+
+The height is also **monotonic**: it's computed as the max over every possible
+`activeIndex` up front, in one pass, so the panel is sized for its tallest
+state on the first frame and never grows or shrinks as you answer questions.
 
 In the plan picker: