devlyn-cli 3.2.1 → 3.3.1

package/benchmark/auto-resolve/fixtures/retired/F34-cli-settle-inflight/spec.md

@@ -1,59 +0,0 @@
----
-id: "F34-cli-settle-inflight"
-title: "Settle command with in-flight authorizations"
-status: planned
-complexity: high
-depends-on: []
----
-
-# F34 Settle command with in-flight authorizations
-
-## Context
-
-`bench-cli` gets a `settle` command that previews a batch of credit
-transfers between accounts. Every transfer must be authorized through the
-seeded gateway module before settlement. The gateway is slow, so
-authorizations for different transfers must be able to overlap — but the
-ledger math must stay exact and order-stable.
-
-## Requirements
-
-- [ ] `bench-cli settle --input <path>` reads JSON shaped as `{ "transfers": [{ "id": string, "from": string, "to": string, "amount": number }] }`.
-- [ ] Account starting balances come from `data/accounts.json`. The command must not modify `data/accounts.json`.
-- [ ] Every transfer is authorized by calling `authorize(transfer)` from `lib/gateway.js` exactly once per transfer. Do not modify, reimplement, or bypass `lib/gateway.js`.
-- [ ] Authorizations must be able to overlap: while one transfer's authorization is awaited, later transfers' authorizations must be able to start. The seeded gateway records the maximum number of authorizations in flight at once in `data/gateway-stats.json`; settling the six-transfer sample in `## Verification` must record `high_water` of at least `3`.
-- [ ] Regardless of the order in which authorizations complete, transfers settle in file order, each exactly once. A transfer is accepted when the sender's balance — after all earlier-in-file accepted transfers — covers the amount; otherwise it is rejected.
-- [ ] Each rejected transfer produces exact row shape `{ "id": string, "error": "insufficient_funds", "available": number, "requested": number }`, where `available` is the sender's balance at that transfer's turn in file order.
-- [ ] Validation happens before any authorization starts. Invalid JSON, missing or non-string `id`/`from`/`to`, unknown account, or non-positive or non-integer `amount` exits `2` and writes exactly one JSON error object to stderr with shape `{ "error": "invalid_input", "reason": string }`, printing nothing to stdout.
-- [ ] On success, write exactly one JSON object to stdout and no stderr. Keys: `accepted` (array of transfer ids in file order), `rejected` (array of rejected rows in file order), `balances` (object with the final balance of every account in `data/accounts.json`).
-- [ ] `tests/cli.test.js` is updated. Existing tests still pass AND at least two new tests cover `settle`: one where a later-in-file transfer depends on an earlier-in-file transfer's settlement, and one rejection.
-
-## Constraints
-
-- **No new npm dependencies.**
-- **No silent catches.** If parsing or file reading fails, emit a visible JSON error to stderr and exit `2`.
-- **No extra stdout/stderr text** on the success path; downstream tooling parses stdout as JSON.
-- Balances are integer credits; no floating-point money.
-
-## Out of Scope
-
-- Persisting settlement results (settle is a preview; `data/accounts.json` stays untouched).
-- Changing server routes, web UI, or `lib/gateway.js`.
-- Retry, timeout, or failure handling for the gateway beyond what it returns.
-- Touching `server/`, `web/`, or `tests/server.test.js`.
-
-## Verification
-
-- `node --test tests/cli.test.js` exits 0.
-- Settling a six-transfer file where authorizations complete in reverse file order still yields file-order settlement: exact `accepted`, `rejected`, and `balances` values.
-- `data/gateway-stats.json` shows `calls` equal to the number of transfers and `high_water` of at least `3`.
-- An unknown account exits `2`, prints one JSON error to stderr, and prints no stdout.
-- `git diff --stat` shows only `bin/cli.js` and `tests/cli.test.js` touched (accounts and gateway are seeded by setup, not the arm).
-
-## Solo-headroom hypothesis
-
-A capable solo_claude baseline is expected to miss the decoupling of
-authorization completion order from file-order settlement — applying
-balance changes as authorizations resolve instead of at each transfer's
-file-order turn; observable command
-`node "$BENCH_FIXTURE_DIR/verifiers/ordered-settlement.js"` exposes the miss.

package/benchmark/auto-resolve/fixtures/retired/F34-cli-settle-inflight/task.txt

@@ -1,9 +0,0 @@
-Add a `settle` command to `bench-cli` so users can run `bench-cli settle --input <path>` with a transfers JSON file. Starting balances come from `data/accounts.json` (read-only — settle is a preview and must not modify it). Every transfer must be authorized by calling `authorize(transfer)` from the seeded `lib/gateway.js` exactly once; do not modify or bypass that module.
-
-The gateway is slow, so authorizations for different transfers must be able to overlap — while one is awaited, later ones must be able to start. The seeded gateway records `calls` and the in-flight `high_water` mark in `data/gateway-stats.json`; a six-transfer batch must reach a high-water mark of at least 3.
-
-No matter which order authorizations finish in, transfers settle in file order, each exactly once: a transfer is accepted when the sender's balance after all earlier-in-file accepted transfers covers the amount, otherwise it is rejected with the exact row `{ "id", "error": "insufficient_funds", "available", "requested" }` where `available` is the balance at that transfer's file-order turn.
-
-Validate the whole file before any authorization starts: bad JSON, missing fields, unknown accounts, or non-positive/non-integer amounts exit `2` with exactly one JSON error object `{ "error": "invalid_input", "reason": string }` on stderr and nothing on stdout. On success print exactly one JSON object with `accepted` (ids in file order), `rejected` (rows in file order), and `balances` (every account) — and nothing on stderr.
-
-Update `tests/cli.test.js`: existing tests still pass, plus at least two new settle tests (one where a later transfer depends on an earlier transfer's settlement, one rejection). No new npm dependencies. Only touch `bin/cli.js` and `tests/cli.test.js`.

package/benchmark/auto-resolve/fixtures/retired/F34-cli-settle-inflight/verifiers/ordered-settlement.js

@@ -1,88 +0,0 @@
-'use strict';
-// F34 hidden verifier — file-order settlement under inverted completion order.
-// Transfer ids encode gateway latency (trailing digits = ms), so the FIRST
-// transfer in the file finishes authorization LAST. Applying balances in
-// completion order (or rejecting against pre-batch balances) flips t-60 and
-// t-40; only strict file-order settlement produces this exact output.
-
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-
-// Structural equality: object key order is NOT part of the visible contract;
-// array order IS. Codex fairness-audit fix (stringify equality made JSON
-// property order a hidden oracle narrower than spec.md).
-function deepEqual(a, b) {
-  if (a === b) return true;
-  if (Array.isArray(a) && Array.isArray(b)) {
-    return a.length === b.length && a.every((v, i) => deepEqual(v, b[i]));
-  }
-  if (a && b && typeof a === 'object' && typeof b === 'object' && !Array.isArray(a) && !Array.isArray(b)) {
-    const ka = Object.keys(a).sort();
-    const kb = Object.keys(b).sort();
-    return deepEqual(ka, kb) && ka.every((k) => deepEqual(a[k], b[k]));
-  }
-  return false;
-}
-
-const inputPath = path.join(os.tmpdir(), `settle-input-${process.pid}.json`);
-fs.writeFileSync(inputPath, JSON.stringify({
-  transfers: [
-    { id: 't-80', from: 'acct-a', to: 'acct-b', amount: 70 },
-    { id: 't-60', from: 'acct-b', to: 'acct-c', amount: 50 },
-    { id: 't-40', from: 'acct-a', to: 'acct-d', amount: 40 },
-    { id: 't-20', from: 'acct-c', to: 'acct-a', amount: 100 },
-    { id: 't-10', from: 'acct-d', to: 'acct-b', amount: 5 },
-    { id: 't-5', from: 'acct-b', to: 'acct-a', amount: 25 }
-  ]
-}));
-
-const work = process.env.BENCH_WORKDIR;
-const cli = path.join(work, 'bin', 'cli.js');
-const result = spawnSync('node', [cli, 'settle', '--input', inputPath], {
-  cwd: work,
-  encoding: 'utf8'
-});
-
-let out;
-try {
-  out = JSON.parse(result.stdout);
-} catch {
-  out = null;
-}
-
-const expected = {
-  accepted: ['t-80', 't-60', 't-20', 't-10', 't-5'],
-  rejected: [
-    { id: 't-40', error: 'insufficient_funds', available: 30, requested: 40 }
-  ],
-  balances: { 'acct-a': 155, 'acct-b': 0, 'acct-c': 0, 'acct-d': 5 }
-};
-
-let stats;
-try {
-  stats = JSON.parse(fs.readFileSync(path.join(work, 'data', 'gateway-stats.json'), 'utf8'));
-} catch {
-  stats = null;
-}
-
-const accountsUntouched = (() => {
-  try {
-    const seeded = JSON.parse(fs.readFileSync(path.join(work, 'data', 'accounts.json'), 'utf8'));
-    return deepEqual(seeded, { 'acct-a': 100, 'acct-b': 0, 'acct-c': 50, 'acct-d': 10 });
-  } catch {
-    return false;
-  }
-})();
-
-const ok = result.status === 0
-  && result.stderr === ''
-  && deepEqual(out, expected)
-  && stats !== null
-  && stats.calls === 6
-  && stats.high_water >= 3
-  && accountsUntouched;
-
-console.log(JSON.stringify({ ok, status: result.status, stderr: result.stderr, out, stats, accountsUntouched }));
-process.exit(ok ? 0 : 1);

package/benchmark/auto-resolve/fixtures/retired/F34-cli-settle-inflight/verifiers/reject-invalid.js

@@ -1,45 +0,0 @@
-'use strict';
-// F34 hidden verifier — validation happens before any authorization: an
-// unknown account exits 2 with one JSON error object on stderr, no stdout,
-// and the gateway records zero calls for the run.
-
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-
-const work = process.env.BENCH_WORKDIR;
-const statsPath = path.join(work, 'data', 'gateway-stats.json');
-fs.rmSync(statsPath, { force: true });
-
-const inputPath = path.join(os.tmpdir(), `settle-bad-${process.pid}.json`);
-fs.writeFileSync(inputPath, JSON.stringify({
-  transfers: [
-    { id: 't-30', from: 'acct-a', to: 'acct-zzz', amount: 10 }
-  ]
-}));
-
-const cli = path.join(work, 'bin', 'cli.js');
-const result = spawnSync('node', [cli, 'settle', '--input', inputPath], {
-  cwd: work,
-  encoding: 'utf8'
-});
-
-let err;
-try {
-  err = JSON.parse(result.stderr);
-} catch {
-  err = null;
-}
-
-const gatewayNeverCalled = !fs.existsSync(statsPath);
-
-const ok = result.status === 2
-  && result.stdout === ''
-  && err !== null
-  && err.error === 'invalid_input'
-  && typeof err.reason === 'string'
-  && gatewayNeverCalled;
-
-console.log(JSON.stringify({ ok, status: result.status, stdout: result.stdout, err, gatewayNeverCalled }));
-process.exit(ok ? 0 : 1);

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/NOTES.md

@@ -1,30 +0,0 @@
-# F35 CLI apply journal
-
-## Failure mode
-
-Detects implementations that flatten the composite ordering/replay/atomicity
-contract into the easy shape: apply-in-file-order against pre-batch stock
-with per-row persistence. Three discriminators: (a) `applied` order and
-journal append order must follow priority-desc with file-order ties (final
-quantities alone cannot catch this — addition commutes); (b) the failing
-op's `available` is measured at its turn AFTER higher-priority ops changed
-stock (rollback verifier: 15, not the pre-batch 10); (c) any failure leaves
-both files byte-for-byte unchanged. In-file duplicate `op_id` is a
-validation error while a journaled `op_id` is a per-op skip — the
-distinction is the replay axis (Tier-1 "A1" from memory
-`project_pair_fixture_tier1_2026_05_05`; keyword-hidden: spec never says
-atomic/transaction/idempotent/rollback).
-
-## Fairness
-
-Every verifier assertion quotes a visible spec bullet via `contract_refs`
-(lint-fixtures enforced). Verifiers reset the seeded files before running so
-command order cannot leak state between checks. No hidden shape, tie-break,
-or availability rule exists outside spec.md.
-
-## Headroom prediction (pre-registered, unmeasured)
-
-bare ≤ 60 (expected to miss at-its-turn availability or journal append
-order), solo ≤ 80 (hypothesis: evaluates availability against pre-batch or
-file-order state). To be measured with `headroom-gate.py` before any
-pair-evidence claims; this fixture carries no measurement claim until then.

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/RETIRED.md

@@ -1,16 +0,0 @@
-# F35 retired
-
-Retired from the active golden suite after headroom run
-`iter-0039-headroom-f34-f35`.
-
-Reason: `solo_claude` scored 97, exceeding the headroom ceiling of 80, while
-bare scored 50. `solo_claude` correctly implemented the `{ "ops": [...] }`
-input contract, priority ordering, rollback, and duplicate-op handling; bare
-failed only because it assumed a bare top-level array instead of the required
-object shape — an input-shape slip, not evidence the task is hard. The
-solo_claude arm also ran to the full 1500s timeout before finishing
-(elapsed_seconds 1501, INVOKE_EXIT=124), but its diff still verified clean, so
-the fixture is not pair-lift evidence.
-
-Future use: rework the visible contract or hidden verifiers so the task
-creates a fair pair-risk-probe gap without hiding requirements from the spec.

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/expected.json

@@ -1,64 +0,0 @@
-{
-  "verification_commands": [
-    {
-      "cmd": "node --test tests/cli.test.js",
-      "exit_code": 0,
-      "stdout_contains": [],
-      "stdout_not_contains": ["not ok "]
-    },
-    {
-      "cmd": "node \"$BENCH_FIXTURE_DIR/verifiers/priority-apply.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "An op whose `op_id` is already listed in the journal's `applied` array is recorded as skipped and changes nothing, regardless of its other fields.",
-        "Non-skipped ops apply in descending `priority`; ties apply in file order.",
-        "On success, persist the final quantities to `data/inventory.json`, append the applied `op_id`s to the journal's `applied` array in application order, and write exactly one JSON object to stdout with keys `applied` (op_ids in application order), `skipped` (op_ids in file order), and `inventory` (final quantities for every sku)."
-      ]
-    },
-    {
-      "cmd": "node \"$BENCH_FIXTURE_DIR/verifiers/rollback.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "An op fails when applying its `delta` would take the sku's quantity below zero, evaluated at its turn in that order, with exact error shape `{ \"error\": \"insufficient_stock\", \"op_id\": string, \"sku\": string, \"available\": number, \"requested\": number }` where `available` is the quantity at that op's turn and `requested` is the absolute value of its `delta`.",
-        "If any op fails, nothing persists: `data/inventory.json` and `data/journal.json` are byte-for-byte unchanged, the command exits `2`, and exactly one JSON error object is written to stderr with nothing on stdout."
-      ]
-    },
-    {
-      "cmd": "node \"$BENCH_FIXTURE_DIR/verifiers/dup-op.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "or an `op_id` that appears more than once in the input file exits `2` and writes exactly one JSON error object to stderr with shape `{ \"error\": \"invalid_input\", \"reason\": string }`, printing nothing to stdout and changing neither file."
-      ]
-    }
-  ],
-  "forbidden_patterns": [
-    {
-      "pattern": "catch\\s*\\([^)]*\\)\\s*\\{[^}]*return\\s+(null|undefined|''|\\{\\})",
-      "description": "silent catch returning fallback in apply path",
-      "files": ["bin/cli.js"],
-      "severity": "disqualifier"
-    },
-    {
-      "pattern": "catch\\s*\\([^)]*\\)\\s*\\{\\s*\\}",
-      "description": "empty catch block",
-      "files": ["bin/cli.js"],
-      "severity": "disqualifier"
-    },
-    {
-      "pattern": "/\\*\\s*eslint-disable",
-      "description": "eslint-disable without scoped justification",
-      "files": ["bin/cli.js"],
-      "severity": "disqualifier"
-    }
-  ],
-  "required_files": ["bin/cli.js", "tests/cli.test.js", "data/inventory.json", "data/journal.json"],
-  "forbidden_files": [],
-  "max_deps_added": 0,
-  "spec_output_files": ["bin/cli.js", "tests/cli.test.js"]
-}

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/metadata.json

@@ -1,10 +0,0 @@
-{
-  "id": "F35-cli-apply-journal",
-  "category": "high-risk",
-  "difficulty": "high",
-  "timeout_seconds": 1500,
-  "required_tools": ["node"],
-  "browser": false,
-  "deps_change_expected": false,
-  "intent": "Add a bench-cli apply command that applies inventory adjustments in priority order with journal-based replay skipping, at-its-turn stock checks, exact JSON output, and all-or-nothing persistence of inventory and journal."
-}

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/setup.sh

@@ -1,21 +0,0 @@
-#!/usr/bin/env bash
-# F35 setup — seed inventory and the replay journal.
-set -e
-
-mkdir -p data
-
-cat > data/inventory.json <<'JSON'
-{
-  "widget": 10,
-  "gadget": 4,
-  "gizmo": 0
-}
-JSON
-
-cat > data/journal.json <<'JSON'
-{
-  "applied": ["op-900"]
-}
-JSON
-
-exit 0

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/spec.md

@@ -1,58 +0,0 @@
----
-id: "F35-cli-apply-journal"
-title: "Apply command with journal replay and all-or-nothing persistence"
-status: planned
-complexity: high
-depends-on: []
----
-
-# F35 Apply command with journal replay and all-or-nothing persistence
-
-## Context
-
-`bench-cli` gets an `apply` command that applies a file of inventory
-adjustments to `data/inventory.json`. Runs are re-deliverable: a journal at
-`data/journal.json` records which ops have already been applied, so a
-delivered-again op must not change inventory twice. A batch either fully
-persists or leaves both files untouched.
-
-## Requirements
-
-- [ ] `bench-cli apply --input <path>` reads JSON shaped as `{ "ops": [{ "op_id": string, "sku": string, "delta": number, "priority": number }] }`.
-- [ ] Quantities come from `data/inventory.json`; the applied-op record comes from the journal's `applied` array in `data/journal.json`. Both are seeded by setup.
-- [ ] Validation happens before any application. Invalid JSON, missing or non-string `op_id`/`sku`, unknown `sku`, non-integer `delta` or `priority`, or an `op_id` that appears more than once in the input file exits `2` and writes exactly one JSON error object to stderr with shape `{ "error": "invalid_input", "reason": string }`, printing nothing to stdout and changing neither file.
-- [ ] An op whose `op_id` is already listed in the journal's `applied` array is recorded as skipped and changes nothing, regardless of its other fields.
-- [ ] Non-skipped ops apply in descending `priority`; ties apply in file order.
-- [ ] An op fails when applying its `delta` would take the sku's quantity below zero, evaluated at its turn in that order, with exact error shape `{ "error": "insufficient_stock", "op_id": string, "sku": string, "available": number, "requested": number }` where `available` is the quantity at that op's turn and `requested` is the absolute value of its `delta`.
-- [ ] If any op fails, nothing persists: `data/inventory.json` and `data/journal.json` are byte-for-byte unchanged, the command exits `2`, and exactly one JSON error object is written to stderr with nothing on stdout.
-- [ ] On success, persist the final quantities to `data/inventory.json`, append the applied `op_id`s to the journal's `applied` array in application order, and write exactly one JSON object to stdout with keys `applied` (op_ids in application order), `skipped` (op_ids in file order), and `inventory` (final quantities for every sku). Nothing is written to stderr on success.
-- [ ] `tests/cli.test.js` is updated. Existing tests still pass AND at least two new tests cover `apply`: one success mixing a journaled op with different priorities, and one failing batch that leaves both files unchanged.
-
-## Constraints
-
-- **No new npm dependencies.**
-- **No silent catches.** If parsing or file reading fails, emit a visible JSON error to stderr and exit `2`.
-- **No extra stdout/stderr text** on the success path; downstream tooling parses stdout as JSON.
-- Quantities are integers; no fractional inventory.
-
-## Out of Scope
-
-- Changing server routes, web UI, or journal schema.
-- Concurrency across multiple `apply` processes.
-- Pruning or rewriting existing journal entries.
-- Touching `server/`, `web/`, or `tests/server.test.js`.
-
-## Verification
-
-- `node --test tests/cli.test.js` exits 0.
-- A batch mixing a journaled op, unequal priorities, and a priority tie yields exact `applied` order, exact `skipped`, exact final `inventory`, and the journal grows by exactly the applied op_ids in that order.
-- A batch whose failing op is only discoverable after higher-priority ops have consumed or added stock reports `available` at that op's turn and leaves both files byte-for-byte unchanged.
-- A duplicated `op_id` in the input file exits `2` with one JSON error on stderr and no stdout.
-- `git diff --stat` shows only `bin/cli.js` and `tests/cli.test.js` touched (inventory and journal are seeded by setup, not the arm).
-
-## Solo-headroom hypothesis
-
-A capable solo_claude baseline is expected to miss that each op's
-`available` stock is evaluated at its turn in priority order rather than
-against the pre-batch inventory or file order; observable command
-`node "$BENCH_FIXTURE_DIR/verifiers/rollback.js"` exposes the miss.

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/task.txt

@@ -1,9 +0,0 @@
-Add an `apply` command to `bench-cli` so users can run `bench-cli apply --input <path>` with an ops JSON file of inventory adjustments. Quantities live in `data/inventory.json` and previously applied op ids live in the `applied` array of `data/journal.json` (both seeded).
-
-Validate the whole file before applying anything: bad JSON, missing/invalid fields, unknown sku, non-integer delta or priority, or the same `op_id` appearing twice in one file exits `2` with exactly one JSON error object `{ "error": "invalid_input", "reason": string }` on stderr, nothing on stdout, and neither file changed.
-
-An op whose `op_id` is already in the journal is recorded as skipped and changes nothing — whatever its other fields say. Everything else applies in descending `priority` (ties in file order). An op fails if its `delta` would push the sku below zero at its turn in that order; the error is the exact object `{ "error": "insufficient_stock", "op_id", "sku", "available", "requested" }` with `available` measured at that op's turn. Any failure means nothing persists — inventory and journal stay byte-for-byte identical and the command exits `2`.
-
-On success, write the final quantities back to `data/inventory.json`, append applied op ids to the journal in application order, and print exactly one JSON object with `applied` (application order), `skipped` (file order), and `inventory` — with nothing on stderr.
-
-Update `tests/cli.test.js`: existing tests still pass, plus at least two apply tests (one success mixing a journaled op with different priorities, one failing batch that leaves both files unchanged). No new npm dependencies. Only touch `bin/cli.js` and `tests/cli.test.js`.

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/verifiers/dup-op.js

@@ -1,54 +0,0 @@
-'use strict';
-// F35 hidden verifier — an op_id duplicated WITHIN the input file is a
-// validation error (whole file rejected, nothing changes), distinct from a
-// journal replay which is a per-op skip. Exit 2, one JSON error object on
-// stderr, no stdout, both files untouched.
-
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-
-const work = process.env.BENCH_WORKDIR;
-const invPath = path.join(work, 'data', 'inventory.json');
-const jrnPath = path.join(work, 'data', 'journal.json');
-
-fs.writeFileSync(invPath, JSON.stringify({ widget: 10, gadget: 4, gizmo: 0 }, null, 2) + '\n');
-fs.writeFileSync(jrnPath, JSON.stringify({ applied: ['op-900'] }, null, 2) + '\n');
-const invBefore = fs.readFileSync(invPath, 'utf8');
-const jrnBefore = fs.readFileSync(jrnPath, 'utf8');
-
-const inputPath = path.join(os.tmpdir(), `apply-dup-${process.pid}.json`);
-fs.writeFileSync(inputPath, JSON.stringify({
-  ops: [
-    { op_id: 'op-20', sku: 'widget', delta: -1, priority: 3 },
-    { op_id: 'op-21', sku: 'gadget', delta: 1, priority: 2 },
-    { op_id: 'op-20', sku: 'gizmo', delta: 2, priority: 1 }
-  ]
-}));
-
-const cli = path.join(work, 'bin', 'cli.js');
-const result = spawnSync('node', [cli, 'apply', '--input', inputPath], {
-  cwd: work,
-  encoding: 'utf8'
-});
-
-let err;
-try {
-  err = JSON.parse(result.stderr);
-} catch {
-  err = null;
-}
-
-const filesUnchanged = fs.readFileSync(invPath, 'utf8') === invBefore
-  && fs.readFileSync(jrnPath, 'utf8') === jrnBefore;
-
-const ok = result.status === 2
-  && result.stdout === ''
-  && err !== null
-  && err.error === 'invalid_input'
-  && typeof err.reason === 'string'
-  && filesUnchanged;
-
-console.log(JSON.stringify({ ok, status: result.status, stdout: result.stdout, err, filesUnchanged }));
-process.exit(ok ? 0 : 1);

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/verifiers/priority-apply.js

@@ -1,82 +0,0 @@
-'use strict';
-// F35 hidden verifier — success path mixing a journaled (replayed) op, unequal
-// priorities, and a priority tie. Final quantities are order-independent
-// (addition commutes), so the discriminator is the exact `applied` ORDER and
-// the journal append order: priority-desc with file-order ties, replayed op
-// skipped regardless of its (otherwise failing) fields.
-
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-
-// Structural equality: object key order is NOT part of the visible contract;
-// array order IS. Codex fairness-audit fix (stringify equality made JSON
-// property order a hidden oracle narrower than spec.md).
-function deepEqual(a, b) {
-  if (a === b) return true;
-  if (Array.isArray(a) && Array.isArray(b)) {
-    return a.length === b.length && a.every((v, i) => deepEqual(v, b[i]));
-  }
-  if (a && b && typeof a === 'object' && typeof b === 'object' && !Array.isArray(a) && !Array.isArray(b)) {
-    const ka = Object.keys(a).sort();
-    const kb = Object.keys(b).sort();
-    return deepEqual(ka, kb) && ka.every((k) => deepEqual(a[k], b[k]));
-  }
-  return false;
-}
-
-const work = process.env.BENCH_WORKDIR;
-const invPath = path.join(work, 'data', 'inventory.json');
-const jrnPath = path.join(work, 'data', 'journal.json');
-
-// Reset seeds so this verifier is order-independent from other commands.
-fs.writeFileSync(invPath, JSON.stringify({ widget: 10, gadget: 4, gizmo: 0 }, null, 2) + '\n');
-fs.writeFileSync(jrnPath, JSON.stringify({ applied: ['op-900'] }, null, 2) + '\n');
-
-const inputPath = path.join(os.tmpdir(), `apply-ok-${process.pid}.json`);
-fs.writeFileSync(inputPath, JSON.stringify({
-  ops: [
-    { op_id: 'op-1', sku: 'widget', delta: -4, priority: 1 },
-    { op_id: 'op-900', sku: 'widget', delta: -9, priority: 9 },
-    { op_id: 'op-2', sku: 'widget', delta: -5, priority: 5 },
-    { op_id: 'op-3', sku: 'gadget', delta: -4, priority: 5 },
-    { op_id: 'op-4', sku: 'widget', delta: 3, priority: 0 }
-  ]
-}));
-
-const cli = path.join(work, 'bin', 'cli.js');
-const result = spawnSync('node', [cli, 'apply', '--input', inputPath], {
-  cwd: work,
-  encoding: 'utf8'
-});
-
-let out;
-try {
-  out = JSON.parse(result.stdout);
-} catch {
-  out = null;
-}
-
-const expected = {
-  applied: ['op-2', 'op-3', 'op-1', 'op-4'],
-  skipped: ['op-900'],
-  inventory: { widget: 4, gadget: 0, gizmo: 0 }
-};
-
-let inv; let jrn;
-try {
-  inv = JSON.parse(fs.readFileSync(invPath, 'utf8'));
-  jrn = JSON.parse(fs.readFileSync(jrnPath, 'utf8'));
-} catch {
-  inv = null; jrn = null;
-}
-
-const ok = result.status === 0
-  && result.stderr === ''
-  && deepEqual(out, expected)
-  && deepEqual(inv, expected.inventory)
-  && deepEqual(jrn, { applied: ['op-900', 'op-2', 'op-3', 'op-1', 'op-4'] });
-
-console.log(JSON.stringify({ ok, status: result.status, stderr: result.stderr, out, inv, jrn }));
-process.exit(ok ? 0 : 1);

package/benchmark/auto-resolve/fixtures/retired/F35-cli-apply-journal/verifiers/rollback.js

@@ -1,77 +0,0 @@
-'use strict';
-// F35 hidden verifier — the failing op is only discoverable AFTER a
-// higher-priority op has added stock: op-12 (priority 8) raises widget
-// 10 -> 15, then op-11 (priority 5) requests 20 and fails with
-// available 15 — not 10 (pre-batch / file-order would report 10).
-// Both files must be byte-for-byte unchanged afterward.
-
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-const { spawnSync } = require('node:child_process');
-
-// Structural equality: object key order is NOT part of the visible contract;
-// array order IS. Codex fairness-audit fix (stringify equality made JSON
-// property order a hidden oracle narrower than spec.md).
-function deepEqual(a, b) {
-  if (a === b) return true;
-  if (Array.isArray(a) && Array.isArray(b)) {
-    return a.length === b.length && a.every((v, i) => deepEqual(v, b[i]));
-  }
-  if (a && b && typeof a === 'object' && typeof b === 'object' && !Array.isArray(a) && !Array.isArray(b)) {
-    const ka = Object.keys(a).sort();
-    const kb = Object.keys(b).sort();
-    return deepEqual(ka, kb) && ka.every((k) => deepEqual(a[k], b[k]));
-  }
-  return false;
-}
-
-const work = process.env.BENCH_WORKDIR;
-const invPath = path.join(work, 'data', 'inventory.json');
-const jrnPath = path.join(work, 'data', 'journal.json');
-
-fs.writeFileSync(invPath, JSON.stringify({ widget: 10, gadget: 4, gizmo: 0 }, null, 2) + '\n');
-fs.writeFileSync(jrnPath, JSON.stringify({ applied: ['op-900'] }, null, 2) + '\n');
-const invBefore = fs.readFileSync(invPath, 'utf8');
-const jrnBefore = fs.readFileSync(jrnPath, 'utf8');
-
-const inputPath = path.join(os.tmpdir(), `apply-fail-${process.pid}.json`);
-fs.writeFileSync(inputPath, JSON.stringify({
-  ops: [
-    { op_id: 'op-10', sku: 'gadget', delta: 2, priority: 9 },
-    { op_id: 'op-11', sku: 'widget', delta: -20, priority: 5 },
-    { op_id: 'op-12', sku: 'widget', delta: 5, priority: 8 }
-  ]
-}));
-
-const cli = path.join(work, 'bin', 'cli.js');
-const result = spawnSync('node', [cli, 'apply', '--input', inputPath], {
-  cwd: work,
-  encoding: 'utf8'
-});
-
-let err;
-try {
-  err = JSON.parse(result.stderr);
-} catch {
-  err = null;
-}
-
-const expectedErr = {
-  error: 'insufficient_stock',
-  op_id: 'op-11',
-  sku: 'widget',
-  available: 15,
-  requested: 20
-};
-
-const filesUnchanged = fs.readFileSync(invPath, 'utf8') === invBefore
-  && fs.readFileSync(jrnPath, 'utf8') === jrnBefore;
-
-const ok = result.status === 2
-  && result.stdout === ''
-  && deepEqual(err, expectedErr)
-  && filesUnchanged;
-
-console.log(JSON.stringify({ ok, status: result.status, stdout: result.stdout, err, filesUnchanged }));
-process.exit(ok ? 0 : 1);