lockwire 0.2.3__tar.gz → 0.2.4__tar.gz

{lockwire-0.2.3 → lockwire-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lockwire
-Version: 0.2.3
+Version: 0.2.4
 Summary: The physical-assumption contract for robots: checks that a robot's declared parts (power, weight, bus, torque) add up
 Keywords: robotics,urdf,ros,preflight,lockfile,ci,hardware,drone
 Author: Shivansh
@@ -19,7 +19,9 @@ Requires-Dist: pydantic>=2.13.4
 Requires-Dist: rich>=15.0.0
 Requires-Dist: ruamel-yaml>=0.19.1
 Requires-Dist: typer>=0.26.8
-Requires-Dist: mcp>=2.1.1 ; extra == 'mcp'
+Requires-Dist: xacro>=2.1.1
+Requires-Dist: mcp>=2.2.0 ; extra == 'mcp'
+Requires-Dist: pyjwt>=2.15 ; extra == 'mcp'
 Requires-Dist: fastapi>=0.141.1 ; extra == 'serve'
 Requires-Dist: uvicorn>=0.52.4 ; extra == 'serve'
 Requires-Python: >=3.12
@@ -198,9 +200,9 @@ VIOLATION budgets/bud.power.pm02-5v — observed 35.20 W (draw mode: nominal), e
   action: shed load on rail 'rail.pm02-5v' or raise its capacity with provenance
 VIOLATION budgets/bud.power.pm02-5v.7w-mode — observed 17.20 W (draw mode: 7W), expected <= 15.60 W (Δ +1.60 W (+10%))
   … (same rail, Jetson in its 7 W mode: the radio's transmit peak still tips it over)
-not scored devices/dev.camera.oak-d-lite/physical/mass — observed mass not declared, expected a positive mass with units
+not scored budgets/bud.mass.payload — observed mass unknown for dev.companion.jetson-orin-nano, dev.camera.oak-d-lite, dev.magnetometer.ist8310; total not scored, expected every device and link in this budget to declare a mass
   … (more not-scored lines: things the lockfile does not declare yet, listed, never hidden)
-scored 10: 8 add up, 2 do not · 9 not scored
+scored 9: 7 add up, 2 do not · 10 not scored
 
 NO-GO — 2 violation(s), 0 warning(s)
 $ echo $?
@@ -217,7 +219,7 @@ integration of published parts, and the two vendors' own numbers still do not ad
 Nobody printed "this build is broken". Nobody printed "5 A" either: that is 25 W / 5 V, a
 quotient of figures published on different pages. The records disagree with each other, and
 you find out before you apply power. Give the Jetson its own regulator
-(`tests/fixtures/x500/contract_corrected.yaml`) and the same check passes.
+(`tests/fixtures/x500/contract_corrected.yaml`) and the same check passes: `GO — records agree (10 scored); 10 check(s) not scored`.
 
 ## Your own robot
 
@@ -241,7 +243,9 @@ Any field you hand-edited (including `robot.name`) is silently overwritten back
 | `start` | the contract was written (or an existing one kept); no page is written | the URDF/SDF could not be parsed, or the contract could not be read or written | — | — |
 
 `NOT SCORED` (exit 3) means no comparison had both operands: it is not a pass and not a failure.
+
 The `scored N: …` line above the verdict is where a script should look.
+`lockwire check --strict` makes a `GO with notes` run exit 1 (the `NO-GO` code); the table does not change.
 
 ## In CI
 
@@ -252,7 +256,7 @@ The `scored N: …` line above the verdict is where a script should look.
     contract: lockwire.yaml
 ```
 
-Inputs: `contract` (default `lockwire.yaml`), `version` (pin a PyPI release; default installs the action's own code), `python-version` (default 3.12).
+Inputs: `contract` (default `lockwire.yaml`), `version` (pin a PyPI release; default installs the action's own code), `strict` (default `false`; `true` passes `--strict`), `python-version` (default 3.12).
 Or just `pipx install lockwire && lockwire check lockwire.yaml`.
 
 ## Pre-commit
@@ -260,7 +264,7 @@ Or just `pipx install lockwire && lockwire check lockwire.yaml`.
 ```yaml
 repos:
   - repo: https://github.com/Shivansh2703/lockwire
-    rev: v0.2.0
+    rev: v0.2.3
     hooks:
       - id: lockwire-check
 ```

{lockwire-0.2.3 → lockwire-0.2.4}/README.md

@@ -166,9 +166,9 @@ VIOLATION budgets/bud.power.pm02-5v — observed 35.20 W (draw mode: nominal), e
   action: shed load on rail 'rail.pm02-5v' or raise its capacity with provenance
 VIOLATION budgets/bud.power.pm02-5v.7w-mode — observed 17.20 W (draw mode: 7W), expected <= 15.60 W (Δ +1.60 W (+10%))
   … (same rail, Jetson in its 7 W mode: the radio's transmit peak still tips it over)
-not scored devices/dev.camera.oak-d-lite/physical/mass — observed mass not declared, expected a positive mass with units
+not scored budgets/bud.mass.payload — observed mass unknown for dev.companion.jetson-orin-nano, dev.camera.oak-d-lite, dev.magnetometer.ist8310; total not scored, expected every device and link in this budget to declare a mass
   … (more not-scored lines: things the lockfile does not declare yet, listed, never hidden)
-scored 10: 8 add up, 2 do not · 9 not scored
+scored 9: 7 add up, 2 do not · 10 not scored
 
 NO-GO — 2 violation(s), 0 warning(s)
 $ echo $?
@@ -185,7 +185,7 @@ integration of published parts, and the two vendors' own numbers still do not ad
 Nobody printed "this build is broken". Nobody printed "5 A" either: that is 25 W / 5 V, a
 quotient of figures published on different pages. The records disagree with each other, and
 you find out before you apply power. Give the Jetson its own regulator
-(`tests/fixtures/x500/contract_corrected.yaml`) and the same check passes.
+(`tests/fixtures/x500/contract_corrected.yaml`) and the same check passes: `GO — records agree (10 scored); 10 check(s) not scored`.
 
 ## Your own robot
 
@@ -209,7 +209,9 @@ Any field you hand-edited (including `robot.name`) is silently overwritten back
 | `start` | the contract was written (or an existing one kept); no page is written | the URDF/SDF could not be parsed, or the contract could not be read or written | — | — |
 
 `NOT SCORED` (exit 3) means no comparison had both operands: it is not a pass and not a failure.
+
 The `scored N: …` line above the verdict is where a script should look.
+`lockwire check --strict` makes a `GO with notes` run exit 1 (the `NO-GO` code); the table does not change.
 
 ## In CI
 
@@ -220,7 +222,7 @@ The `scored N: …` line above the verdict is where a script should look.
     contract: lockwire.yaml
 ```
 
-Inputs: `contract` (default `lockwire.yaml`), `version` (pin a PyPI release; default installs the action's own code), `python-version` (default 3.12).
+Inputs: `contract` (default `lockwire.yaml`), `version` (pin a PyPI release; default installs the action's own code), `strict` (default `false`; `true` passes `--strict`), `python-version` (default 3.12).
 Or just `pipx install lockwire && lockwire check lockwire.yaml`.
 
 ## Pre-commit
@@ -228,7 +230,7 @@ Or just `pipx install lockwire && lockwire check lockwire.yaml`.
 ```yaml
 repos:
   - repo: https://github.com/Shivansh2703/lockwire
-    rev: v0.2.0
+    rev: v0.2.3
     hooks:
       - id: lockwire-check
 ```

{lockwire-0.2.3 → lockwire-0.2.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "lockwire"
-version = "0.2.3"
+version = "0.2.4"
 description = "The physical-assumption contract for robots: checks that a robot's declared parts (power, weight, bus, torque) add up"
 readme = "README.md"
 authors = [
@@ -26,13 +26,15 @@ dependencies = [
     "rich>=15.0.0",
     "ruamel-yaml>=0.19.1",
     "typer>=0.26.8",
+    "xacro>=2.1.1",
 ]
 
 [project.optional-dependencies]
 # Serving lockwire over MCP to an agent. Optional for the same reason as `ros2bag`:
 # a plain install must stay lean, and the SDK is only needed by `lockwire mcp`.
 mcp = [
-    "mcp>=2.1.1",
+    "mcp>=2.2.0",
+    "pyjwt>=2.15",  # direct floor: a fresh lock must not resolve below the fixed release
 ]
 # The Electron app's sidecar: `lockwire serve` over local HTTP. Optional for the
 # same reason as `desktop`/`ros2bag`/`mcp` — a plain CLI install stays lean; only the
@@ -59,7 +61,7 @@ build-backend = "uv_build"
 
 [dependency-groups]
 dev = [
-    "mcp>=2.1.1",
+    "mcp>=2.2.0",
     # tests/test_serve.py needs the sidecar (`lockwire serve`) importable and
     # runnable as a subprocess. Same reasoning as `mcp`/`mcap` above: CI's
     # `test` job runs a plain `uv sync --dev`, so without these here that

{lockwire-0.2.3 → lockwire-0.2.4}/src/lockwire/__init__.py

@@ -1,6 +1,6 @@
 """Lockwire — the physical-assumption contract for robots, enforced in CI and at preflight."""
 
-__version__ = "0.2.3"
+__version__ = "0.2.4"
 
 
 def main() -> None:

{lockwire-0.2.3 → lockwire-0.2.4}/src/lockwire/api.py

@@ -105,6 +105,24 @@ def start(
     return start_contract(urdf, overwrite=overwrite, expected_revision=expected_revision)
 
 
+def from_parts(
+    text: str, *, out: Path | str | None = None, catalog: Path | str | None = None
+) -> dict[str, Any]:
+    """Match a pasted parts list to the catalog; with ``out``, also write a draft lockfile.
+
+    Information, not a gate: a mismatch is listed, never refused. ``parts_list.match_parts``.
+    """
+    from lockwire.parts_list import match_parts, write_draft
+
+    if not isinstance(text, str):  # same plain ValueError the neighbouring functions raise
+        raise ValueError("from_parts needs the parts list as text")
+    document = match_parts(text, catalog)
+    if out is not None and not Path(out).exists():
+        write_draft(document, Path(out), catalog)
+        document["written"] = str(out)
+    return document
+
+
 def api_schema(out: Path | str) -> None:
     """Write the payload union's JSON schema — ``api_payload.export_openapi``.
 
@@ -249,6 +267,7 @@ __all__ = [
     "FUNCTIONS",
     "add",
     "api_schema",
+    "from_parts",
     "api_types",
     "blame",
     "what_if",
@@ -262,6 +281,7 @@ __all__ = [
     "mount_shape",
     "move",
     "log",
+    "place",
     "plan",
     "reparent",
     "review",