PR #32390 live verification
main: 73fb49d0b3a61bff74aebc362fc6c17d6c0d39be
PR: d3f7d7fd0500a79160a5919f54b6127f3a26b26b

Each checkout ran vp i and a separate real dev server, never simultaneously.
Main ports: server 16733, web 8693. PR ports: server 13773, web 5733.
Each app got a project for /home/user/main and a Codex ACP gpt-6.1-sol thread through Chrome/Playwright. The real provider ran pwd and git rev-parse --is-inside-work-tree successfully. Native Codex gpt-6.1-sol also succeeded on main.

Protocol probe: manually send a JSON-RPC request on the real Codex ACP process stdout socket using pidfd_getfd, with strace passively capturing reads on its stdin. No application source edits, fake provider, substituted handlers, mocks, fixtures, demo data or test hooks. These malformed requests were deliberate protocol probes, not requests spontaneously produced by the model.

Request:
{"jsonrpc":"2.0","id":"verify-error-data","method":"elicitation/create","params":{}}

Main response (reproduces the bug):
{
  "jsonrpc": "2.0",
  "id": "verify-error-data",
  "error": {
    "_tag": "Cause",
    "code": -32602,
    "message": "Invalid payload for ACP extension method 'elicitation/create'.",
    "data": [
      {
        "_tag": "Fail",
        "error": {
          "code": -32602,
          "message": "Invalid payload for ACP extension method 'elicitation/create'.",
          "data": {
            "issueCount": 17,
            "issueKinds": [
              "AnyOf",
              "Composite",
              "Pointer",
              "MissingKey"
            ],
            "maximumPathDepth": 1
          }
        }
      }
    ]
  }
}

PR response and neighboring probes:
[
  {
    "jsonrpc": "2.0",
    "id": "verify-error-data",
    "error": {
      "code": -32602,
      "message": "Invalid payload for ACP extension method 'elicitation/create'.",
      "data": {
        "issueCount": 17,
        "issueKinds": [
          "AnyOf",
          "Composite",
          "Pointer",
          "MissingKey"
        ],
        "maximumPathDepth": 1
      }
    }
  },
  {
    "jsonrpc": "2.0",
    "id": "verify-no-data",
    "error": {
      "code": -32601,
      "message": "Method not found: x/verification-unknown"
    }
  },
  [
    {
      "jsonrpc": "2.0",
      "id": 0,
      "result": {
        "connectionId": "7538858e-0829-4d6c-a782-4e5589d3e3cd"
      }
    },
    {
      "jsonrpc": "2.0",
      "id": "verify-batch-error",
      "error": {
        "code": -32602,
        "message": "Invalid payload for ACP extension method 'elicitation/create'.",
        "data": {
          "issueCount": 17,
          "issueKinds": [
            "AnyOf",
            "Composite",
            "Pointer",
            "MissingKey"
          ],
          "maximumPathDepth": 1
        }
      }
    }
  ],
  {
    "jsonrpc": "2.0",
    "id": "verify-disconnect",
    "result": {}
  }
]

Assertions: PR error.data exactly equals main's nested Fail.error.data. Code -32602 and message unchanged. Private _tag removed. Unknown method has code -32601 and no data key. Mixed mcp/connect success + elicitation failure batch keeps numeric 0 and string verify-batch-error ids. MCP connection explicitly disconnected.

Blacksmith: vp i && vp test run packages/effect-acp/src/protocol.test.ts packages/effect-acp/src/agent.test.ts packages/effect-acp/src/client.test.ts
3 files, 74 tests passed. Hosted CI: 33 successful, 0 failing, 0 pending.

After all protocol probes, a follow-up UI turn on the same Codex ACP process (PID 46268) ran printf and returned acp-error-recovery-ok. It completed in the real client. No source files changed.