@pome-sh/cli 0.20.0 → 0.21.1

package/dist/src/runner/groupRender.d.ts

@@ -1,65 +0,0 @@
-import type { ScoreStatus } from "../hosted/evalResultView.js";
-export type TrialRow = {
-    kind: "completed";
-    /** Cloud-authoritative satisfaction score, 0-100. */
-    score: number;
-    /**
-     * F-925 — three states, not a boolean. `incomplete` means the trial ran
-     * and finalized but at least one criterion never produced a verdict, so
-     * it is neither a pass nor the agent's failure. It was `passed: boolean`
-     * fed from `exitCode === 0`, which counted a 100/100 run with 3 of 4
-     * criteria skipped as a clean passing trial.
-     *
-     * Typed as the CLI's own `ScoreStatus` rather than a second enum, so the
-     * trial line and the single-run headline cannot drift apart.
-     */
-    verdict: ScoreStatus;
-    seconds: number;
-    /** Failing-criteria summary ("a · b"), absent when none were reported. */
-    note?: string;
-} | {
-    kind: "errored";
-    reason: string;
-};
-/** The muted hint under the command echo, naming where the agent command
- *  came from (pome.json / --agent / the built-in default). */
-export declare function flagHintLine(agentCommandSource: string): string;
-/** Printed once the upfront mints are done (the cloud provisions one
- *  isolated twin sandbox per session — ADR-012). FDRS-663: when the plan's
- *  concurrent-twin quota bounded the upfront mint below k, the bound is
- *  named honestly — k stays the design default, the wall-clock stretches. */
-export declare function provisioningLine(k: number, twins: string[], bound?: number): string;
-export declare function spawningAgentLine(command: string, source: string): string;
-export declare function trialRowLine(n: number, row: TrialRow): string;
-export interface GroupSummaryInput {
-    rows: TrialRow[];
-    /** Most-common failed-criterion phrase across completed trials, if any. */
-    failingCriterionPhrase?: string;
-    /** How many completed trials failed that criterion. */
-    failingCriterionCount?: number;
-    /** The task's reliability page (dashboard /runs/task/<taskName>). */
-    reliabilityUrl: string;
-}
-export declare function groupSummaryLines(input: GroupSummaryInput): string[];
-/** [DECISION 2026-07-05] group exit code: 0 iff at least one trial completed
- *  AND every completed trial passed; 1 when a completed trial failed; 2 when
- *  nothing completed. Documented next to the k=1 mapping in
- *  src/hosted/errors.ts. */
-export declare function groupExitCode(rows: TrialRow[]): number;
-/** Modal failed-criterion text across the group's completed trials, as the
- *  short phrase the "start there" line renders. */
-export declare function mostCommonFailedCriterion(failures: string[]): {
-    phrase: string;
-    count: number;
-} | null;
-/** Flatten an errored trial's reason to one short row-friendly line. */
-export declare function shortReason(reason: string): string;
-/** FDRS-644 — the fix & green handoff, printed under the group summary when
- *  at least one COMPLETED trial failed (errored trials are sandbox noise —
- *  the answer there is re-run, not a code fix). Copy stays modest per the
- *  north-star honesty note ("don't sell a 5-trial bump as proof"): a
- *  greener set is a signal, the climb across re-runs is what to watch. */
-export declare function fixHandoffLines(input: {
-    fixPromptCommand: string;
-    rerunCommand: string;
-}): string[];

package/dist/src/runner/groupRender.js

@@ -1,144 +0,0 @@
-// SPDX-License-Identifier: Apache-2.0
-// FDRS-636 — pure terminal rendering for `pome run -n k` trial groups,
-// matching the design-of-record (CLI moments.dc.html moment 04,
-// task/code-model vocabulary):
-//
-//   -n sets how many isolated trials to run · the agent command comes from pome.json
-//   provisioning 5 isolated github twins … ready
-//   spawning agent <cmd> · from pome.json …
-//   trial 1  ✓  100      14.3s
-//   trial 2  ✓  96       12.1s
-//   trial 3  ✗  58       15.9s  <failing criteria summary>
-//   trial 5  ⚠  errored         <reason> — excluded
-//   ─────
-//   2 of 4 passed · 1 errored, excluded from the fraction
-//   <failing-criterion phrase> failed in 2 of 4 — start there
-//   full trace, per-criterion diffs, and the trial spread:
-//   → <reliability page url>
-//
-// Trial verdicts are NUMERIC SCORES from the cloud judge — never words (that
-// vocabulary belongs to `pome demo`, moment 01). Errored rows show no
-// duration and are EXCLUDED from the fraction's denominator.
-import { criterionPhrase } from "../demo/render.js";
-/** The muted hint under the command echo, naming where the agent command
- *  came from (pome.json / --agent / the built-in default). */
-export function flagHintLine(agentCommandSource) {
-    return `-n sets how many isolated trials to run · the agent command comes from ${agentCommandSource}`;
-}
-/** Printed once the upfront mints are done (the cloud provisions one
- *  isolated twin sandbox per session — ADR-012). FDRS-663: when the plan's
- *  concurrent-twin quota bounded the upfront mint below k, the bound is
- *  named honestly — k stays the design default, the wall-clock stretches. */
-export function provisioningLine(k, twins, bound) {
-    if (bound !== undefined && bound < k) {
-        return `provisioning ${bound} isolated ${twins.join("+")} twins … ready (plan concurrency ${bound} — ${k} trials reuse slots as they finish)`;
-    }
-    return `provisioning ${k} isolated ${twins.join("+")} twins … ready`;
-}
-export function spawningAgentLine(command, source) {
-    return `spawning agent ${command} · from ${source} …`;
-}
-// Column layout (moment 04): score field padded to 9 so durations align;
-// "errored" padded to the duration column (16) so reasons align with the
-// failing-criteria notes.
-export function trialRowLine(n, row) {
-    if (row.kind === "errored") {
-        return `trial ${n}  ⚠  ${"errored".padEnd(16)}${row.reason} — excluded`;
-    }
-    // A dash for the ungradable trial: it ran, and it asserts nothing. Reusing
-    // ✗ would make a grader gap look like the agent's failure at a glance, which
-    // is the whole reading F-925 removes.
-    const mark = row.verdict === "pass" ? "✓" : row.verdict === "incomplete" ? "–" : "✗";
-    const base = `trial ${n}  ${mark}  ${String(row.score).padEnd(9)}${row.seconds.toFixed(1)}s`;
-    return row.note ? `${base}  ${row.note}` : base;
-}
-export function groupSummaryLines(input) {
-    const completed = input.rows.filter((r) => r.kind === "completed");
-    const passed = completed.filter((r) => r.verdict === "pass").length;
-    const incomplete = completed.filter((r) => r.verdict === "incomplete").length;
-    // F-925 — the fraction's denominator is the GRADED trials. A trial that
-    // finalized but could not be fully graded leaves both the numerator and the
-    // denominator, so a 5-trial set with one of them reads "3 of 4", never the
-    // "4 of 5" that counted it as a pass.
-    const graded = completed.length - incomplete;
-    const errored = input.rows.length - completed.length;
-    const lines = ["─────"];
-    // The fraction counts GRADED trials only; incomplete and errored trials are
-    // named and excluded, never silently folded into the denominator. They stay
-    // two clauses rather than one: "the trial died" is ours to retry, "the trial
-    // ran and could not be graded" is a grader gap, and a reader told the wrong
-    // one goes looking in the wrong place.
-    let fraction;
-    if (graded === 0) {
-        fraction =
-            completed.length === 0 ? "no trials completed" : "no trials could be graded";
-    }
-    else {
-        fraction = `${passed} of ${graded} passed`;
-    }
-    if (incomplete > 0) {
-        fraction += ` · ${incomplete} incomplete, excluded from the fraction`;
-    }
-    if (errored > 0) {
-        fraction += ` · ${errored} errored, excluded from the fraction`;
-    }
-    lines.push(fraction);
-    if (input.failingCriterionPhrase &&
-        typeof input.failingCriterionCount === "number" &&
-        input.failingCriterionCount > 0 &&
-        completed.length > 0) {
-        lines.push(`${input.failingCriterionPhrase} failed in ${input.failingCriterionCount} of ${completed.length} — start there`);
-    }
-    // The dashboard handoff only makes sense when at least one run row exists.
-    if (completed.length > 0) {
-        lines.push("");
-        lines.push("full trace, per-criterion diffs, and the trial spread:");
-        lines.push(`→ ${input.reliabilityUrl}`);
-    }
-    return lines;
-}
-/** [DECISION 2026-07-05] group exit code: 0 iff at least one trial completed
- *  AND every completed trial passed; 1 when a completed trial failed; 2 when
- *  nothing completed. Documented next to the k=1 mapping in
- *  src/hosted/errors.ts. */
-export function groupExitCode(rows) {
-    const completed = rows.filter((r) => r.kind === "completed");
-    if (completed.length === 0)
-        return 2;
-    // F-925 — an ungradable trial is not a pass, so a group holding one cannot
-    // exit 0: green here would tell CI the set was verified when part of it was
-    // never checked. It stays 1 rather than 2 even when EVERY trial was
-    // incomplete — `2` means nothing completed, and these completed.
-    return completed.every((r) => r.verdict === "pass") ? 0 : 1;
-}
-/** Modal failed-criterion text across the group's completed trials, as the
- *  short phrase the "start there" line renders. */
-export function mostCommonFailedCriterion(failures) {
-    if (failures.length === 0)
-        return null;
-    const counts = new Map();
-    for (const text of failures) {
-        counts.set(text, (counts.get(text) ?? 0) + 1);
-    }
-    const [text, count] = [...counts.entries()].sort((a, b) => b[1] - a[1])[0];
-    return { phrase: criterionPhrase(text), count };
-}
-/** Flatten an errored trial's reason to one short row-friendly line. */
-export function shortReason(reason) {
-    const flat = reason.replace(/\s+/g, " ").trim();
-    return flat.length > 72 ? `${flat.slice(0, 69)}…` : flat;
-}
-/** FDRS-644 — the fix & green handoff, printed under the group summary when
- *  at least one COMPLETED trial failed (errored trials are sandbox noise —
- *  the answer there is re-run, not a code fix). Copy stays modest per the
- *  north-star honesty note ("don't sell a 5-trial bump as proof"): a
- *  greener set is a signal, the climb across re-runs is what to watch. */
-export function fixHandoffLines(input) {
-    return [
-        "",
-        "fix & green: hand the failure signatures to your coding agent —",
-        `  ${input.fixPromptCommand}`,
-        `after the fix lands, re-run the task:  ${input.rerunCommand}`,
-        "fresh trials, honestly counted — one greener set is a signal, not proof; the reliability page tracks the climb.",
-    ];
-}

package/dist/src/runner/mergeAdapterSignals.d.ts

@@ -1,27 +0,0 @@
-import { type Event } from "../types/shared.js";
-/**
- * F-1200 — give every twin HTTP row the tool call that caused it.
- *
- * The twin writes `parent_event_id: null` because it runs in its own process
- * and cannot know the agent-side `event_id`; the adapter knows the `event_id`
- * but never sees the twin's tape. This merge is the one place both halves are
- * in hand, so the join belongs here — and it is a pure data operation over two
- * finished files, with no dependency on the order the two writers ran in.
- *
- * The join key is the SDK's `tool_use_id`, which since F-1200 is what the
- * adapter stamps on `x-pome-correlation-id`. The twin persists that header as
- * `correlation_id` ALWAYS and as `tool_call_id` only when it pins
- * `stampToolCallId` (github's frozen tape shape) — so `correlation_id` is the
- * key that works for every twin, with `tool_call_id` preferred when present
- * because it is unambiguously the header rather than the request-id fallback.
- *
- * A row keeps its null parent when the id names no tool call: a pre-F-1200
- * `tlc_…`, a `req_…` from the no-header fallback, or a direct REST call made
- * outside any tool handler. An unresolvable parent is the honest answer there —
- * inventing one would put twin calls under tools that did not make them.
- */
-export declare function resolveTwinHttpParents(rows: Event[]): Event[];
-export declare function mergeAdapterSignalsIntoEvents(signalsPath: string, eventsJsonlPath: string): Promise<{
-    appended: number;
-    dropped: number;
-}>;

package/dist/src/runner/mergeAdapterSignals.js

@@ -1,137 +0,0 @@
-// SPDX-License-Identifier: Apache-2.0
-import { readFile, writeFile } from "node:fs/promises";
-import { eventSchema } from "../types/shared.js";
-import { redactEvent } from "../recorder/redaction.js";
-// Post-run merge of the adapter signals JSONL into the canonical events.jsonl
-// (FDRS-411 + FDRS-412). This is a pure ts-sort/interleave step implemented
-// inline so the OSS capture path has no dependency on any correlator package.
-//
-// Three sources write events.jsonl during a self-host run:
-//   1. The capture-server child appends `LlmCallEvent` rows as each CONNECT
-//      tunnel closes (FDRS-399) — capture-close order, not ts-order.
-//   2. The trace writer then appends `TwinHttpEvent` rows from the in-process
-//      twin recorder (FDRS-415).
-//   3. This helper reads `signals.jsonl` (HookEvent / ToolUseEvent /
-//      ToolResultEvent / SubagentSpawnEvent / LlmTurnEvent rows written by the
-//      agent subprocess via `POME_ADAPTER_SIGNALS_PATH`), validates each line
-//      against the M0 unified `eventSchema`, then **interleaves** the signal
-//      rows with the existing events.jsonl rows by ts ascending and rewrites
-//      the file. The merged file is the canonical view for `pome inspect`
-//      + dashboard upload.
-//
-// Robustness: a missing signals file, an empty file, malformed JSONL lines,
-// and signals that fail schema validation never crash the run. Invalid signal
-// lines are dropped and counted; the caller can log the drop count. Existing
-// events.jsonl rows that fail to parse are passed through unsorted at the
-// head of the file so a corrupted in-flight write is never silently dropped.
-/**
- * F-1200 — give every twin HTTP row the tool call that caused it.
- *
- * The twin writes `parent_event_id: null` because it runs in its own process
- * and cannot know the agent-side `event_id`; the adapter knows the `event_id`
- * but never sees the twin's tape. This merge is the one place both halves are
- * in hand, so the join belongs here — and it is a pure data operation over two
- * finished files, with no dependency on the order the two writers ran in.
- *
- * The join key is the SDK's `tool_use_id`, which since F-1200 is what the
- * adapter stamps on `x-pome-correlation-id`. The twin persists that header as
- * `correlation_id` ALWAYS and as `tool_call_id` only when it pins
- * `stampToolCallId` (github's frozen tape shape) — so `correlation_id` is the
- * key that works for every twin, with `tool_call_id` preferred when present
- * because it is unambiguously the header rather than the request-id fallback.
- *
- * A row keeps its null parent when the id names no tool call: a pre-F-1200
- * `tlc_…`, a `req_…` from the no-header fallback, or a direct REST call made
- * outside any tool handler. An unresolvable parent is the honest answer there —
- * inventing one would put twin calls under tools that did not make them.
- */
-export function resolveTwinHttpParents(rows) {
-    const eventIdByToolUseId = new Map();
-    for (const row of rows) {
-        if (row.kind === "ToolUseEvent")
-            eventIdByToolUseId.set(row.tool_use_id, row.event_id);
-    }
-    if (eventIdByToolUseId.size === 0)
-        return rows;
-    return rows.map((row) => {
-        if (row.kind !== "TwinHttpEvent")
-            return row;
-        // Never overwrite a parent the writer already established.
-        if (row.parent_event_id != null)
-            return row;
-        const causingToolUseId = row.tool_call_id ?? row.correlation_id ?? null;
-        if (causingToolUseId === null)
-            return row;
-        const parentEventId = eventIdByToolUseId.get(causingToolUseId);
-        return parentEventId === undefined ? row : { ...row, parent_event_id: parentEventId };
-    });
-}
-export async function mergeAdapterSignalsIntoEvents(signalsPath, eventsJsonlPath) {
-    let rawSignals;
-    try {
-        rawSignals = await readFile(signalsPath, "utf8");
-    }
-    catch {
-        return { appended: 0, dropped: 0 };
-    }
-    let dropped = 0;
-    const signalRows = [];
-    for (const line of rawSignals.split("\n")) {
-        if (line.length === 0)
-            continue;
-        let parsed;
-        try {
-            parsed = JSON.parse(line);
-        }
-        catch {
-            dropped += 1;
-            continue;
-        }
-        const result = eventSchema.safeParse(parsed);
-        if (!result.success) {
-            dropped += 1;
-            continue;
-        }
-        signalRows.push(redactEvent(result.data));
-    }
-    if (signalRows.length === 0)
-        return { appended: 0, dropped };
-    let rawEvents;
-    try {
-        rawEvents = await readFile(eventsJsonlPath, "utf8");
-    }
-    catch {
-        rawEvents = "";
-    }
-    const eventRows = [];
-    const unparseablePassthrough = [];
-    for (const line of rawEvents.split("\n")) {
-        if (line.length === 0)
-            continue;
-        let parsed;
-        try {
-            parsed = JSON.parse(line);
-        }
-        catch {
-            unparseablePassthrough.push(line);
-            continue;
-        }
-        const result = eventSchema.safeParse(parsed);
-        if (result.success) {
-            eventRows.push(redactEvent(result.data));
-        }
-        else {
-            // A schema-invalid row on disk means the writer drifted from the M0
-            // schema; preserving the raw line is safer than dropping it silently.
-            unparseablePassthrough.push(line);
-        }
-    }
-    // Concat, resolve twin-HTTP parentage, then stable sort by ts. ISO-8601 with
-    // `Z` sorts chronologically under lexicographic compare.
-    const merged = resolveTwinHttpParents(eventRows.concat(signalRows));
-    merged.sort((a, b) => (a.ts < b.ts ? -1 : a.ts > b.ts ? 1 : 0));
-    const sortedJsonl = merged.map((r) => JSON.stringify(r)).join("\n");
-    const head = unparseablePassthrough.length > 0 ? unparseablePassthrough.join("\n") + "\n" : "";
-    await writeFile(eventsJsonlPath, head + sortedJsonl + "\n");
-    return { appended: signalRows.length, dropped };
-}

package/dist/src/runner/ports.d.ts

@@ -1 +0,0 @@
-export declare function getAvailablePort(): Promise<number>;

package/dist/src/runner/ports.js

@@ -1,21 +0,0 @@
-// SPDX-License-Identifier: Apache-2.0
-import { createServer } from "node:net";
-// NOTE: allocate-then-close hands back a port that is free at close time; a
-// caller that rebinds it races any other process that grabs it in the gap.
-// Pre-existing and acceptable for local dev twins (loopback, short-lived).
-export async function getAvailablePort() {
-    return new Promise((resolve, reject) => {
-        const server = createServer();
-        server.on("error", reject);
-        server.listen(0, "127.0.0.1", () => {
-            const address = server.address();
-            if (typeof address === "object" && address) {
-                const { port } = address;
-                server.close(() => resolve(port));
-            }
-            else {
-                server.close(() => reject(new Error("Could not allocate a local port")));
-            }
-        });
-    });
-}