@junghanacs/entwurf 0.22.0 → 0.23.1

package/mcp/entwurf-bridge/dist/pi-extensions/lib/fresh-call-composition.js

@@ -0,0 +1,423 @@
+/**
+ * FRESH-CALL COMPOSITION — the part of opening a sibling that is the same wherever the
+ * sibling is placed.
+ *
+ * WHY THIS FILE EXISTS (#116 S2-a). A herdr rail opens the same five-backend dialect, hands the
+ * same first-turn framing and mints the same correlation nonce as the tmux rail — but it places
+ * the sibling with `pane split` + `agent start` rather than `new-window`, and it cannot inherit
+ * one line of tmux placement to get there. Leaving this composition inside `mux-fresh-call.ts`
+ * would have forced the herdr module to import that file, and that file imports tmux placement,
+ * the launch preflights and the Codex socket resolver. One import would have dragged the whole
+ * tmux rail behind it.
+ *
+ * SO THE FENCE IS THE POINT: this leaf imports NOTHING from `mux-*` or `entwurf-*`. Only the
+ * Node standard library. Anything a rail owns arrives as an explicit argument — the opening
+ * sentence that says where the sibling was placed, and the Codex socket path. Both are injected
+ * rather than resolved here, because resolving either one would re-open the coupling this file
+ * exists to close.
+ *
+ * WHAT DELIBERATELY STAYED BEHIND in `mux-fresh-call.ts`: placement, seat selection, runtime
+ * proof, the mutation-order safety argument, and the receipt type. None of those are shared —
+ * a herdr coordinate is not a tmux coordinate, herdr abandons pre-mutation runtime proof
+ * (#116 D1), and its two-step launch breaks the ordering argument outright.
+ */
+import { randomBytes } from "node:crypto";
+/** The backends this rail can open. Fixed set, not a profile — a further one is a decision,
+ * not a config entry. `copilot` was added by #82 RAIL 9, `omp` by #87 Bundle C, and `codex`
+ * by #95 after its system birth and app-server rails were measured. The set is joined to the
+ * citizen backends by `check-harness-admission-parity`: a harness that mints records but is
+ * missing HERE is not an unwired convenience, it is a release blocker. */
+export const FRESH_CALL_BACKENDS = ["pi", "claude-code", "copilot", "omp", "codex"];
+/**
+ * The callback tool NAME differs per backend and that is not cosmetic: native pi exposes the
+ * capability directly (`entwurf_v2`), while an MCP-hosted session reaches it under whatever
+ * name that harness composes. Naming the wrong one costs the whole first turn.
+ *
+ * `[측정]` Copilot CLI 1.0.80 composes `<mcpServerName>-<mcpToolName>` — NOT Claude Code's
+ * `mcp__<server>__<tool>`. Read from two independent sessions' own event logs
+ * (`~/.copilot/session-state/<id>/events.jsonl`): `assistant.message.toolRequests[].name` and
+ * `tool.execution_start.toolName` both carry `entwurf-bridge-entwurf_v2`, with
+ * `mcpServerName`/`mcpToolName` beside them as the parts. Derive-and-measure, never copy a
+ * sibling's spelling (`docs/adding-a-harness.md` step 5).
+ *
+ * `[측정]` omp 18.0.0 is the sharpest case for that rule: it mints
+ * `mcp__${sanitizedServerName}_${normalizedToolName}` with a sanitizer whose charset is
+ * `[a-z_]` (`mcp/tool-bridge.ts:351-357`, `:396`), so the DIGIT IN `entwurf_v2` IS EATEN and the
+ * hyphen in the server key becomes an underscore — the model-facing name is
+ * `mcp__entwurf_bridge_entwurf_v`, not `..._entwurf_v2` and not Claude's double-underscore form.
+ * Confirmed against a live tool dump of all seven bridge tools and a real session transcript
+ * (`scripts/raw-omp-measure/README.md` "Tool-name dialect"). Unlike Copilot there is no second
+ * permission dialect: omp's approval layer consults the same minted string (`source-audit.md`).
+ */
+export const FRESH_CALL_CALLBACK_TOOL = {
+    pi: "entwurf_v2",
+    "claude-code": "mcp__entwurf-bridge__entwurf_v2",
+    copilot: "entwurf-bridge-entwurf_v2",
+    omp: "mcp__entwurf_bridge_entwurf_v",
+    codex: "mcp__entwurf_bridge__entwurf_v2",
+};
+/**
+ * The same dialects, for the tool the framing OFFERS rather than requires.
+ *
+ * `[sol D2, 2026-09-18]` the corroboration sentence named a bare `entwurf_peers` to every backend,
+ * including the four that reach it under a composed MCP name. The prohibition it replaced was
+ * removed precisely because a sibling should be able to check who called it; naming that tool in a
+ * spelling its own session does not expose puts the offer back out of reach for exactly the
+ * backends that needed it most.
+ *
+ * Every entry is the callback dialect applied to `entwurf_peers`, so the two maps drift together
+ * or not at all. omp is the one that has to be read rather than pattern-matched: its sanitizer
+ * charset is `[a-z_]`, which ate the digit in `entwurf_v2` — `entwurf_peers` has no digit, so the
+ * SAME rule produces the whole word here.
+ */
+export const FRESH_CALL_PEERS_TOOL = {
+    pi: "entwurf_peers",
+    "claude-code": "mcp__entwurf-bridge__entwurf_peers",
+    copilot: "entwurf-bridge-entwurf_peers",
+    omp: "mcp__entwurf_bridge_entwurf_peers",
+    codex: "mcp__entwurf_bridge__entwurf_peers",
+};
+/**
+ * ONE BACKEND NEEDS TO BE TOLD HOW TO REACH ITS OWN CALLBACK TOOL `[측정 2026-09-18, n=5 + n=3]`.
+ *
+ * A Claude Code child of this rail could not call `entwurf_v2` on its first turn because the tool
+ * was not callable yet — claude-code 2.1.267 surfaces an MCP server that is still connecting as
+ * DEFERRED: the NAME is listed, the schema is not, and a call without the schema fails. Across five
+ * isolated probes the bridge's tools were directly callable ZERO times (4 DEFERRED, 1 still
+ * connecting), and the framing said "FIRST ACTION … call `entwurf_v2`" without saying the one thing
+ * that makes that possible. A child that cannot call the tool answers in text and goes idle — which
+ * is exactly the "silence" this rail measured in production, 5 of 14 recorded launches.
+ *
+ * The timing story that preceded this one is retired: re-read at n=13 rather than n=4, the success
+ * and silence latencies overlap completely (a 52 ms child called back; a 94 ms child did not), and
+ * the repair worked on a 782 ms child — slower than every silent run.
+ *
+ * `[측정, n=3, same model]` adding the sentence below produced 3/3 callbacks. It is a FACT about the
+ * runtime, in the register the rest of this framing uses since the prohibitions came out: it grants
+ * nothing, forbids nothing, and names the one call that turns a listed name into a callable tool.
+ * Both tools ride ONE `ToolSearch` select, so the corroboration the framing offers stays reachable
+ * for a child that takes the offer.
+ *
+ * Every other backend gets an EMPTY array, deliberately: pi has no deferred-tool surface, and the
+ * other three were never measured to need it. A hint invented for a runtime nobody probed would be
+ * this rail guessing about a vendor again.
+ */
+export const FRESH_CALL_TOOL_LOAD_HINT = {
+    pi: [],
+    "claude-code": [
+        "If ${callbackTool} is not callable yet, the entwurf-bridge server is still connecting or its",
+        'tools are deferred: load them first with ToolSearch("select:${callbackTool},${peersTool}") —',
+        "it waits for the server — then call ${callbackTool}.",
+    ],
+    copilot: [],
+    omp: [],
+    codex: [],
+};
+/**
+ * The omp bootstrap flag, spelled WITHOUT dashes — the vendor's flag map is keyed by bare
+ * name (`extensions/loader.ts:221-228`) and this composition adds the `--` itself.
+ *
+ * Held equal to the installed extension's own constant by
+ * `test/omp-fresh-bootstrap.contract.test.ts`. The two copies exist because the extension
+ * ships INSIDE the omp agent dir carrying only its own small closure and cannot import this
+ * module; the gate is what keeps the duplication from becoming drift.
+ */
+export const OMP_BOOTSTRAP_FLAG = "entwurf-bootstrap";
+/** Payload grammar version, matched exactly by the decoder. A bump means a stale installed
+ * unit, which is the one thing `doctor-omp-bridge` exists to say out loud. */
+export const OMP_BOOTSTRAP_VERSION = 1;
+/**
+ * The whole of what a fresh omp sibling is launched with.
+ *
+ * THREE FIELDS, CLOSED. The decoder refuses an unknown key, so this object is the entire
+ * contract: who to call back, the nonce that proves it is this call, and the task that is
+ * released only after that callback succeeds. There is no command here, no path, no env name
+ * and no model — the model is already an explicit argv token, and a second copy of it inside
+ * a payload would be a second place for it to disagree with the launch.
+ */
+export function buildOmpBootstrapPayload(params) {
+    return JSON.stringify({
+        v: OMP_BOOTSTRAP_VERSION,
+        target: params.callerGardenId,
+        nonce: params.nonce,
+        task: params.task,
+    });
+}
+/**
+ * THE CODEX SOCKET IS INJECTED, NOT RESOLVED HERE, and that is the one seam #116 S2-a had to
+ * open. `resolveCodexDefaultSocketPath` lives in `native-push/codex-ws-client.ts`, which imports
+ * `entwurf-v2-contract` — importing it would have put a delivery-contract module inside the leaf
+ * that is supposed to know nothing about delivery. The alternative, re-deriving the path here,
+ * would have been a silent second copy of a vendor coordinate. So the caller passes a THUNK: it
+ * is evaluated only inside the codex arm, exactly as the inline call was, so a missing HOME still
+ * fails only for codex and never for pi.
+ */
+/**
+ * Backend argv AFTER the runtime path. Both orders are MEASURED, and both were measured by
+ * getting them wrong first (rail §6-a):
+ *
+ *   pi          — prompt BEFORE `--entwurf-control`, then `--model`, value as TWO tokens.
+ *                 Flag-first submitted no message; Pi rejects the equals form for `--model`.
+ *   claude-code — prompt, then `--allowedTools=` and `--model=` as ONE token each. The space form
+ *                 for allowedTools is variadic and eats the prompt as an option value.
+ *   copilot     — the managed VERB first, then the prompt as the value of `-i/--interactive`,
+ *                 `--model`, value as two tokens, and the policy as the explicit `--yolo`
+ *                 token. Measured from `copilot --help` (1.0.80).
+ *   omp         — NO positional prompt at all. The task rides `--entwurf-bootstrap`, a fixed
+ *                 flag the installed birth extension registers, then `--model`, value as two
+ *                 tokens, then the policy as `--approval-mode`, `yolo`. `-p/--print` remains
+ *                 the flag this argv must never carry — it processes a prompt and EXITS,
+ *                 closing the window on a sibling that has to stay open to be delivered to.
+ *
+ * Both pi/claude failures looked identical from outside: window open, record and socket minted,
+ * no turn.
+ *
+ * For pi and claude-code the equals form is NOT a permission guarantee — on the measured host
+ * the tool was already permitted, so the option's effect was unobservable. What was observed is
+ * that it does no harm to the argv. Permission stays a documented host precondition there.
+ *
+ * Copilot is the backend where the policy IS carried explicitly (step 9 clause 2), and three of
+ * its argv facts are load-bearing:
+ *
+ *   - `copilot` is argv[0] of the RUNTIME `entwurf`, i.e. the managed verb — see
+ *     `FRESH_CALL_RUNTIME`. Everything after it is forwarded byte-identical by
+ *     `scripts/copilot-launch.sh`.
+ *   - the prompt rides `--interactive`, never `-p/--prompt`: `-p` runs the prompt and EXITS,
+ *     which would close the window on a sibling that is supposed to stay open and be delivered
+ *     to. `--interactive <prompt>` is non-variadic, so the space form is safe here.
+ *   - the policy token is `--yolo`, STATED HERE rather than left to the launcher: the launcher
+ *     injects `--yolo` only when the argv names no policy, and step 9 clause 2 requires the
+ *     fresh composition to state its model and permission policy explicitly, never to rely
+ *     invisibly on someone else's default.
+ *
+ * `--yolo` is a GLG operator decision, not a drifted default. The first cut passed a
+ * callback-only `--allow-tool=entwurf-bridge(entwurf_v2)` grant, and GLG's 2026-08-25 operator
+ * LIVE measured the consequence: the fresh sibling's footer showed no `YOLO`, and every tool
+ * its task needed stopped on a confirmation prompt, which made the sibling impractical to work
+ * with. GLG then set the policy explicitly: a fresh Copilot sibling carries the same managed
+ * `--yolo` profile a human-typed `entwurf copilot` gets. (Copilot 1.0.80 help: `--yolo` = all
+ * tools + all paths + all URLs.) The permission GRAMMAR lesson from that first cut — Copilot's
+ * `--allow-tool` takes `<mcp-server-name>(tool-name?)`, a different dialect from the
+ * model-facing tool name — stays recorded in `docs/adding-a-harness.md` step 9's worked
+ * example; it is a measured vendor fact even though this argv no longer uses it.
+ *
+ * OMP'S POLICY TOKEN IS THE ONE MOST EASILY ARGUED AWAY, SO READ THIS BEFORE DELETING IT.
+ * `[측정]` omp 18.0.0's schema default for `tools.approvalMode` IS ALREADY `yolo`
+ * (vendor doc `omp://approval-mode.md`; `omp config get tools.approvalMode` → `yolo` on the
+ * acceptance host). So dropping `--approval-mode yolo` changes NOTHING observable: the callback
+ * still fires, the LIVE smoke still passes, and the argv silently starts depending on a vendor
+ * default and on whatever the operator's config happens to say. That is exactly the drift step 9
+ * clause 2 forbids — "carry the chosen width as an explicit argv token rather than relying on a
+ * launcher's injected default" — and the reason the width is stated here even though the host
+ * would have granted it anyway. The width itself (task-wide, not callback-only) is a GLG
+ * operator decision of 2026-08-30, taken with the Copilot measurement in hand: a callback-only
+ * sibling names itself and then stops at the first tool its TASK needs. omp offers no argv
+ * grammar for a narrower grant at all — `tools.approval.<tool>` is a config axis, not a flag —
+ * so the honest choice was between `write` and `yolo`, and `yolo` matches what a human-typed
+ * `omp` gets on this host. `--approval-mode` takes both the space and equals form (measured);
+ * the space form is used for symmetry with `--model`.
+ *
+ * WHY OMP ALONE CARRIES NO PROMPT, AND WHY THAT IS A MEASUREMENT RATHER THAN A PREFERENCE.
+ * `[LIVE 2026-08-30]` the first public fresh call at omp DID pass the full framing as a bare
+ * positional. The window opened, the record minted (garden `20260830T181342-452167`), the
+ * prompt arrived byte-identical as a user message at `09:13:42.413Z` — and the model answered
+ * the literal text `ACK` with ZERO tool calls, because the callback tool did not exist yet.
+ * `[source]` the interactive UI defers MCP discovery and only refreshes the tool list once
+ * `discoverAndConnect()` settles (`sdk.ts:1847-1855`, `:1881-1905`), while the positional
+ * `initialMessage` prompts immediately after `await mode.init()` (`main.ts:540-565`,
+ * `595-610`). `[측정]` a `/tmp` observer on the same runtime: `turn_start` at +654ms with the
+ * entwurf tools ABSENT, callback tool present only at +1484ms — the turn began ~830ms before
+ * the tool it was told to call existed. No argv can close that gap, because the gap is a race
+ * inside the host. So the composition hands omp a PAYLOAD instead of a turn, and the
+ * in-process birth extension — which can see when the tool becomes callable — owns the first
+ * two messages (`pi-extensions/meta-bridge-omp.ts`, "THE TWO-STAGE FRESH BOOTSTRAP").
+ *
+ * The flag is fixed and one-purpose ON PURPOSE. `[측정 2026-08-30]` a normal discovered
+ * extension that registers a flag receives the operator's argv value byte-identical — quotes,
+ * `$VAR`, backticks and a semicolon all survived a 137-byte JSON payload — because extensions
+ * load before argv classification and the reparse writes the registered map
+ * (`main.ts:1799-1810`, `cli/extension-flags.ts:36-43`). An env carrier or a temp file would
+ * have needed its own quoting, its own lifetime and its own refusal rules; argv already owns
+ * all three. This is deliberately NOT a general `--flag value` passthrough — an arbitrary
+ * carrier would hand callers the launch-shaping power this rail exists to refuse.
+ *
+ * CODEX ALONE CARRIES A DIRECTORY IN ITS ARGV, AND OMITTING IT IS A WRONG ANSWER RATHER THAN A
+ * NEUTRAL ONE. `[source rust-v0.153.4]` an explicit `--remote <endpoint>` — which this argv
+ * always passes — resolves to `AppServerTarget::Remote` (`codex-rs/tui/src/lib.rs:875-876`;
+ * `LocalDaemon` is only the IMPLICIT no-flag reuse path), and a Remote target takes its new
+ * thread's directory from `remote_cwd_override` ALONE: `thread_cwd_from_config`
+ * (`codex-rs/tui/src/app_server_session.rs:2022-2033`) answers `None` without it, and the
+ * app-server then opens the thread in ITS OWN directory. That override is exactly `-C/--cd`,
+ * retained only for a remote target (`codex-rs/tui/src/startup_orchestration.rs:191-194`), and
+ * the flag lives on the shared interactive options this argv already uses for
+ * `--dangerously-bypass-approvals-and-sandbox` (`codex-rs/utils/cli/src/shared_options.rs:53-68`)
+ * — not only on the `agents` subcommand that also spells it (`codex-rs/cli/src/main.rs:334`).
+ *
+ * `[측정 2026-09-16]` with the flag absent, three citizens of one chain (pi → Codex → Claude
+ * Code) all recorded the app-server's `~/repos/gh/entwurf` while the panes themselves sat in
+ * `~/repos/gh/agent-config`, and the birth hook wrote that vendor-supplied cwd into each record
+ * honestly (#95 lane C §1). So the token is ALWAYS present for codex: ONE directory, TWO
+ * CARRIERS — tmux `-c` places the PANE, codex `-C` places the THREAD, and the rail's chosen
+ * directory is the single value both receive. It is not a new input axis: the value is chosen by
+ * the cwd rules the rail already has, one layer up.
+ *
+ * BOTH CODEX FACTS ARRIVE AS THUNKS, and for the same reason: they are rail knowledge, and only
+ * the codex branch may pay for them. A host with no Codex home must still open pi and claude
+ * siblings, and the herdr rail — where codex is not a pilot backend and is refused before this
+ * point — supplies throwing resolvers so a future widening cannot silently inherit a guess.
+ */
+export function composeBackendArgs(backend, composition, model, resolveCodexSocketPath, resolveCodexLaunchCwd) {
+    switch (backend) {
+        case "pi":
+            return [composition.prompt, "--entwurf-control", "--model", model];
+        case "claude-code":
+            return [composition.prompt, `--allowedTools=${FRESH_CALL_CALLBACK_TOOL["claude-code"]}`, `--model=${model}`];
+        case "copilot":
+            return ["copilot", "--interactive", composition.prompt, "--model", model, "--yolo"];
+        case "omp":
+            return [`--${OMP_BOOTSTRAP_FLAG}`, composition.bootstrapPayload, "--model", model, "--approval-mode", "yolo"];
+        case "codex":
+            return [
+                "--remote",
+                `unix://${resolveCodexSocketPath()}`,
+                "-C",
+                resolveCodexLaunchCwd(),
+                "--model",
+                model,
+                "--dangerously-bypass-approvals-and-sandbox",
+                composition.prompt,
+            ];
+    }
+}
+/**
+ * PLACEMENT SENTENCE. The first line names where the sibling was opened, and only the RAIL knows
+ * that — "the operator's tmux session" is true of a `new-window` launch and false of a herdr
+ * pane. It is therefore supplied by the caller rather than composed here. Everything BELOW that
+ * line is rail-independent and stays the contract: the callback is the first action, the task
+ * follows it, and the three prohibitions are measured rather than polite.
+ */
+/**
+ * The first-turn framing, WITHOUT the task.
+ *
+ * Split from the whole prompt because the two halves travel differently. The tmux rail hands a
+ * sibling one multi-line string and both halves ride together; the herdr rail cannot carry a
+ * newline at all (`[source herdr 7505c08]` `src/app/agents.rs:157-161` refuses any agent argument
+ * containing a Unicode Cc), so it folds THIS half onto one line and encodes only the task. Keeping
+ * the halves separate is what lets the framing stay plain prose on both rails while the operator's
+ * task text keeps every byte it was written with.
+ *
+ * Order is the contract: the callback is the FIRST action and the task follows it, so a sibling
+ * that gets stuck in the task has already told the caller who it is.
+ *
+ * WHAT THIS SAYS AND WHY IT STOPPED SAYING THE REST (#116). Until 2026-09-17 this framing carried
+ * three prohibitions, including "Do not inspect environment variables, do not call entwurf_self".
+ * `[GLG 직접, 날것 PC, 2026-09-17]` a Claude Sonnet 5 sibling REFUSED the whole first turn and named
+ * that line as its reason: "legitimate instructions don't need to disable your ability to
+ * sanity-check them". It was right, and the prohibition was costing more than the wasted turn it
+ * was written to prevent. What replaces it is the same steering stated as a FACT — reporting your
+ * identity in the pane does not reach the caller, the tool call does — plus a read-only way to
+ * corroborate the caller instead of an instruction not to look.
+ */
+export function composeFreshCallFraming(params) {
+    const tool = FRESH_CALL_CALLBACK_TOOL[params.backend];
+    const peersTool = FRESH_CALL_PEERS_TOOL[params.backend];
+    // The hint is a per-backend TEMPLATE so the two tool dialects stay the single source of their
+    // own spelling here too — a hint that hard-coded Claude's name would go stale the day a dialect
+    // moves, and it would go stale silently, in the one sentence a stuck child depends on.
+    const loadHint = FRESH_CALL_TOOL_LOAD_HINT[params.backend].map((line) => line.replaceAll("${callbackTool}", tool).replaceAll("${peersTool}", peersTool));
+    const hintBlock = loadHint.length === 0 ? [] : ["", ...loadHint];
+    if (params.openingLine.length === 0) {
+        throw new Error("fresh-call composition: openingLine is empty — the rail must state where it placed the sibling");
+    }
+    return [
+        params.openingLine,
+        "",
+        `FIRST ACTION, before reading files or anything else: call ${tool} with ` +
+            `target=${params.callerGardenId}, intent=fire-and-forget, wants_reply=false, and ` +
+            `message set to exactly ${params.nonce} — that string alone, nothing added.`,
+        `${params.nonce} is a correlation tag this caller minted for this one launch: it names no`,
+        "secret and grants no access. Sending it is how the caller learns the garden id you were born",
+        "with, which it has no other way to know. Your own record does not carry the caller's address,",
+        "so reporting your identity here does not reach it — that tool call does.",
+        "",
+        `You can corroborate the caller first if you want to: ${peersTool} is a read-only listing of`,
+        `this garden's citizens and ${params.callerGardenId} is one of them. That listing is capped, so`,
+        "a caller you do not happen to see in it is not a reason to skip the callback.",
+        ...hintBlock,
+        "",
+        // WHERE THE RESULT GOES, said once, as topology. `[GLG 직접, 2026-09-18]` a Sonnet sibling
+        // finished its task and printed the answer in its own window; the caller never saw it. An
+        // investigation found no broken injection — NEITHER framing, old or new, had ever said this.
+        // It used to work because a hand-written briefing named the target and the tool, and when the
+        // briefing stopped doing that the sentence turned out to live nowhere.
+        //
+        // It is a FACT about the topology, not a command about behaviour: the second half is what
+        // makes the first half necessary, because a sibling with a visible window has no way to know
+        // its window is not the delivery. Nothing here watches for completion or sends on the
+        // sibling's behalf — this rail launches and lets go (Hard Rule 16, and the reason there is no
+        // supervisor anywhere in it).
+        `When the task reaches its requested final result, send that result to the same target with ${tool}.`,
+        "Output in this sibling window is not delivered to the caller.",
+    ];
+}
+/**
+ * The whole first turn for a rail that can carry newlines: the framing, then the task.
+ */
+export function composeFreshCallPrompt(params) {
+    return [...composeFreshCallFraming(params), "", "After the tool receipt, carry out this task:", "", params.task].join("\n");
+}
+/** Correlation tag only. Random, never derived from time, cwd or a peer listing — a nonce that
+ * encoded any of those would invite exactly the guessing this rail exists to refuse. */
+export function mintNonce(randomHex = defaultRandomHex) {
+    return `mux-fresh-call-${randomHex()}`;
+}
+function defaultRandomHex() {
+    return randomBytes(12).toString("hex");
+}
+/** Mirrors the `entwurf_v2` message bound. This is an INTERFACE cap for symmetry with the
+ * delivery surface, not a claim that a task of this size was measured through any one rail. An
+ * argv that the OS refuses is a launch failure and fails loud — it never reads as a delivered
+ * task. */
+export const TASK_MAX_CHARS = 16000;
+export const MODEL_MAX_CHARS = 200;
+const MODEL_PATTERN = /^[A-Za-z0-9][A-Za-z0-9._/:[\]-]*$/;
+/** A model is an explicit launch input, not ambient process state. The grammar admits canonical
+ * pi provider/model ids, Claude model ids/aliases, and bracketed context variants, while refusing
+ * whitespace and shell/tmux control syntax. It is passed without a shell using each runtime's
+ * measured CLI dialect: Pi takes `--model`, value; Claude Code takes `--model=value`. */
+export function isSafeFreshCallModel(model) {
+    return model.length > 0 && model.length <= MODEL_MAX_CHARS && MODEL_PATTERN.test(model);
+}
+/**
+ * Normalise and validate what the CALLER supplied, in the one order both rails share.
+ *
+ * Model and task are TRIMMED — that is the public contract and predates both rails, so a task
+ * of spaces is `task-empty` rather than a sibling born with nothing to do. Everything after this
+ * point travels byte-exact; the trim is the only normalisation anywhere in a launch.
+ *
+ * `cwd` is the exception that must not be "fixed": ONLY `undefined` and the exact empty string
+ * mean "no cwd". Every other value is the literal path, deliberately untrimmed, so a
+ * whitespace-mangled directory is refused loudly by each rail's classifier instead of being
+ * silently repaired into a different directory. The classification itself stays on the rails,
+ * because the reasons differ — tmux format-expands a `-c` value and herdr does not.
+ */
+export function normalizeFreshCallInputs(params) {
+    if (typeof params.callerGardenId !== "string" || params.callerGardenId.length === 0) {
+        return { ok: false, reason: "caller-identity-unavailable" };
+    }
+    const model = params.model.trim();
+    if (model.length === 0)
+        return { ok: false, reason: "model-empty" };
+    if (!isSafeFreshCallModel(model))
+        return { ok: false, reason: "model-invalid" };
+    const task = params.task.trim();
+    if (task.length === 0)
+        return { ok: false, reason: "task-empty" };
+    if (task.length > TASK_MAX_CHARS)
+        return { ok: false, reason: "task-too-long" };
+    const cwd = params.cwd === undefined || params.cwd === "" ? undefined : params.cwd;
+    return {
+        ok: true,
+        inputs: { callerGardenId: params.callerGardenId, model, task, ...(cwd === undefined ? {} : { cwd }) },
+    };
+}

package/mcp/entwurf-bridge/dist/pi-extensions/lib/fresh-call-dispatch.js

@@ -0,0 +1,98 @@
+/**
+ * fresh-call-dispatch — the ONE place that decides which rail opens a sibling, and the only module
+ * allowed to know that there are two.
+ *
+ * WHY A COMPOSITION ROOT AND NOT A BRANCH IN EACH SURFACE. Two surfaces register
+ * `entwurf_fresh_call`: pi's own extension and the MCP bridge. Before this file each of them
+ * carried the Codex preflight ordering and the render call itself, and adding a rail choice to
+ * both would have made four places where the wrong one could be picked. A defect planted in one
+ * copy survives on the other, which is precisely the shape a mutant proves nothing about. So the
+ * surfaces now supply identity and an env, and this module supplies everything else.
+ *
+ * THE RAIL IS A CAPABILITY FACT, NOT A PARAMETER. `HERDR_ENV=1` — exactly that value, herdr's own
+ * variable — means this process is inside herdr and the herdr rail is the honest placement. Every
+ * other value, including a missing one, stays on the tmux rail. A caller cannot ask for a rail:
+ * a parameter would let someone request tmux placement from inside herdr, where no tmux server
+ * exists, and the failure would arrive after a mutation rather than before one.
+ *
+ * NO FALLBACK, EITHER DIRECTION. If herdr was selected and its context is incomplete, the call is
+ * refused with the HERDR reason. Silently opening a tmux window instead would put a sibling
+ * somewhere the operator cannot see from where they are standing, and the receipt would look fine.
+ *
+ * WHAT THIS MODULE DOES NOT DO: it never reads the record store, never resolves a garden id, and
+ * never turns the direct herdr witness into a second public address. The nonce callback remains
+ * the one address path, on both rails.
+ */
+import { spawn as spawnChildProcess } from "node:child_process";
+import { codexCallerFreshPreflight, codexFreshPreflight } from "./codex-fresh-preflight.js";
+import { mintNonce } from "./fresh-call-composition.js";
+import { createHerdrRunner, herdrFreshCall, renderHerdrFreshCall, resolveHerdrContext, } from "./herdr-fresh-call.js";
+import { freshCall, renderFreshCall } from "./mux-fresh-call.js";
+/** herdr's own marker, read for its EXACT value. `[측정 2026-09-14]` herdr exports `HERDR_ENV=1`
+ * to every process it starts; anything else is not a claim herdr made. */
+export function selectFreshCallRail(env) {
+    return env.HERDR_ENV === "1" ? "herdr" : "tmux";
+}
+/**
+ * Open a sibling on whichever rail this process is actually standing in.
+ *
+ * ORDER MATTERS TWICE. On tmux, the Codex capability preflights run BEFORE the composition, which
+ * is the pre-existing contract. On herdr, the backend refusal comes first: codex is not a pilot
+ * backend there, so running a Codex preflight would ask an irrelevant question and could fail for
+ * a reason that has nothing to do with why the call is impossible.
+ *
+ * THE TWO CODEX CALLER INPUTS ARE TMUX-RAIL FACTS and stop at this boundary. #95 lane B/C measured
+ * both against a tmux pane and an app-server-hosted bridge: a pane title is what carries the
+ * caller's thread-id, and a record cwd exists as an input because THAT process's directory is the
+ * app-server's. Inside herdr the tab is created by herdr, there is no pane title to anchor to, and
+ * neither fact has been measured — so the herdr rail is handed the request without consulting
+ * them rather than inheriting a rule from a topology it does not share.
+ */
+export async function dispatchFreshCall(request, env = process.env, spawn, nonce = mintNonce()) {
+    if (selectFreshCallRail(env) === "herdr") {
+        const context = resolveHerdrContext(env);
+        if (!context.ok) {
+            // Selected herdr, incomplete herdr: the refusal names the herdr fact. Falling back to
+            // tmux here would open a window the operator cannot see from inside herdr.
+            return { rail: "herdr", result: { ok: false, reason: context.reason } };
+        }
+        const run = createHerdrRunner(context.context.bin, env, spawn ?? spawnChildProcess);
+        return { rail: "herdr", result: await herdrFreshCall(request, run, env, nonce) };
+    }
+    // TWO capability axes, in this order, both pre-mutation and neither standing in for the
+    // other. The TARGET axis first — "entwurf cannot open a Codex sibling here at all" is the
+    // more fundamental answer than "and it would not know where to put it". The CALLER axis
+    // second, and only when the seat anchor will actually be consulted: a codex caller that
+    // named an explicit placement never reads a pane title, so refusing it for a missing
+    // `thread-id` would refuse an unused capability.
+    const targetMissing = request.backend === "codex" ? await codexFreshPreflight(env) : null;
+    const callerMissing = targetMissing === null && request.callerNativeSessionId !== undefined && request.placement === undefined
+        ? codexCallerFreshPreflight(env)
+        : null;
+    const missing = targetMissing ?? callerMissing;
+    if (missing)
+        return { rail: "tmux", result: { ok: false, reason: missing } };
+    return {
+        rail: "tmux",
+        result: freshCall({
+            backend: request.backend,
+            model: request.model,
+            task: request.task,
+            ...(request.cwd === undefined ? {} : { cwd: request.cwd }),
+            ...(request.placement?.tmuxSession === undefined
+                ? {}
+                : { placement: { tmuxSession: request.placement.tmuxSession } }),
+            callerGardenId: request.callerGardenId,
+            ...(request.callerNativeSessionId === undefined
+                ? {}
+                : { callerNativeSessionId: request.callerNativeSessionId }),
+            ...(request.callerCwd === undefined ? {} : { callerCwd: request.callerCwd }),
+        }, env, nonce),
+    };
+}
+/** Each rail renders its own receipt: the coordinates and the failure modes differ, and a single
+ * "universal" renderer would have to speak about panes and windows at once, which is how prose
+ * starts claiming every call uses tmux. */
+export function renderDispatchedFreshCall(dispatched) {
+    return dispatched.rail === "herdr" ? renderHerdrFreshCall(dispatched.result) : renderFreshCall(dispatched.result);
+}