test(chat): require interactive tool parity across advertised harnesses
This commit is contained in:
@@ -32,3 +32,29 @@ not provide durable callback recovery; a disconnected transport is reported as
|
||||
an error rather than claiming old requests are still actionable.
|
||||
|
||||
Claude is not advertised as a backend until its sidecar and login flow are wired.
|
||||
|
||||
## Web interaction contract
|
||||
|
||||
Both advertised chat adapters (OpenCode V2 and Codex) implement the same server
|
||||
contract for uploads, models, pending approvals, questions, form replies,
|
||||
interrupts, command readback and bounded output. Compile-time assertions and a
|
||||
browser regression run against both backend identities protect this contract;
|
||||
support is not satisfied by text streaming alone. Pi's pipeline executor is not
|
||||
advertised as a Pi web-chat adapter, and an unavailable Claude adapter is not
|
||||
presented as a working choice.
|
||||
|
||||
Codex uploads use native `localImage` for verified supported images. Other files
|
||||
are retained intact with an explicit server-local reference; the model's own
|
||||
tools inspect them rather than pretending their contents were already loaded.
|
||||
The saved next-turn model is also respected with uploads. Model sandbox and
|
||||
approval policy remain in force.
|
||||
|
||||
Codex's paged history retains tool and reasoning items, including structured MCP
|
||||
errors and Code Mode outputs, instead of discarding everything except text.
|
||||
Unknown item kinds remain inspectable. Tool detail is explicitly truncated at
|
||||
64 KiB, not silently represented as complete. Running commands and their output
|
||||
use real command items plus read-only thread history; no unsupported terminal
|
||||
endpoint, process control, resumed turn or experimental flag is invented.
|
||||
Output reads are bounded and verify thread ownership. The installed Codex
|
||||
version exposes no API for controlling an agent-owned terminal through the
|
||||
separate, client-owned `command/exec` process IDs; those IDs are never conflated.
|
||||
|
||||
Reference in New Issue
Block a user