Chinesezjc
96597c5ed8
Addresses the review's registration-text accuracy findings: - _run binds _done_with_value into a local (done_with_value_bound) before the program runs, closing the __main__._done_with_value = boom success-rewrite vector; a regression test rebinds it and returns a legitimate value, asserting the success survives. - README (en + zh): the CPU-recheck bullet now states the recheck runs unconditionally after the program returns (a pre-return overrun dies there as a timeout) and the false-success window is only a trap-SIGXCPU program that passes the recheck and overruns during the settlement flush/encode; the encoder-deps residual rationale is replaced with the actual one (bash-equivalent trust, verdict still delivered via the send_done fallback frame) and names the now-bound entry; the t.join() deadlock bullet fixes the subject/object (the main coroutine joins the worker, blocking the pump's main event loop). - The portable-identifier-seam architecture note no longer claims the Python backend does not exist. - Settlement note (en + zh) registers the entry-name binding and the new test. - All pairings re-recorded; corpus-wide verify-translation-pairing passes 1004.
description, kind
| description | kind |
|---|---|
| Package map for the code-execution capability family: what program execution does for you, and which package owns each part. | package-group |
code-runtime/ — code-execution capability family
English | 中文
Summary
The code-runtime/ group provides program execution: a model writes one program that calls host-provided functions as ordinary async calls, and a runtime executes it in isolation and returns only what the program printed and returned. One package defines the shared capability (ctx.codeRuntime), a second executes TypeScript programs in a fresh Node worker thread, and a third owns the wire protocol between a Node host and a CPython subprocess for the Python backend. Every run is independent — no state carries from one program to the next — and failures come back as part of the result, so the caller can see why a program failed and feed that back to the model.
Table of Contents
Packages
These three packages together provide program execution; each README describes what its part does.
| Package | Role | ctx key |
|---|---|---|
code-runtime/ |
Defines what a code runtime does: run one program against host-provided bindings and report what it printed and returned | ctx.codeRuntime |
code-runtime-worker-thread/ |
Executes TypeScript programs, each in a fresh Node worker thread | registers ctx.codeRuntime |
code-runtime-python/ |
Owns the fd-3 wire protocol between a Node host and a CPython subprocess, the Python backend's protocol layer | — |
Related documentation
Start with the subsystem reference for the service contract, then the PTC mode design that consumes this capability and the capability-seam model it follows.
- Code runtime subsystem reference — request/result vocabulary, bindings, and the
ctx.codeRuntimecordis surface. - PTC mode Agent Note — how the tool registry presents
run_codeto the model. - Capability seams — the Service Definition / Service Provider / Consumer split this family follows.
Dev Note
Working context for maintainers — click to expand
None.