ph-runtime-guest 0.1.0__tar.gz → 0.2.0__tar.gz

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ph-runtime-guest
-Version: 0.1.0
+Version: 0.2.0
 Summary: The guest half of pH's code runtime: the fd-3 protocol, the run loop, and the binding proxies a cell awaits.
 Project-URL: Homepage, https://github.com/chastabor/pH
 Project-URL: Repository, https://github.com/chastabor/pH
@@ -130,7 +130,7 @@ The host's orphan journal is the backstop for all three.
 
 Nothing here is configured directly. Every knob belongs to `ph-rlm`'s
 `code-runtime-python` row, which spawns this package and sends the `boot` frame
-that parameterises it — and the **host owns every default**, because there are
+that parameterizes it — and the **host owns every default**, because there are
 two definitions of the protocol across the two sides and exactly one owner of
 each value. `boot` carries every limit as a required field, so a guest has
 nothing to guess and a changed default cannot mean two things at once.

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/README.md

@@ -104,7 +104,7 @@ The host's orphan journal is the backstop for all three.
 
 Nothing here is configured directly. Every knob belongs to `ph-rlm`'s
 `code-runtime-python` row, which spawns this package and sends the `boot` frame
-that parameterises it — and the **host owns every default**, because there are
+that parameterizes it — and the **host owns every default**, because there are
 two definitions of the protocol across the two sides and exactly one owner of
 each value. `boot` carries every limit as a required field, so a guest has
 nothing to guess and a changed default cannot mean two things at once.

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ph-runtime-guest"
-version = "0.1.0"
+version = "0.2.0"
 description = "The guest half of pH's code runtime: the fd-3 protocol, the run loop, and the binding proxies a cell awaits."
 readme = "README.md"
 requires-python = ">=3.12"

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/src/ph_runtime/cell.py

@@ -60,7 +60,7 @@ MAGIC_HINT = (
 The magic was the bypass — one shell command per cell that no `tools/pre-execute`
 listener, no approval and no sandbox `confine()` ever saw. Removing the
 mechanism closes the hole, so the error explains the governed route rather than
-apologising for a missing feature.
+apologizing for a missing feature.
 """
 
 

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/src/ph_runtime/protocol.py

@@ -1,12 +1,23 @@
 """The fd-3 frame vocabulary, guest side.
 
-**This module is written twice on purpose.** Its twin is
-`ph_rlm.kernel.protocol`, and neither imports the other: the guest runs in
-`$PH_CACHE/runtime-venv` with almost nothing installed, and making it import the
-host package would put the harness inside the process boundary that exists to keep
-the harness out. What keeps the two in step is `test_protocol_mirror.py`, which
-compares `PROTOCOL_VERSION`, every frame's required and optional field set, and
-the truncation marker byte for byte (D7, D4).
+**This module is written twice on purpose — but not all of it, and the
+asymmetry is the point.** Its twin is `ph_rlm.kernel.protocol`.
+
+The four constants below are declared *here* and **imported** by the host. That
+direction is the only one available: the guest runs in `$PH_CACHE/runtime-venv`
+with almost nothing installed, and making it import the host package would put
+the harness inside the process boundary that exists to keep the harness out. The
+host is under no such restriction — it already depends on this package — so for
+anything that is plain data with no typing to lose, one declaration beats two
+held equal by a test.
+
+Everything else is genuinely twinned, and `test_protocol_mirror.py` is what keeps
+it honest (D7, D4). Two things, for two different reasons: every frame's required
+and optional field set, because the host *derives* its own from `TypedDict`s for
+mypy and a `TypedDict` cannot be derived from a runtime table; and the truncation
+marker byte for byte, because the host re-exports ph-core's copy and this side may
+not import ph-core at all — two implementations, which is the one thing a shared
+declaration could never have reconciled.
 
 **`FRAME_FIELDS` is the *only* declaration of the vocabulary on this side** — a
 second one that no test compares is a copy that drifts, and one already had.
@@ -62,7 +73,14 @@ is dropped and a missing one takes its default.
 
 **Not a cache key**, though `venv._marker` digests it and a bump does force a
 warm guest venv to rebuild. Reaching for it to ship an edit is how a number that
-means "compatibility" ends up meaning "some byte changed"."""
+means "compatibility" ends up meaning "some byte changed".
+
+**Sharing this declaration with the host does not make the two agree at
+runtime**, and nothing about the import should be read as if it did: host and
+guest import from *different* venvs, so they are two installations that can hold
+different versions. What covers that is unchanged and lives elsewhere —
+`kernel/venv.py`'s staleness marker rebuilds a venv whose protocol or guest
+version moved, and `boot-ack` refuses a pairing that still disagrees."""
 
 PROTOCOL_FD: Final = 3
 """Where the channel is by default. fd 0/1/2 stay the program's own, so a cell's

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/src/ph_runtime/runner.py

@@ -324,7 +324,7 @@ class Runner:
                 cell = self.globals.pop(CELL_FUNCTION)
                 value = await cell()
         except asyncio.CancelledError:
-            error = {"kind": "aborted", "message": "the run was cancelled"}
+            error = {"kind": "aborted", "message": "the run was canceled"}
         except KeyboardInterrupt:
             error = {"kind": "aborted", "message": "the run was interrupted"}
         except CpuBudgetExceeded as exceeded:

{ph_runtime_guest-0.1.0 → ph_runtime_guest-0.2.0}/tests/test_snapshot_paths.py

@@ -2,7 +2,7 @@
 
 `NamespaceSnapshotter.changed` is called after every cell, and what it emits is
 the only account the host gets of a variable's fate. Two of its branches are
-about *not* saying things, which is exactly the kind of behaviour a test has to
+about *not* saying things, which is exactly the kind of behavior a test has to
 pin because nothing downstream fails when it breaks:
 
 * a variable that cannot be pickled is reported once and then stays quiet, so a