docs: streamjson2 built but deliberately not deployed

The corrected runtime image exists on gw-04 and stays there. It delivers no observability until TurnEvent::ToolCall can be emitted for observed calls, so deploying it alone would be a provider output-format change carrying risk for no benefit. Production stays on the known-good :v084. The harmful v1 image was deleted from both hosts so it cannot be redeployed by accident. Co-Authored-By: Claude Opus 5 <[email protected]>
2026-08-20 09:55:33 -07:00
parent 536adddd0f
commit afb1e29bf3
1 changed files with 9 additions and 3 deletions
@@ -76,9 +76,15 @@ output, which is precisely why it would have gone unnoticed.
 Fixed in fork commit `295d6d3b8`: the calls are logged, never returned. **Both
 runtimes were rolled back to the known-good image** (`:v084` on gw-04,
-`:toolchain` locally) rather than leaving the harmful build in production. A
+`:toolchain` locally), and the harmful v1 image was deleted from both hosts so
-corrected image (`clawmates-runtime:streamjson2`) was building on gw-04 at
+it cannot be redeployed by accident.
-session end — `ssh gw-04 'tail -3 /tmp/rtbuild/build2.log'`.
+
 A corrected image **`clawmates-runtime:streamjson2`** (from `295d6d3`) is built
 and sitting on gw-04, **deliberately not deployed**. It delivers no
 observability until the event channel exists, so shipping it would be a
 provider output-format change with real risk and no current benefit.
 Production stays on `:v084`. Deploy `streamjson2` only as part of the
 event-channel work below — not on its own.
 **The real fix for mission-tier tool observability** is to plumb an event
 channel into the provider so it can emit `TurnEvent::ToolCall` for calls it