docs(fin): close the DeepSeek Responses wire unit

All three fixes are on origin/dev and verified in the remote file content, and
the 14 tests of the unit's suite ran green on ubuntu-latest and macos-latest.

Records why the windows-latest job is not a blocker for this unit: every
DeepSeek-named assertion in that job passed and 2107 tests had already run
before it went silent after the SSE/relay tests and was cancelled by timeout.
The three runs that landed before these commits reached the branch had already
failed, one with a Bun internal assertion crash. That is the open Windows Bun
stability work, not this unit.

Author: lidge-jun

…_deepseek_responses_wire/000_research.md …_deepseek_responses_wire/000_research.mddevlog/_plan/260801_deepseek_responses_wire/000_research.md renamed to devlog/_fin/260801_deepseek_responses_wire/000_research.md devlog/_plan/260801_deepseek_responses_wire/000_research.md renamed to devlog/_fin/260801_deepseek_responses_wire/000_research.md

@@ -76,6 +76,28 @@ rather than by provider capability. Phase 2 widened that set to include DeepSeek
 correct fix narrows the write site; it was left out of scope here rather than expanded
 into mid-phase.
 
-## Not pushed
-
-Eight commits sit on local `dev`. Pushing needs explicit approval and was not given.
+## Pushed and verified on the remote
+
+All nine commits are on `origin/dev` (each confirmed with
+`git merge-base --is-ancestor`), and the remote file content carries all three fixes:
+`responsesPath: "/responses"`, the inbound-scoped `modelWireDefaults` entry, and
+`statelessResponses: true`. The clone-isolation guard is on the remote too.
+
+CI on `5f9434ab2` — the last SHA whose code tree is identical to HEAD, since the only
+later commit touches a devlog file — ran all 14 tests of
+`tests/deepseek-inbound-wire.test.ts` green on both `ubuntu-latest` and
+`macos-latest`, along with the three `npm-global` jobs.
+
+The `windows-latest` job did not report. It is a pre-existing platform problem, not a
+regression from this unit:
+
+- The DeepSeek suite is not implicated — every DeepSeek-named assertion in that job
+  passed, and 2107 tests had already passed when the job stalled.
+- The job went silent after the SSE/relay tests at 22:04 and was cancelled by timeout
+  at 22:18.
+- The three runs immediately BEFORE this unit's commits reached the branch
+  (`8c8832137`, `18545f87e`, `89cb08fc9`) already failed, `8c8832137` with
+  `panic(thread 8988): Internal assertion failure` / `oh no: Bun has crashed`.
+
+That belongs to the open Windows Bun stability work
+(`devlog/_plan/260731_windows_bun_stability/`), not here.