labcode 0.4.0__tar.gz → 0.6.0__tar.gz

{labcode-0.4.0 → labcode-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.4.0
+Version: 0.6.0
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -21,8 +21,8 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: ofplang-validate<0.3,>=0.2
-Requires-Dist: ofplang-schedule<0.9,>=0.8
-Requires-Dist: ofplang-run<0.8,>=0.7
+Requires-Dist: ofplang-schedule<0.11,>=0.9
+Requires-Dist: ofplang-run<0.10,>=0.8
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"

{labcode-0.4.0 → labcode-0.6.0}/labcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.4.0
+Version: 0.6.0
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -21,8 +21,8 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: ofplang-validate<0.3,>=0.2
-Requires-Dist: ofplang-schedule<0.9,>=0.8
-Requires-Dist: ofplang-run<0.8,>=0.7
+Requires-Dist: ofplang-schedule<0.11,>=0.9
+Requires-Dist: ofplang-run<0.10,>=0.8
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"

{labcode-0.4.0 → labcode-0.6.0}/labcode.egg-info/requires.txt

@@ -1,6 +1,6 @@
 ofplang-validate<0.3,>=0.2
-ofplang-schedule<0.9,>=0.8
-ofplang-run<0.8,>=0.7
+ofplang-schedule<0.11,>=0.9
+ofplang-run<0.10,>=0.8
 
 [dev]
 pytest>=7.0

labcode-0.6.0/labcode.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.6.0",
+  "distance": 0,
+  "node": "g9788ffa864178c0e21165cd62fcd0ddfb48ac2cc",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-09-15"
+}

{labcode-0.4.0 → labcode-0.6.0}/pyproject.toml

@@ -41,10 +41,16 @@ classifiers = [
 # `dispatch_replenishment` seam and the `kind: replenishment` the child harness has to
 # recognise as side-effect only.
 #
-# `ofplang-schedule>=0.8` is required, not merely tested against: `lc run` passes
-# `--max-transport-legs` through to it (schedule SPEC §6.4.1), and a job may leave a
-# running plan (§6.11), which needs the `withdraw` argument and the levels carried
-# forward with it. The `>=0.5` floor it replaces was required because an environment may
+# `ofplang-schedule>=0.9` and `ofplang-run>=0.8` are required together, not merely
+# tested against: the runner now carries the plan itself from one replan to the next
+# instead of rebuilding a status, and the scheduler is what makes that possible -- it
+# derives what a stopped job is still holding rather than being told, takes
+# `carry_levels_to_now` so a departing job's draws are not handed back, and replans a
+# pending refill rather than refusing the document carrying one. Pairing an older
+# scheduler with this runner has every replan refused, and a refused replan stops
+# every job of the run. The `>=0.8` floor it replaces was required because `lc run`
+# passes `--max-transport-legs` through (schedule SPEC §6.4.1) and a job may leave a
+# running plan (§6.11). The `>=0.5` floor before that was required because an environment may
 # declare a route that needs no transporter (`transporter: null`, schedule §4.6/§5.4) and
 # this dialect accepts a `sila2` script on one, but an older scheduler refuses the
 # environment with `wrong_type` before there is a plan to run -- and `ofplang-run>=0.6` is
@@ -55,6 +61,12 @@ classifiers = [
 # workflow acceptance of 0.1.3. CI resolves the siblings from PyPI, so every run of this suite and
 # every real-lab example already happens on it, and run's own floor requires it anyway
 # (an older scheduler reports a running refill free before it is).
+#
+# 🔴 The `<0.11` / `<0.10` bounds are bounds, not floors. schedule 0.10 refuses two jobs
+# binding one boundary spot where it used to warn, and run 0.9 records a backend's
+# refusal as the activity failing instead of letting it escape `run()`. Both change what
+# happens to a document or a run this package hands over, not anything this package
+# calls, so the floors stay where they are and only the bounds move to admit them.
 dependencies = [
 # Upper bounds are deliberate. A sibling's minor version is where a
 # specification revision lands, and a revision may reject documents an earlier one
@@ -64,8 +76,8 @@ dependencies = [
 # bounds cannot protect what is already on PyPI without one, which is why they go
 # in now rather than at the first breakage.
     "ofplang-validate>=0.2,<0.3",
-    "ofplang-schedule>=0.8,<0.9",
-    "ofplang-run>=0.7,<0.8",
+    "ofplang-schedule>=0.9,<0.11",
+    "ofplang-run>=0.8,<0.10",
 ]
 
 [project.urls]

labcode-0.4.0/labcode.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "0.4.0",
-  "distance": 0,
-  "node": "ge84abdb92eead9230494348c19d0e418605aaecb",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-09-11"
-}