docs(code-runtime-python): correct the sink comment and register the frame parse cap

The review's remaining warning: the _run binding comment claimed the log sink
went 'through the bound send', contradicting the sink's actual direct use of the
bound encode+write primitives. The comment now states that; the settlement note
(en + zh) registers FRAME_PARSE_CAP_BYTES and the 65 MiB-frame regression case.
Pairing re-recorded.

.agents/notes/implemented/bug-fix/2026-07-31-code-runtime-python-settlement-fixes.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write .agents/notes/implemented/bug-fix/2026-07-31-code-runtime-python-settlement-fixes.md
-2026-07-31-code-runtime-python-settlement-fixes.md: 0ecbe509eeb25aa191a66fb96ec645f6709a2953
-2026-07-31-code-runtime-python-settlement-fixes.zh.md: a5da38e684bcfda6ba1e819d5dcf5ad7d63921da
+2026-07-31-code-runtime-python-settlement-fixes.md: 94d5a7b6608f54a6eaa9b1640cf017d16a1c5b8c
+2026-07-31-code-runtime-python-settlement-fixes.zh.md: f542216b7be865fbbbfed15d77a41f5aa8080912

packages/code-runtime/code-runtime-python/py/bootstrap.py

@@ -950,7 +950,8 @@ async def _run(channel: ProtocolChannel) -> None:
     # `_encode_json_plain` (module global) and `self.write_encoded` (class
     # attribute) at call time, so a program rebinding either before the first
     # binding call could turn a legitimate call into an exception. dispatch
-    # writes through these directly, and the log sink through the bound send.
+    # and the log sink both write through these directly (the sink does NOT go
+    # through send_sync, whose body resolves the same names at call time).
     _write_encoded_cls = channel.write_encoded
     _encode_plain_cls = _encode_json_plain
     # 1. Boot handshake.