devlyn-cli 3.2.1 → 3.3.0

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/expected.json

@@ -1,56 +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/idempotent-close.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "Exact duplicate transactions are idempotent: apply the first copy once and count later exact copies in `duplicates_ignored`.",
-        "Apply accepted unique transactions in chronological order by `occurred_at` ascending, then `id` ascending.",
-        "Negative closing balances are allowed and must be reported, not rejected."
-      ]
-    },
-    {
-      "cmd": "node \"$BENCH_FIXTURE_DIR/verifiers/conflicting-duplicate.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "Conflicting duplicate transaction ids are invalid input. A duplicate id is conflicting when any field other than `id` differs from the first transaction with that id.",
-        "Invalid input exits `2`, writes exactly one JSON error object to stderr, and writes nothing to stdout.",
-        "Conflicting duplicate transaction ids use the exact stderr JSON shape `{ \"error\": \"conflicting_duplicate\", \"id\": string }`."
-      ]
-    }
-  ],
-  "forbidden_patterns": [
-    {
-      "pattern": "catch\\s*\\([^)]*\\)\\s*\\{[^}]*return\\s+(null|undefined|''|\\{\\})",
-      "description": "silent catch returning fallback in ledger 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"],
-  "forbidden_files": [],
-  "max_deps_added": 0,
-  "spec_output_files": ["bin/cli.js", "tests/cli.test.js"]
-}

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/metadata.json

@@ -1,10 +0,0 @@
-{
-  "id": "F22-cli-ledger-close",
-  "category": "high-risk",
-  "difficulty": "high",
-  "timeout_seconds": 1500,
-  "required_tools": ["node"],
-  "browser": false,
-  "deps_change_expected": false,
-  "intent": "Add a bench-cli ledger-close command that reads account opening balances and transaction events, applies chronological idempotent ledger rules, rejects conflicting duplicate transaction ids, and prints exact closing balances and audit counts."
-}

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/setup.sh

@@ -1,2 +0,0 @@
-#!/usr/bin/env bash
-set -e

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/spec.md

@@ -1,64 +0,0 @@
----
-id: "F22-cli-ledger-close"
-title: "Ledger close command"
-status: planned
-complexity: high
-depends-on: []
----
-
-# F22 Ledger close command
-
-## Context
-
-Add a `bench-cli ledger-close --input <path>` command that reads account
-opening balances and transaction events, applies chronological idempotent
-ledger rules, rejects conflicting duplicate transaction ids, and prints exact
-closing balances and audit counts.
-
-The command is used in finance-style reconciliation. Determinism matters more
-than convenience: every amount is integer cents, every accepted event is applied
-once, and duplicate ids must not silently corrupt balances.
-
-## Requirements
-
-- [ ] `bench-cli ledger-close --input <path>` reads JSON shaped as `{ "accounts": Array<Account>, "transactions": Array<Transaction> }`.
-- [ ] Each account has `{ "id": string, "currency": string, "opening_cents": number }`.
-- [ ] Each transaction has `{ "id": string, "account": string, "currency": string, "kind": "debit" | "credit", "amount_cents": number, "occurred_at": string }`.
-- [ ] Validate before applying balances: account ids are unique, transaction ids are non-empty strings, account references exist, currencies match the referenced account, `amount_cents` is a positive integer, and `kind` is either `debit` or `credit`.
-- [ ] Conflicting duplicate transaction ids are invalid input. A duplicate id is conflicting when any field other than `id` differs from the first transaction with that id.
-- [ ] Exact duplicate transactions are idempotent: apply the first copy once and count later exact copies in `duplicates_ignored`.
-- [ ] Apply accepted unique transactions in chronological order by `occurred_at` ascending, then `id` ascending.
-- [ ] A `debit` subtracts `amount_cents`; a `credit` adds `amount_cents`.
-- [ ] Negative closing balances are allowed and must be reported, not rejected.
-- [ ] Invalid input exits `2`, writes exactly one JSON error object to stderr, and writes nothing to stdout.
-- [ ] Conflicting duplicate transaction ids use the exact stderr JSON shape `{ "error": "conflicting_duplicate", "id": string }`.
-- [ ] On success, write exactly one JSON object to stdout and no stderr. Keys: `accounts`, `applied_count`, `duplicates_ignored`.
-- [ ] Output `accounts` sorted by account id ascending. Each row has keys `id`, `currency`, `closing_cents`.
-- [ ] `tests/cli.test.js` is updated. Existing tests still pass AND at least two ledger tests cover one success case and one invalid-input case.
-
-## Constraints
-
-- **No new npm dependencies.**
-- **No floating-money output.** All amounts are integer cents.
-- **No silent catches.** Invalid input and file-read failures must surface as JSON errors with exit `2`.
-- **No mutation of the input file.**
-- **No extra stdout/stderr text** on the success path; downstream tooling parses stdout as JSON.
-- **Touch only `bin/cli.js` and `tests/cli.test.js`.**
-
-## Out of Scope
-
-- Exchange rates.
-- Decimal currency parsing.
-- Persistence or database writes.
-- Account creation from transactions.
-- Touching `server/`, `web/`, or `tests/server.test.js`.
-
-## Verification
-
-- `node --test tests/cli.test.js` exits 0.
-- Exact duplicate transactions are counted in `duplicates_ignored` and applied once.
-- Conflicting duplicate transaction ids exit `2`, write one JSON error to stderr, and write no stdout.
-- Conflicting duplicate transaction ids use the exact stderr JSON shape `{ "error": "conflicting_duplicate", "id": string }`.
-- Transactions are applied in chronological order by `occurred_at` ascending, then `id` ascending.
-- Negative closing balances are allowed and appear in output.
-- `git diff --stat` shows only `bin/cli.js` and `tests/cli.test.js` touched.

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/task.txt

@@ -1,7 +0,0 @@
-Add a `ledger-close` command to `bench-cli` so users can run `bench-cli ledger-close --input <path>` with a JSON file containing account opening balances and transaction events. It should apply chronological idempotent ledger rules, reject conflicting duplicate transaction ids, and print exact closing balances and audit counts.
-
-The input has `accounts` with `id`, `currency`, and `opening_cents`, and `transactions` with `id`, `account`, `currency`, `kind`, `amount_cents`, and `occurred_at`. Validate the full input before applying balances. Exact duplicate transactions should be applied only once and counted in `duplicates_ignored`; duplicate ids with any conflicting field should make the whole input invalid. Apply accepted unique transactions by `occurred_at` ascending, then id ascending. Debits subtract, credits add, and negative closing balances are allowed.
-
-On success, stdout must be exactly parseable JSON and stderr must be empty. The output has `accounts`, `applied_count`, and `duplicates_ignored`; accounts are sorted by id and each row has `id`, `currency`, and `closing_cents`. Invalid input or file-read failures should exit `2`, print exactly one JSON error object to stderr, and print nothing to stdout. Conflicting duplicate transaction ids must use the exact stderr JSON shape `{ "error": "conflicting_duplicate", "id": string }`.
-
-Update `tests/cli.test.js` so existing tests still pass and add at least two ledger tests: one success case and one invalid-input case. No new npm dependencies. Only touch `bin/cli.js` and `tests/cli.test.js`.

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/verifiers/conflicting-duplicate.js

@@ -1,34 +0,0 @@
-'use strict';
-const assert = require('node:assert');
-const { spawnSync } = require('node:child_process');
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-
-const work = process.env.BENCH_WORKDIR || process.cwd();
-const cli = path.join(work, 'bin', 'cli.js');
-const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'f22-conflict-'));
-const input = path.join(tmp, 'ledger.json');
-
-fs.writeFileSync(input, JSON.stringify({
-  accounts: [
-    { id: 'cash', currency: 'USD', opening_cents: 1000 }
-  ],
-  transactions: [
-    { id: 'same-id', account: 'cash', currency: 'USD', kind: 'credit', amount_cents: 100, occurred_at: '2026-01-01T00:00:00Z' },
-    { id: 'same-id', account: 'cash', currency: 'USD', kind: 'credit', amount_cents: 101, occurred_at: '2026-01-01T00:00:00Z' }
-  ]
-}), 'utf8');
-
-const proc = spawnSync('node', [cli, 'ledger-close', '--input', input], {
-  cwd: work,
-  encoding: 'utf8'
-});
-assert.strictEqual(proc.status, 2);
-assert.strictEqual(proc.stdout, '');
-const parsed = JSON.parse(proc.stderr);
-assert.deepStrictEqual(parsed, {
-  error: 'conflicting_duplicate',
-  id: 'same-id'
-});
-console.log(JSON.stringify({ ok: true }));

package/benchmark/auto-resolve/fixtures/F22-cli-ledger-close/verifiers/idempotent-close.js

@@ -1,41 +0,0 @@
-'use strict';
-const assert = require('node:assert');
-const { execFileSync } = require('node:child_process');
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-
-const work = process.env.BENCH_WORKDIR || process.cwd();
-const cli = path.join(work, 'bin', 'cli.js');
-const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'f22-ledger-'));
-const input = path.join(tmp, 'ledger.json');
-
-const tx = { id: 't-dup', account: 'cash', currency: 'USD', kind: 'debit', amount_cents: 1200, occurred_at: '2026-01-03T00:00:00Z' };
-fs.writeFileSync(input, JSON.stringify({
-  accounts: [
-    { id: 'cash', currency: 'USD', opening_cents: 1000 },
-    { id: 'receivable', currency: 'USD', opening_cents: 200 }
-  ],
-  transactions: [
-    { id: 't-late', account: 'receivable', currency: 'USD', kind: 'credit', amount_cents: 50, occurred_at: '2026-01-05T00:00:00Z' },
-    tx,
-    { ...tx },
-    { id: 't-early', account: 'cash', currency: 'USD', kind: 'credit', amount_cents: 300, occurred_at: '2026-01-01T00:00:00Z' }
-  ]
-}), 'utf8');
-
-const stdout = execFileSync('node', [cli, 'ledger-close', '--input', input], {
-  cwd: work,
-  encoding: 'utf8',
-  stdio: ['ignore', 'pipe', 'pipe']
-});
-const parsed = JSON.parse(stdout);
-assert.deepStrictEqual(parsed, {
-  accounts: [
-    { id: 'cash', currency: 'USD', closing_cents: 100 },
-    { id: 'receivable', currency: 'USD', closing_cents: 250 }
-  ],
-  applied_count: 3,
-  duplicates_ignored: 1
-});
-console.log(JSON.stringify({ ok: true }));

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/NOTES.md

@@ -1,39 +0,0 @@
-# F23 CLI fulfillment wave
-
-## Failure mode
-
-This fixture detects plausible allocators that pass simple order tests while
-missing production-critical interactions: priority before input order,
-all-or-nothing rollback, FEFO lot ordering, distance tie-breaks, and
-single-warehouse constraints.
-
-## Pipeline phase target
-
-PLAN must separate validation, order processing, tentative allocation, rollback,
-and final output sorting. IMPLEMENT must avoid partial mutation leaks. VERIFY
-should construct counterexamples where a partial allocation looks locally valid
-but corrupts later orders.
-
-## Why existing fixtures do not cover it
-
-F21 covers interval scheduling. F16 covers quote arithmetic. F22 was too easy
-for bare in the first calibration run. This fixture targets allocation rollback
-and inventory consumption across multiple dimensions.
-
-## Measurement status
-
-Pair evidence passed in `20260510-f16-f23-f25-combined-proof`: bare `33`,
-solo_claude `66`, pair `97`, margin `+31`, wall `2.25x`,
-arm `l2_risk_probes`, verdict `pair_evidence_passed`.
-
-## Solo-headroom hypothesis
-
-A capable solo_claude baseline is expected to miss all-or-nothing rollback after
-a higher-priority order consumes stock first; observable command
-`node "$BENCH_FIXTURE_DIR/verifiers/priority-rollback.js"` exposes the miss.
-
-## Retirement
-
-Retire or replace if both bare and solo consistently exceed the headroom
-thresholds, or if a later logistics fixture provides the same rollback and
-allocation-order signal with less wall time.

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/expected.json

@@ -1,56 +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-rollback.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "Process orders by `priority` descending, then `submitted_at` ascending, then `id` ascending.",
-        "An order is all-or-nothing. If any line cannot be fully allocated, reject the order and roll back all allocations tentatively made for that order.",
-        "Accepted allocations reduce stock for later orders in the same wave. Rejected orders do not reduce stock."
-      ]
-    },
-    {
-      "cmd": "node \"$BENCH_FIXTURE_DIR/verifiers/single-warehouse-fefo.js\"",
-      "exit_code": 0,
-      "stdout_contains": ["\"ok\":true"],
-      "stdout_not_contains": [],
-      "contract_refs": [
-        "For a line where `single_warehouse` is `true`, the entire line quantity must come from one warehouse. It may use multiple lots inside that warehouse, but it must not split across warehouses.",
-        "Lot choice inside a warehouse is FEFO: `expires` ascending, then lot id ascending.",
-        "`remaining` is sorted by warehouse id, then sku, then expires, then lot."
-      ]
-    }
-  ],
-  "forbidden_patterns": [
-    {
-      "pattern": "catch\\s*\\([^)]*\\)\\s*\\{[^}]*return\\s+(null|undefined|''|\\{\\})",
-      "description": "silent catch returning fallback in fulfillment 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"],
-  "forbidden_files": [],
-  "max_deps_added": 0,
-  "spec_output_files": ["bin/cli.js", "tests/cli.test.js"]
-}

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/metadata.json

@@ -1,10 +0,0 @@
-{
-  "id": "F23-cli-fulfillment-wave",
-  "category": "high-risk",
-  "difficulty": "high",
-  "timeout_seconds": 1500,
-  "required_tools": ["node"],
-  "browser": false,
-  "deps_change_expected": false,
-  "intent": "Add a bench-cli fulfill-wave command that allocates prioritized orders across warehouses and inventory lots using all-or-nothing order rollback, FEFO lot choice, distance tie-breaks, and single-warehouse line constraints."
-}

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/setup.sh

@@ -1,2 +0,0 @@
-#!/usr/bin/env bash
-set -e

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/spec.md

@@ -1,76 +0,0 @@
----
-id: "F23-cli-fulfillment-wave"
-title: "Fulfillment wave allocator"
-status: planned
-complexity: high
-depends-on: []
----
-
-# F23 Fulfillment wave allocator
-
-## Context
-
-Add a `bench-cli fulfill-wave --input <path>` command that allocates
-prioritized orders across warehouses and inventory lots using all-or-nothing
-order rollback, FEFO lot choice, distance tie-breaks, and single-warehouse line
-constraints.
-
-The allocator prepares a batch for warehouse pickers. A plausible partial plan
-is worse than no plan: rejected orders must not consume stock, and accepted
-orders must be deterministic.
-
-## Requirements
-
-- [ ] `bench-cli fulfill-wave --input <path>` reads JSON shaped as `{ "warehouses": Array<Warehouse>, "orders": Array<Order> }`.
-- [ ] Each warehouse has `{ "id": string, "distance": number, "lots": Array<Lot> }`.
-- [ ] Each lot has `{ "sku": string, "lot": string, "qty": number, "expires": "YYYY-MM-DD" }`.
-- [ ] Each order has `{ "id": string, "priority": number, "submitted_at": string, "lines": Array<Line> }`.
-- [ ] Each line has `{ "sku": string, "qty": number, "single_warehouse": boolean }`.
-- [ ] Validate before allocation: ids are non-empty strings, quantities are positive integers, dates parse as ISO dates, priorities are numbers, and order ids are unique.
-- [ ] Process orders by `priority` descending, then `submitted_at` ascending, then `id` ascending.
-- [ ] An order is all-or-nothing. If any line cannot be fully allocated, reject the order and roll back all allocations tentatively made for that order.
-- [ ] For a normal line where `single_warehouse` is `false`, allocation may split across warehouses and lots.
-- [ ] For a line where `single_warehouse` is `true`, the entire line quantity must come from one warehouse. It may use multiple lots inside that warehouse, but it must not split across warehouses.
-- [ ] Warehouse choice order is `distance` ascending, then warehouse id ascending.
-- [ ] Lot choice inside a warehouse is FEFO: `expires` ascending, then lot id ascending.
-- [ ] Accepted allocations reduce stock for later orders in the same wave. Rejected orders do not reduce stock.
-- [ ] If an order cannot be fully allocated, reject with `{ "id": string, "reason": "insufficient_stock" }`.
-- [ ] Invalid input exits `2`, writes exactly one JSON error object to stderr, and writes nothing to stdout.
-- [ ] On success, write exactly one JSON object to stdout and no stderr. Keys: `accepted`, `rejected`, `remaining`.
-- [ ] `accepted` is ordered by processing order. Each accepted row has keys `id`, `allocations`.
-- [ ] Each allocation row has keys `sku`, `warehouse`, `lot`, `qty` and rows are ordered in the sequence stock was chosen.
-- [ ] `rejected` is ordered by original input order. Each rejected row has keys `id`, `reason`.
-- [ ] `remaining` is sorted by warehouse id, then sku, then expires, then lot. Each row has keys `warehouse`, `sku`, `lot`, `qty`, `expires`.
-- [ ] `tests/cli.test.js` is updated. Existing tests still pass AND at least two fulfill-wave tests cover one accepted allocation and one rejected all-or-nothing order.
-
-## Constraints
-
-- **No new npm dependencies.**
-- **No silent catches.** Invalid input and file-read failures must surface as JSON errors with exit `2`.
-- **No mutation of the input file.**
-- **No extra stdout/stderr text** on the success path; downstream tooling parses stdout as JSON.
-- **Touch only `bin/cli.js` and `tests/cli.test.js`.**
-
-## Out of Scope
-
-- Carrier selection.
-- Package dimensions.
-- Backorders or partial order acceptance.
-- Persistence beyond stdout.
-- Touching `server/`, `web/`, or `tests/server.test.js`.
-
-## Verification
-
-- `node --test tests/cli.test.js` exits 0.
-- A higher-priority order consumes stock before a lower-priority order even when the lower-priority order appears first in the input.
-- A rejected order rolls back all tentative allocations and does not reduce stock available to later orders.
-- `single_warehouse: true` does not split a line across warehouses even if total stock across warehouses is enough.
-- Lot choice is FEFO by expiry date, then lot id.
-- `remaining` is sorted by warehouse id, then sku, then expires, then lot.
-- `git diff --stat` shows only `bin/cli.js` and `tests/cli.test.js` touched.
-
-## Solo-headroom hypothesis
-
-A capable solo_claude baseline is expected to miss all-or-nothing rollback after
-a higher-priority order tentatively allocates FEFO lots; observable command
-`node "$BENCH_FIXTURE_DIR/verifiers/priority-rollback.js"` exposes the miss.

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/task.txt

@@ -1,7 +0,0 @@
-Add a `fulfill-wave` command to `bench-cli` so users can run `bench-cli fulfill-wave --input <path>` with a JSON file containing warehouses, inventory lots, and prioritized orders. It should allocate orders across warehouses and lots using all-or-nothing order rollback, FEFO lot choice, distance tie-breaks, and single-warehouse line constraints.
-
-Process orders by priority descending, then submitted_at ascending, then id ascending. Warehouse choice is distance ascending, then warehouse id ascending. Lot choice inside a warehouse is FEFO: expires ascending, then lot id ascending. Normal lines may split across warehouses and lots, but a line with `single_warehouse: true` must be fully allocated from one warehouse, though it may use multiple lots inside that warehouse. If any line in an order cannot be fully allocated, reject that order and roll back every tentative allocation for that order.
-
-On success, stdout must be exactly parseable JSON and stderr must be empty. The output has `accepted`, `rejected`, and `remaining`. Invalid input or file-read failures should exit `2`, print exactly one JSON error object to stderr, and print nothing to stdout.
-
-Update `tests/cli.test.js` so existing tests still pass and add at least two fulfill-wave tests: one accepted allocation and one rejected all-or-nothing order. No new npm dependencies. Only touch `bin/cli.js` and `tests/cli.test.js`.

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/verifiers/priority-rollback.js

@@ -1,64 +0,0 @@
-'use strict';
-const assert = require('node:assert');
-const { execFileSync } = require('node:child_process');
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-
-const work = process.env.BENCH_WORKDIR || process.cwd();
-const cli = path.join(work, 'bin', 'cli.js');
-const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'f23-wave-'));
-const input = path.join(tmp, 'wave.json');
-
-fs.writeFileSync(input, JSON.stringify({
-  warehouses: [
-    {
-      id: 'near',
-      distance: 1,
-      lots: [
-        { sku: 'A', lot: 'n-old', qty: 2, expires: '2026-02-01' },
-        { sku: 'B', lot: 'n-b', qty: 1, expires: '2026-02-01' }
-      ]
-    },
-    {
-      id: 'far',
-      distance: 9,
-      lots: [
-        { sku: 'A', lot: 'f-a', qty: 3, expires: '2026-01-15' }
-      ]
-    }
-  ],
-  orders: [
-    { id: 'low-first', priority: 1, submitted_at: '2026-01-01T09:00:00Z', lines: [{ sku: 'A', qty: 2, single_warehouse: false }] },
-    { id: 'bad-middle', priority: 5, submitted_at: '2026-01-01T09:01:00Z', lines: [{ sku: 'B', qty: 1, single_warehouse: false }, { sku: 'C', qty: 1, single_warehouse: false }] },
-    { id: 'high-second', priority: 10, submitted_at: '2026-01-01T09:02:00Z', lines: [{ sku: 'A', qty: 5, single_warehouse: false }] },
-    { id: 'after-bad', priority: 4, submitted_at: '2026-01-01T09:03:00Z', lines: [{ sku: 'B', qty: 1, single_warehouse: false }] }
-  ]
-}), 'utf8');
-
-const stdout = execFileSync('node', [cli, 'fulfill-wave', '--input', input], {
-  cwd: work,
-  encoding: 'utf8',
-  stdio: ['ignore', 'pipe', 'pipe']
-});
-const parsed = JSON.parse(stdout);
-assert.deepStrictEqual(parsed.accepted, [
-  {
-    id: 'high-second',
-    allocations: [
-        { sku: 'A', warehouse: 'near', lot: 'n-old', qty: 2 },
-        { sku: 'A', warehouse: 'far', lot: 'f-a', qty: 3 }
-    ]
-  },
-  {
-    id: 'after-bad',
-    allocations: [
-      { sku: 'B', warehouse: 'near', lot: 'n-b', qty: 1 }
-    ]
-  }
-]);
-assert.deepStrictEqual(parsed.rejected, [
-  { id: 'low-first', reason: 'insufficient_stock' },
-  { id: 'bad-middle', reason: 'insufficient_stock' }
-]);
-console.log(JSON.stringify({ ok: true }));

package/benchmark/auto-resolve/fixtures/F23-cli-fulfillment-wave/verifiers/single-warehouse-fefo.js

@@ -1,66 +0,0 @@
-'use strict';
-const assert = require('node:assert');
-const { execFileSync } = require('node:child_process');
-const fs = require('node:fs');
-const os = require('node:os');
-const path = require('node:path');
-
-const work = process.env.BENCH_WORKDIR || process.cwd();
-const cli = path.join(work, 'bin', 'cli.js');
-const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'f23-single-'));
-const input = path.join(tmp, 'wave.json');
-
-fs.writeFileSync(input, JSON.stringify({
-  warehouses: [
-    {
-      id: 'east',
-      distance: 2,
-      lots: [
-        { sku: 'K', lot: 'e-late', qty: 2, expires: '2026-04-01' },
-        { sku: 'K', lot: 'e-early', qty: 1, expires: '2026-03-01' }
-      ]
-    },
-    {
-      id: 'west',
-      distance: 1,
-      lots: [
-        { sku: 'K', lot: 'w-only', qty: 2, expires: '2026-02-01' },
-        { sku: 'Z', lot: 'w-z', qty: 1, expires: '2026-02-01' }
-      ]
-    }
-  ],
-  orders: [
-    { id: 'single-ok', priority: 10, submitted_at: '2026-01-01T09:00:00Z', lines: [{ sku: 'K', qty: 3, single_warehouse: true }] },
-    { id: 'single-reject', priority: 9, submitted_at: '2026-01-01T09:01:00Z', lines: [{ sku: 'K', qty: 3, single_warehouse: true }] },
-    { id: 'normal-z', priority: 8, submitted_at: '2026-01-01T09:02:00Z', lines: [{ sku: 'Z', qty: 1, single_warehouse: false }] }
-  ]
-}), 'utf8');
-
-const stdout = execFileSync('node', [cli, 'fulfill-wave', '--input', input], {
-  cwd: work,
-  encoding: 'utf8',
-  stdio: ['ignore', 'pipe', 'pipe']
-});
-const parsed = JSON.parse(stdout);
-assert.deepStrictEqual(parsed.accepted, [
-  {
-    id: 'single-ok',
-    allocations: [
-      { sku: 'K', warehouse: 'east', lot: 'e-early', qty: 1 },
-      { sku: 'K', warehouse: 'east', lot: 'e-late', qty: 2 }
-    ]
-  },
-  {
-    id: 'normal-z',
-    allocations: [
-      { sku: 'Z', warehouse: 'west', lot: 'w-z', qty: 1 }
-    ]
-  }
-]);
-assert.deepStrictEqual(parsed.rejected, [
-  { id: 'single-reject', reason: 'insufficient_stock' }
-]);
-assert.deepStrictEqual(parsed.remaining, [
-  { warehouse: 'west', sku: 'K', lot: 'w-only', qty: 2, expires: '2026-02-01' }
-]);
-console.log(JSON.stringify({ ok: true }));

package/benchmark/auto-resolve/fixtures/F25-cli-cart-promotion-rules/NOTES.md

@@ -1,40 +0,0 @@
-# F25 CLI cart promotion rules
-
-## Failure mode
-
-This fixture detects checkout implementations that pass shallow cart tests while
-missing interaction invariants: duplicate-SKU aggregation, line-promotion order,
-order-coupon order, taxable base selection, free-shipping threshold timing, and
-externalized catalog data.
-
-## Pipeline phase target
-
-PLAN must preserve ordering between aggregation, validation, line promotions,
-coupon discount, tax, and shipping. IMPLEMENT must keep all money values in
-integer cents without new dependencies. VERIFY should execute adversarial cart
-examples rather than only checking a happy path.
-
-## Why existing fixtures do not cover it
-
-F16 covers quote tax rules, but not multiple line-promotion types plus an order
-coupon. F21/F23 cover scheduling/allocation, not checkout interaction ordering.
-This fixture keeps the F16-style fair visible-contract shape while testing a
-different checkout interaction.
-
-## Measurement status
-
-Pair evidence passed in `20260510-f16-f23-f25-combined-proof`: bare `25`,
-solo_claude `75`, pair `99`, margin `+24`, wall `1.65x`,
-arm `l2_risk_probes`, verdict `pair_evidence_passed`.
-
-## Solo-headroom hypothesis
-
-A capable solo_claude baseline is expected to miss the interaction between
-duplicate aggregation, line promotions, tax base, coupon order, and shipping;
-observable command `node "$BENCH_FIXTURE_DIR/verifiers/exact-success.js"` exposes the miss.
-
-## Retirement
-
-Retire or replace this fixture if either `bare` or `solo_claude` consistently
-reaches ceiling, or if a later fixture covers the same promotion-order and
-catalog-source failure mode with cleaner full-pipeline lift.