@junghanacs/entwurf 0.14.2 → 0.15.1

package/mcp/entwurf-bridge/dist/pi-extensions/lib/meta-session.js

@@ -12,8 +12,8 @@
  *   1. RECORD functions + types (mint / serialize / parse / certifyActiveStore /
  *      decideUpsert), the backend-agnostic authority. Pure beyond an injected
  *      `now`; backend capability (wakeMode/deliveryLevel) comes from the packaged
- *      registry via a cached fs read (loadMetaCapabilityRegistry) — see that seam
- *      below.
+ *      registry, re-read on every load (loadMetaCapabilityRegistry holds NO cache, so a
+ *      grade moved on disk is visible to a long-lived process) — see that seam below.
  *   2. The thin FS-BOUND STORE (step 3): `upsertMetaSession` wraps the pure core
  *      (readdir → `certifyActiveStore` → `decideUpsert` → atomic write) with the real
  *      filesystem. It lives in this module (not a sibling `*-store.ts`) on purpose:
@@ -69,12 +69,14 @@ export class MetaRecordError extends Error {
 // Schema
 // ---------------------------------------------------------------------------
 /**
- * The three native meta-bridge backends, declared from the start so the
- * per-backend adapter seam is forced (a different native layout each — that
- * difference is the whole reason for a thin adapter). Discriminator field on
- * every record.
+ * Native meta-bridge backends. Discriminator on every record. Adding a member
+ * is a sibling-reader redeploy (`./run.sh install-meta-bridge` and the matching
+ * sibling install), not a store archive: writers certify the whole active store
+ * against THIS set, so a deployed plugin still carrying the old set refuses
+ * every write, including its own. `./run.sh doctor-meta-bridge` already flags a
+ * stale deployed writer — run it after the change.
  */
-export const META_BACKENDS = ["claude-code", "antigravity", "codex"];
+export const META_BACKENDS = ["claude-code", "antigravity", "codex", "copilot"];
 export const META_BACKEND_DESCRIPTORS = {
     "claude-code": {
         backend: "claude-code",
@@ -94,6 +96,47 @@ export const META_BACKEND_DESCRIPTORS = {
         deliveryLevel: "D6",
         nativeIdLabel: "threadId",
     },
+    // SELF-FETCH citizen since #82 RAIL 5. Copilot CLI 1.0.80 runs our plugin hook (birth,
+    // garden address, who-sent) AND forks our first-party extension, whose `joinSession()`
+    // holds an `fs.watch` on the garden mailbox signal and can `session.send()` a doorbell
+    // into an idle session. That is the same shape Claude's mailbox has, reached through a
+    // different vendor surface. Hence:
+    //   wakeMode  self-fetch — the doorbell announces, the model drains its own inbox with
+    //             `entwurf_inbox_read`, and THAT read is the receipt. The extension never
+    //             injects the body, so this label promises exactly what happens. It was
+    //             `direct-inject` while no doorbell existed (measured 2026-08-20: no
+    //             `FileChanged`, `asyncRewake` or `watchPaths` in the bundle) — that
+    //             absence was never a claim about the vendor's other surfaces, and the
+    //             extension rail is the one it missed. Copilot is still NOT a
+    //             `nativePushSupported` backend and has no native-push adapter.
+    //   D6        the PRODUCT grade, earned by the managed LIVE acceptance of 2026-08-23
+    //             (garden 20260823T181316-d9f6ba, native 20fe30c8-b2bc-4600-91a0-8a409131be51,
+    //             CLI 1.0.80): the receive log joins that native id and arms that garden id,
+    //             the mailbox state stamps lastEnqueuedAt 09:23:41.235Z and lastReadAt
+    //             09:23:56.480Z, and the model answered on the SAME record/native/gid chain.
+    //             This is still the PRODUCT grade and not the raw probe's: the earlier
+    //             transport probe was evidence about the mechanism, and it did not move this
+    //             number — a managed round trip did.
+    //             D7 is PARTIAL, deliberately: the reply and the read receipt were observed,
+    //             but the completion taxonomy as a whole and any long-haul operation were
+    //             not, and the reply envelope itself reaches this comment as an INHERITED
+    //             fact (it was not re-read from a transcript when this was written). D8 is
+    //             unproven and D3 (managed second-session isolation) is pending — its
+    //             decisive log was lost to a scratch cleanup before it could be preserved.
+    //             The route stays fail-closed on both ends: with no armed receiver marker
+    //             every dispatch is still refused `mailbox-undeliverable`, so replyability
+    //             is a fact about a live marker and never a constant of this backend.
+    //   sessionId the native join key, measured to be ONE id across all three surfaces:
+    //             the hook envelope, `record.nativeSessionId`, and the SDK's
+    //             `session.sessionId` (record 20260823T112003-9d069a ==
+    //             `ARMED sessionId=4fc16d8d-473d-4258-a1fd-f99d3cb375e9`, CLI 1.0.80).
+    //             That agreement is what lets the extension bind its arm to the record.
+    copilot: {
+        backend: "copilot",
+        wakeMode: "self-fetch",
+        deliveryLevel: "D6",
+        nativeIdLabel: "sessionId",
+    },
 };
 // ---------------------------------------------------------------------------
 // Validation helpers (crash, don't warn)
@@ -104,9 +147,9 @@ export function requireNonEmptyString(value, field) {
     }
     return value;
 }
-/** Validate the 3-backend NATIVE bridge axis (sender/receiver markers, capability
+/** Validate the native-bridge backend axis (sender/receiver markers, capability
  * drift guard). Not a record-schema validator: identity records take
- * `requireCitizenBackend` (which admits `pi`). Markers stay native-3 because the
+ * `requireCitizenBackend` (which admits `pi`). Markers stay on this set because the
  * pi adapter carries its record-established garden id into children via env rather
  * than using the native-hook pid marker rail. */
 export function requireBackend(value) {
@@ -166,7 +209,7 @@ function isoNow(now) {
 /** The one live identity schema number. */
 export const META_SCHEMA_VERSION_V3 = 3;
 /** Every backend admitted by the one V3 record-citizen schema. */
-export const META_CITIZEN_BACKENDS = ["claude-code", "antigravity", "codex", "pi"];
+export const META_CITIZEN_BACKENDS = ["claude-code", "antigravity", "codex", "copilot", "pi"];
 export function requireCitizenBackend(value) {
     if (typeof value !== "string" || !META_CITIZEN_BACKENDS.includes(value)) {
         throw new MetaRecordError(`meta-record "backend" must be one of ${META_CITIZEN_BACKENDS.join(" | ")} (got ${describe(value)}).`);
@@ -523,18 +566,30 @@ export function metaCapabilitiesFilePath() {
 // record.delivery.wakeMode SLOT still existed. 3D-4 then deleted that slot with
 // the rest of `delivery{}`, so today the registry is the sole home.
 // ---------------------------------------------------------------------------
-/** Memoized packaged registry; the file is immutable at runtime, so caching is honest (not stateful lying). */
-let cachedMetaCapabilities = null;
 /**
- * Load + memoize the packaged capability registry — the live source of backend
- * honesty metadata as of 3D-3. A missing/corrupt file throws (the registry is a
- * packaged invariant; check-pack guarantees its presence).
+ * Load the packaged capability registry — the live source of backend honesty metadata
+ * as of 3D-3. A missing/corrupt file throws (the registry is a packaged invariant;
+ * check-pack guarantees its presence).
+ *
+ * NO CACHE, deliberately. This used to memoize into a process-lifetime singleton on the
+ * argument that "the file is immutable at runtime". That argument was false for the one
+ * process that matters: the entwurf-bridge MCP child lives as long as its harness
+ * session, so a grade or wakeMode moved by an install/upgrade was invisible to every
+ * already-running dispatcher until the operator restarted it — and nothing anywhere
+ * said so. The symptom is a citizen answering with last week's capability, which is the
+ * silent-wrong-answer class this repo refuses; "restart your session" is an instruction
+ * to work around a defect, not a fix for it (#82 RAIL 7).
+ *
+ * The subtraction is the whole repair, and it is deliberately not an invalidation
+ * scheme. Stat-based invalidation (mtime+size) cannot see an atomic same-size,
+ * same-timestamp replacement, so it would trade a certain staleness bug for an
+ * intermittent one; content hashing would have to read the file anyway. The registry is
+ * a few hundred bytes and both production callers — the v2 decider and production
+ * deliverability — reach it once per dispatch, not in a loop, so reading it there is
+ * cheaper than being wrong.
  */
 export function loadMetaCapabilityRegistry() {
-    if (cachedMetaCapabilities === null) {
-        cachedMetaCapabilities = parseMetaCapabilityRegistry(fs.readFileSync(metaCapabilitiesFilePath(), "utf8"));
-    }
-    return cachedMetaCapabilities;
+    return parseMetaCapabilityRegistry(fs.readFileSync(metaCapabilitiesFilePath(), "utf8"));
 }
 /**
  * The capability for one backend, from the registry (3D-3 live source). The
@@ -749,14 +804,17 @@ export function certifyActiveStoreDir(dir) {
 }
 /**
  * The refusal an uncertifiable ACTIVE store earns, in the words both the runtime
- * writers and the install doctor use. One prescription, both invocation forms —
- * every defect kind (previous generation, corruption, drift, duplicate, symlink)
- * is answered by archiving the generation, so there is nothing to branch on.
+ * writers and the install doctor use. Rotten records (previous generation,
+ * corruption, drift, duplicate, symlink) are answered by archiving. An
+ * unknown-backend defect is a stale reader, not a rotten store — the listed
+ * defect says so; this headline tells the operator to distinguish. No branch:
+ * both sentences always print.
  */
 export function activeStoreRefusal(cert, shown = 3) {
     const headline = `meta-record store ${cert.dir} holds ${cert.defects.length} entry/entries this generation cannot certify — ` +
         `refusing to write (the active store is v3-only and carries no cross-generation continuity). ` +
-        `Archive the generation and open a fresh one with ${FRESH_CUT_PRESCRIPTION}.`;
+        `Archive the generation and open a fresh one with ${FRESH_CUT_PRESCRIPTION}. ` +
+        `If a listed defect says "backend" must be one of this reader's known set, the reader is stale — redeploy the sibling unit (the matching doctor names the install verb); do not archive those records.`;
     // `shown = 0` is for a caller that ALREADY printed every cause per entry (the
     // store-doctor): repeating them here doubles the wall on a large previous
     // generation, which is exactly the aggregation lesson F8 taught. The count and
@@ -1339,12 +1397,28 @@ export function readMetaSenderMarker(opts) {
 }
 // ── meta-receiver presence marker (SE-2 active-receiver signal) ──────────────
 /**
- * The arm-capable hook events. Only these can emit watchPaths (and therefore arm
- * the idle-wake), so only these write a receiver presence marker. UserPromptSubmit
- * is deliberately absent: it can backfill the record but cannot re-arm the watch, so
- * it must NOT mint or refresh an "active receiver" claim it cannot back.
+ * The arm-capable events, across every backend that can arm an idle wake.
+ *
+ * CLAUDE (`session-start`, `cwd-changed`, `file-changed`): only these hook events can
+ * emit watchPaths (and therefore arm the idle-wake), so only these write a receiver
+ * presence marker. UserPromptSubmit is deliberately absent: it can backfill the record
+ * but cannot re-arm the watch, so it must NOT mint or refresh an "active receiver"
+ * claim it cannot back.
+ *
+ * COPILOT (`extension-join`): the same rule, one backend over. Copilot's arm is not a
+ * hook at all — the CLI forks a first-party extension and the extension's own
+ * `joinSession()` is what puts a live `fs.watch` on the garden mailbox signal and gives
+ * it a `session.send()` channel to ring. The membership test is unchanged and is about
+ * capability, not event vocabulary: this provenance is admitted because the process that
+ * writes it holds the watch and can start a turn on an idle session. A Copilot hook event
+ * has neither, which is why the birth hook still arms nothing (#82 RAIL 5).
  */
-export const META_RECEIVER_ARM_PROVENANCES = ["session-start", "cwd-changed", "file-changed"];
+export const META_RECEIVER_ARM_PROVENANCES = [
+    "session-start",
+    "cwd-changed",
+    "file-changed",
+    "extension-join",
+];
 function requireArmProvenance(value) {
     if (typeof value === "string" && META_RECEIVER_ARM_PROVENANCES.includes(value)) {
         return value;

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

@@ -46,26 +46,47 @@
  */
 import { randomBytes } from "node:crypto";
 import { classifyTmuxCwd } from "./classify-tmux-cwd.js";
+import { COPILOT_PREFLIGHT_HINT, copilotFreshPreflight, } from "./copilot-fresh-preflight.js";
 import { assertLaunchTarget, LaunchPreconditionError, resolveRuntimeOnPath, } from "./mux-launch.js";
 import { APPEND_FORMAT, assertSelector, assertTmuxOk, inspectPlacement, parseWindowFields, requireSameContext, runTmux, } from "./mux-placement.js";
-/** The two backends this rail can open. Fixed set, not a profile — a third one is a decision,
- * not a config entry. */
-export const FRESH_CALL_BACKENDS = ["pi", "claude-code"];
-/** The fixed runtime each backend resolves on PATH. Same reason `mux-launch` uses PATH rather
+/** 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 under the step 9 admission contract. */
+export const FRESH_CALL_BACKENDS = ["pi", "claude-code", "copilot"];
+/**
+ * The fixed runtime each backend resolves on PATH. Same reason `mux-launch` uses PATH rather
  * than a compiled-in location: the official binary is whatever the operator's environment gives
- * when they type the name. */
+ * when they type the name.
+ *
+ * `copilot` resolves `entwurf`, NOT the vendor CLI, and that is the contract rather than a
+ * convenience. Step 9 clause 1 requires ONE fixed MANAGED runtime path, and a bare `copilot`
+ * is not one: it would start without the `COPILOT_CLI_ENABLED_FEATURE_FLAGS=EXTENSIONS` token
+ * whose absence skips the extension scan SILENTLY, so the sibling would look launched and could
+ * never be delivered to. `entwurf copilot` is the accepted managed invocation that owns that
+ * flag, its recursion fence and its receiver precondition; fresh call reaches Copilot only
+ * through it. The cost is named: a Copilot fresh call needs a current `entwurf` on PATH, the
+ * way a pi fresh call needs `pi`.
+ */
 export const FRESH_CALL_RUNTIME = {
     pi: "pi",
     "claude-code": "claude",
+    copilot: "entwurf",
 };
 /**
  * The callback tool NAME differs per backend and that is not cosmetic: native pi exposes the
- * capability directly (`entwurf_v2`), while a Claude Code session reaches it through the MCP
- * bridge under its namespaced name. Naming the wrong one costs the whole first turn.
+ * 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).
  */
 export const FRESH_CALL_CALLBACK_TOOL = {
     pi: "entwurf_v2",
     "claude-code": "mcp__entwurf-bridge__entwurf_v2",
+    copilot: "entwurf-bridge-entwurf_v2",
 };
 /** 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 tmux. An argv
@@ -88,12 +109,41 @@ export function isSafeFreshCallModel(model) {
  *                 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).
  *
- * Both failures looked identical from outside: window open, record and socket minted, no turn.
+ * Both pi/claude failures looked identical from outside: window open, record and socket minted,
+ * no turn.
  *
- * 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.
+ * 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.
  */
 export function buildBackendArgs(backend, prompt, model) {
     switch (backend) {
@@ -101,6 +151,8 @@ export function buildBackendArgs(backend, prompt, model) {
             return [prompt, "--entwurf-control", "--model", model];
         case "claude-code":
             return [prompt, `--allowedTools=${FRESH_CALL_CALLBACK_TOOL["claude-code"]}`, `--model=${model}`];
+        case "copilot":
+            return ["copilot", "--interactive", prompt, "--model", model, "--yolo"];
     }
 }
 /**
@@ -204,6 +256,17 @@ export function freshCall(params, env = process.env, nonce = mintNonce()) {
             return { ok: false, reason: err.reason };
         throw err;
     }
+    // Backend capability, still PRE-MUTATION (step 9 clause 3). It runs AFTER the runtime is
+    // proven, because "entwurf is not on PATH" is the more fundamental answer — telling an
+    // operator to run `entwurf install-copilot-bridge` when they have no `entwurf` at all sends
+    // them to the wrong repair. It runs BEFORE placement for the reason this whole ordering
+    // exists: a refusal here cannot leave a window behind, while the launcher's own equivalent
+    // check (receiver only, manual `entwurf copilot`) necessarily runs after one is open.
+    if (params.backend === "copilot") {
+        const missing = copilotFreshPreflight(env);
+        if (missing)
+            return { ok: false, reason: missing };
+    }
     const inspected = inspectPlacement(env);
     if (!inspected.ok)
         return { ok: false, reason: inspected.reason };
@@ -244,6 +307,9 @@ export function freshCall(params, env = process.env, nonce = mintNonce()) {
 /** Why each refusal happened, in the caller's terms. A reason a caller cannot act on is a reason
  * they will guess about. */
 const REJECT_HINT = {
+    // The Copilot capability reasons keep their repair text on the leaf that decides them, so
+    // the sentence an operator reads cannot drift away from the predicate that produced it.
+    ...COPILOT_PREFLIGHT_HINT,
     "no-tmux-context": "this agent is not running inside tmux, so there is no session to open a sibling beside",
     "anchor-malformed": "TMUX_PANE is not a native pane id",
     "anchor-unresolved": "tmux resolved no pane for this agent's anchor",

package/mcp/entwurf-bridge/dist/pi-extensions/meta-bridge-hook-copilot.js

@@ -0,0 +1,288 @@
+/**
+ * meta-bridge-hook-copilot — the GitHub Copilot CLI native-session BIRTH entry (#82).
+ *
+ * WHAT THIS IS, AND WHAT IT DELIBERATELY IS NOT
+ *
+ * It mints, then names the minted citizen as this host's SENDER:
+ *
+ *   stdin {sessionId|session_id, cwd}   (Copilot hook envelope, either shape)
+ *     -> upsertMetaSession(copilot)     idempotent create/attach the record
+ *        -> gardenId                    the session's garden address
+ *     -> writeMetaSenderMarker(ppid)    who-sent join for this host's MCP children
+ *
+ * No receiver marker, no mailbox arm, no watchPaths — and that is still the contract now
+ * that Copilot HAS a doorbell (#82 RAIL 5). The reason changed, the rule did not. A
+ * receiver marker is a claim that a LIVE process holds a watch, and the process that holds
+ * Copilot's watch is the forked extension (`pi/copilot-receive/`), not this hook. Minted
+ * here it would name the Copilot host pid as the owner of a watch that pid does not hold,
+ * and the citizen would read deliverable, wired to nothing, for as long as the TUI stayed
+ * open. Arming belongs to the watcher; birth belongs here.
+ *
+ * THE SENDER MARKER IS A DIFFERENT FACT, AND THIS UNIT USED TO CONFLATE THEM. Until
+ * #82 RAIL 5b this file wrote no marker of EITHER kind, and gave the doorbell's
+ * absence as the reason for both. That reasoning is only valid for the receiver:
+ *
+ *   receiver marker = "a live session is ARMED to be woken"  -> needs a doorbell
+ *   sender  marker  = "who owns this MCP child process"      -> needs a shared parent
+ *
+ * `lib/meta-sender-identity.ts` states the sender join in one line — the hook writes a
+ * marker keyed by ITS parent pid, the bridge child looks one up under its own parent,
+ * and that shared ancestor IS the join key. Nothing in it consults a doorbell. So a
+ * Copilot citizen with the MCP hand installed could read (`entwurf_peers`) but never
+ * send: the bridge held the owner pid and found no marker to look up. Writing one is
+ * what closes that, and it changes exactly one thing for the receiver of a message —
+ * it learns WHO sent it.
+ *
+ * IT DOES NOT MAKE THIS CITIZEN REPLYABLE, and must never be described as if it did.
+ * `mcp/entwurf-bridge/src/index.ts` picks the reply rail from `nativePushSupported`;
+ * copilot is not native-push, so it lands in the self-fetch domain, where `replyable`
+ * comes from a RECEIVER marker written by the extension when it joins the session. A
+ * citizen that is born but whose receiver has not armed is `replyable: false` with a real
+ * garden identity — the honest answer, and it becomes true on its own once the extension
+ * binds. What this file must never do is anticipate that answer.
+ *
+ * WHY A SECOND ENTRY FILE. `meta-bridge-hook.ts` hardcodes `backend: "claude-code"`
+ * at mint and then does the marker/watch work above, and two gates pin that unit to
+ * Claude's exec form and its four PascalCase events. Copilot's schema has no `args`
+ * key at all, its exec form is a single `exec` string and its events are camelCase,
+ * so the two units cannot share a manifest — and once the manifests are separate,
+ * sharing an entry would only buy a runtime branch that the gates would then have to
+ * unpick. The shared half lives where it belongs: `lib/meta-session.ts`.
+ *
+ * BIRTH IS ON THE FIRST PROMPT, NOT AT SESSION OPEN. Measured: opening the TUI
+ * registers a session and fires NO hook (11:17:19.920Z registration, three idle
+ * minutes, zero hook lines, `Session: 0 AIC used`). The first prompt then fires
+ * `userPromptSubmitted` (11:20:29.476Z) -> `sessionStart` (11:20:32.102Z). Both are
+ * wired to this entry and the upsert is idempotent, so the earlier of the two mints
+ * and the later attaches. Do not describe a Copilot citizen as born when its window
+ * opens; it is born when it is first spoken to.
+ *
+ * ENVELOPE SHAPE — TWO ACCEPTED, ON PURPOSE. Copilot ships a Claude-compat envelope
+ * translator: a Claude-form hook declaration receives `{hook_event_name, session_id,
+ * cwd, ...}` (measured), while its native declarations carry `{sessionId, timestamp,
+ * cwd, source, ...}`. This unit declares the NATIVE form, and which of the two shapes
+ * a native declaration puts on stdin was not measured. Reading both is not sloppiness
+ * about which is true — it is refusing to bet a citizen's existence on an unmeasured
+ * key name when the two shapes are trivially distinguishable and the log line records
+ * which one actually arrived. That log line is how the doctor turns the guess into a
+ * measurement on the first real session.
+ *
+ * FAILURE POLICY, inherited from the Claude unit: BEST-EFFORT + LOG. Never scream
+ * into the operator's terminal, never block the turn. On any error, append a level-
+ * tagged line to `<pi-agent-dir>/meta-bridge-hook.log` and exit 0 with `{}` on
+ * stdout. The fail-loud surface is the doctor, which reads that log.
+ *
+ * LAUNCH: never invoked directly by Copilot. `hooks/hooks.json` declares
+ * `exec: <baked abspath of scripts/copilot-hook-launch.sh>` and that launcher `exec`s
+ * this payload. See copilot-hook-launch.sh for why it cannot be the Claude launcher.
+ */
+import * as fs from "node:fs";
+import * as path from "node:path";
+import { defaultMetaSessionsDir, isPlausibleOwnerPid, upsertMetaSession, writeMetaSenderMarker, } from "./lib/meta-session.js";
+/**
+ * The launch-provenance handshake, held as LOCAL literals on purpose.
+ *
+ * The Claude payload declares the same pair privately, and `check-meta-receiver-marker`
+ * asserts the literal is present in THAT source — so hoisting the two strings into a
+ * shared module would drag a sibling rail's production file and its gate into this lane
+ * for no behavioral gain (PM decision, 2026-08-21).
+ *
+ * This is not an unguarded copy. The value already exists on both sides of a shell/TS
+ * boundary anyway (`copilot-hook-launch.sh` exports it), and `check-copilot-birth-hook`
+ * fires the REAL assembled launcher, so a drift between the two spellings shows up as a
+ * refused marker in that gate rather than as a silent mismatch.
+ */
+const META_HOOK_LAUNCH_ENV = "ENTWURF_META_HOOK_LAUNCH";
+const META_HOOK_LAUNCH_TOKEN = "hook-launch/v1";
+/** Append a best-effort diagnostic line; swallow even its own failure. Same log file
+ * and same LEVEL vocabulary as the Claude unit, so one doctor grep covers both. */
+function logLine(level, message) {
+    try {
+        const file = path.join(path.dirname(defaultMetaSessionsDir()), "meta-bridge-hook.log");
+        fs.mkdirSync(path.dirname(file), { recursive: true });
+        fs.appendFileSync(file, `${new Date().toISOString()} ${level} [copilot] ${message}\n`);
+    }
+    catch {
+        /* logging is best-effort; a broken log must not break the session */
+    }
+}
+/** Emit the neutral hook response and leave. Copilot has no watchPaths to arm, so
+ * there is never anything else to say. */
+function emit() {
+    process.stdout.write("{}\n");
+    process.exit(0);
+}
+/**
+ * Reduce either envelope shape to the two fields birth needs, or refuse.
+ *
+ * ACCEPTING TWO SHAPES IS NOT THE SAME AS PREFERRING ONE. `sessionId ?? session_id`
+ * would silently pick a winner when the two disagree, and a disagreement is exactly
+ * the case worth refusing: it means the compat translator produced two different
+ * identities for one session, or something hand-built the envelope. A record minted
+ * from the loser would be a citizen no live session can be joined back to. So both
+ * present + equal is fine (`agreeing-both`); both present + different is a REFUSAL
+ * (cross-review, terra, 2026-08-20).
+ *
+ * `cwd` has NO process.cwd() fallback, unlike the Claude entry. There the hook runs
+ * in the session's own cwd, so the fallback is the same value by another route; here
+ * the record is the ONLY thing this unit ever writes and a guessed cwd would be a
+ * fact nothing later can correct. Both measured Copilot shapes carry `cwd`.
+ */
+export function readBirthEnvelope(env) {
+    const nativeRaw = env.sessionId;
+    const compatRaw = env.session_id;
+    const native = typeof nativeRaw === "string" ? nativeRaw : "";
+    const compat = typeof compatRaw === "string" ? compatRaw : "";
+    if (nativeRaw !== undefined && native.length === 0)
+        return { refusal: "sessionId present but not a non-empty string" };
+    if (compatRaw !== undefined && compat.length === 0)
+        return { refusal: "session_id present but not a non-empty string" };
+    if (native && compat && native !== compat) {
+        return { refusal: `sessionId and session_id disagree (${native} vs ${compat})` };
+    }
+    const sessionId = native || compat;
+    if (!sessionId)
+        return { refusal: "no sessionId/session_id" };
+    const shape = native && compat ? "agreeing-both" : native ? "copilot-native" : "claude-compat";
+    if (typeof env.cwd !== "string" || env.cwd.length === 0)
+        return { refusal: "cwd missing or not a non-empty string" };
+    const cwd = env.cwd;
+    const eventLabel = typeof env.hook_event_name === "string" && env.hook_event_name.length > 0
+        ? env.hook_event_name
+        : typeof env.source === "string" && env.source.length > 0
+            ? `native(source=${env.source})`
+            : "unlabeled";
+    return { sessionId, cwd, shape, eventLabel };
+}
+/**
+ * Which pid does a sender marker written here belong to — or NONE.
+ *
+ * `copilot-hook-launch.sh` `exec`s this payload, so on the shipped path this process IS
+ * the launcher and its parent is the Copilot host that ran the hook. Two things that
+ * form cannot promise are asked anyway, and both fail CLOSED:
+ *
+ *   1. LAUNCH PROVENANCE. `process.ppid` only names the Copilot host when this payload
+ *      was reached THROUGH the shipped launcher. A session still holding an older cached
+ *      hook command, or a hand-run of the entry file, has some other parent — so the
+ *      launcher stamps a token and this reads it. No token, no claim.
+ *   2. A PLAUSIBLE LIVE PARENT. `isPlausibleOwnerPid` is the predicate shared with every
+ *      marker writer, reader and the generation cut. A marker naming init outlives every
+ *      process that could refute it, and one such leftover once blocked a host's
+ *      fresh-cut until it was deleted by hand (#53 A).
+ *
+ * Failing closed costs only who-sent, which this backend did not have five minutes ago,
+ * and the doctor reads the WARN. Claiming a transient wrapper as the owner would instead
+ * attribute a citizen's messages to a pid that never sent them.
+ *
+ * MEASUREMENT STATE OF THE JOIN ITSELF. `[측정]` Closed end to end on Copilot CLI 1.0.80,
+ * 2026-08-21, through the PRODUCTION events this unit wires: a live session's marker owner
+ * was the running Copilot native process, that same pid was the parent of the running
+ * entwurf MCP child, and a send from that session arrived carrying its own garden id with
+ * `origin: "meta-session"`. Marker owner == native host == MCP child's parent is therefore
+ * an observed fact on this backend, not an assumption inherited from the other two.
+ *
+ * The claim is still BOUNDED, and the bound is the vendor version: one CLI release is not a
+ * promise about the next, and this join is the only thing standing between a marker and the
+ * child that must find it. That is why the success line below prints the owner pid — it
+ * keeps the join re-checkable from the log alone, with no probe to re-run.
+ */
+/**
+ * Arm who-sent for this host's MCP children, or say in the log why it could not be.
+ *
+ * BEST-EFFORT + LOG, exactly like the mint above it: a Copilot turn must never be broken
+ * or spammed by our bookkeeping, so nothing here throws and nothing reaches the terminal.
+ * The three outcomes get three distinct tokens because they need three different fixes,
+ * and the doctor greps this log:
+ *
+ *   `sender marker <pid> -> <gid>`  armed. The pid is printed because it is the join key
+ *                                   AND the production-event measurement that is still
+ *                                   open (see resolveCopilotHookOwnerPid).
+ *   `sender-marker-refused`         we declined to claim an owner: no launch provenance
+ *                                   (reinstall + restart that session) or an implausible
+ *                                   parent (a reparented orphan). Not an error — a
+ *                                   fail-closed answer, so WARN.
+ *   `sender-marker-failed`          we tried and the write itself broke (permissions, a
+ *                                   full disk, a refused owner pid). ERROR.
+ *
+ * Either non-success costs only who-sent: the citizen still exists, still appears in
+ * `entwurf_peers`, and can still be addressed BY others. Only its own outbound sends fall
+ * back to the bridge's default refusal.
+ */
+function writeCopilotSenderMarker(gardenId, envelope) {
+    const ownerPid = resolveCopilotHookOwnerPid();
+    if (ownerPid === null) {
+        logLine("WARN", process.env[META_HOOK_LAUNCH_ENV] !== META_HOOK_LAUNCH_TOKEN
+            ? `sender-marker-refused garden=${gardenId}: exec-launch provenance missing (${META_HOOK_LAUNCH_ENV}); this hook was NOT reached through copilot-hook-launch.sh, so its parent is not a trustworthy owner. Reinstall the Copilot bridge and RESTART that session. This citizen exists but cannot send (event=${envelope.eventLabel})`
+            : `sender-marker-refused garden=${gardenId}: parent pid ${process.ppid} is not a plausible owner (reparented orphan?); this citizen exists but cannot send (event=${envelope.eventLabel})`);
+        return;
+    }
+    try {
+        writeMetaSenderMarker({
+            backend: "copilot",
+            gardenId,
+            nativeSessionId: envelope.sessionId,
+            cwd: envelope.cwd,
+            ownerPid,
+        });
+        logLine("INFO", `sender marker ${ownerPid} -> ${gardenId} (event=${envelope.eventLabel})`);
+    }
+    catch (err) {
+        logLine("ERROR", `sender-marker-failed pid=${ownerPid} garden=${gardenId}: ${err instanceof Error ? err.message : String(err)}`);
+    }
+}
+function resolveCopilotHookOwnerPid() {
+    if (process.env[META_HOOK_LAUNCH_ENV] !== META_HOOK_LAUNCH_TOKEN)
+        return null;
+    const ownerPid = process.ppid;
+    if (!isPlausibleOwnerPid(ownerPid))
+        return null;
+    return ownerPid;
+}
+function main() {
+    let raw;
+    try {
+        raw = fs.readFileSync(0, "utf8"); // fd 0 = stdin (the Copilot hook envelope)
+    }
+    catch (err) {
+        logLine("ERROR", `stdin read failed: ${err instanceof Error ? err.message : String(err)}`);
+        emit();
+    }
+    let env;
+    try {
+        const parsed = JSON.parse(raw);
+        if (typeof parsed !== "object" || parsed === null)
+            throw new Error("envelope is not an object");
+        env = parsed;
+    }
+    catch (err) {
+        logLine("ERROR", `envelope parse failed: ${err instanceof Error ? err.message : String(err)}`);
+        emit();
+    }
+    const envelope = readBirthEnvelope(env);
+    if ("refusal" in envelope) {
+        // A record keyed to a guess would be a citizen nobody can join back to a real
+        // session, so refuse — and make it ERROR, because this session did NOT become a
+        // garden citizen. The doctor reads this line.
+        logLine("ERROR", `degraded envelope: ${envelope.refusal} (keys=${Object.keys(env).sort().join(",")})`);
+        emit();
+    }
+    try {
+        // transcriptPath and model are omitted, not guessed: Copilot's envelope carries
+        // neither, and both axes are nullable at mint by design.
+        const result = upsertMetaSession({
+            input: { backend: "copilot", nativeSessionId: envelope.sessionId, cwd: envelope.cwd },
+        });
+        logLine("INFO", `${result.action} record ${path.basename(result.path)} (event=${envelope.eventLabel}, shape=${envelope.shape}, native=${envelope.sessionId})`);
+        // RECORD AUTHORITY FIRST: the marker is only a pid->garden hint that the record
+        // must vouch for, so it is written INSIDE the success branch. A marker minted
+        // after a failed upsert would name a garden id with no record behind it — the
+        // resolver would read it, find nothing, and report "names nobody" for a citizen
+        // whose real failure was the mint. Same order as the agy writer.
+        writeCopilotSenderMarker(result.record.gardenId, envelope);
+    }
+    catch (err) {
+        logLine("ERROR", `upsert failed (event=${envelope.eventLabel}, native=${envelope.sessionId}): ${err instanceof Error ? err.message : String(err)}`);
+    }
+    emit();
+}
+main();