fix(harness): move harness-specific output handling into the harness plugins (#1855)

This commit is contained in:
jason.woltje committed 2026-11-06 18:27:58 -06:00
1 parent ad9b2dee42
commit 08b7db413b
14 files changed
+129 -83

No files matched your search

+2 -1
View File
@@ -63,13 +63,14 @@ export const KINDS = Object.freeze({
// bundle({ dir, files, session, write, quote }) -> { files, digests, sources }, its own bundle files
// env({ files, policy, tools, session }) -> its adapter variables, written into session.json
// turnEnd() -> "marker" (a turn ends only with the turn marker) | "exit"
// outputPolicy({ proxy }) -> "adapter" | "non-newline-stdout" | "stdout"
// transcript({ runDir, store }) -> the directory its transcripts land in, for usage
// compactions({ store, cursors, budget, streams, first }) -> { found, cursors, known, reason, version },
// the session store's compactions past the ledger's cursors (row 307)
harness: Object.freeze({
kind: "harness", interfaceVersion: 1, switch: "list",
exports: Object.freeze(["adapter", "levels", "preflight", "version", "countsAccount", "mounts", "builtinWeb", "builtins",
"typedName", "reliesOn", "gateTimeout", "bundle", "env", "turnEnd", "transcript", "compactions"]),
"typedName", "reliesOn", "gateTimeout", "bundle", "env", "turnEnd", "outputPolicy", "transcript", "compactions"]),
}),
// Optional proxy telemetry (row 333): read({ readUsageQueue }) -> the drained events. The bus
// hands the module that one function and nothing else from its management client (R3).