Commit Graph
4 Commits
Author SHA1 Message Date
ci-check 3e27168cea fix(#5951): commandcode truncation record uses single-newline JSONL terminator
The commandcode branch of emitUpstreamTruncation emitted a blank line
("\n\n") after the error record. The commandcode wire is bare JSONL and
every other record on it (nativeErrorChunk, legacyCompletionChunk,
emitPreflightError) is single-newline terminated; a blank line is not a
valid JSONL record and chokes strict consumers at the moment the stream
already failed. Revert to single newline and pin the invariant in the
commandcode-plugin-pipe test (no blank line, endsWith }\n).

PR description claimed the commandcode branch "keeps its shape" from
#5958 — it did not; this restores it.

(cherry picked from commit 910bc13249)
2026-11-13 10:38:34 +08:00
ci-check 1a928c3acd fix: keep commandcode plugin-pipe filter state across deltas
pipePluginJsonlWithStrip flushed its tag-echo/marker filters after every JSONL line. The filters hold partial tag heads and marker prefixes across deltas by design; a per-line flush destroyed that state, so a render tag split across two text-delta lines leaked its ref into client-visible prose, a held prefix at the terminal frame was silently dropped, and a forged marker line completed across deltas escaped stripping. The SSE pipe (pipePluginChatWithStrip) already resolves tails only before terminal frames / EOF / read failure — mirror that here: one filter instance per prose field, tails written back as synthetic lines of the original event type before finish/error/EOF/truncation. Regression tests pin all three facets (#1295).
2026-11-09 23:33:55 +08:00
awork 5d36420e88 Merge branch 'master' into PR #1444 — resolve 9-file conflict against split pipeline (#1440) 2026-10-18 22:23:39 +08:00
ework-agent b818b0ad5b fix: review hardening for declared custom-wire endpoints (#1295)
- F1: reject userinfo in normalizeMatch (loudly, like search/hash) instead of
  silently minting a credentials-less origin claim
- F3: rewrap user branch mirrors unwrap's text-part join — block-content user
  messages are never silently blanked mid-forward (WC-2)
- F4: warn when a provider explicitProtocol pin overrides a declaration
- F6: declared-endpoint probes (GET/HEAD/empty-body POST) are not flagged
  "unrecognized path"; undeclared paths still warn (scoped carve-out)
- F7: drop dead meta.reasoningEffort (reasoning_effort round-trips via
  extraParams)
- F8: document why the host-side loader uses console.error
- F9: coverage — commandcode plugin pipe (tag-echo strip / verbatim relay /
  terminal fragment drop / in-band truncation), commandcode branches of the
  three stream-error emitters, duplicate-tool-name verbatim replay pin
- F2/F5: WC-2 empty-message note; docs for two-gate URL semantics (declare
  the URL the request lands on) + userinfo rejection
2026-09-27 09:57:01 +08:00