lucen-cli 0.1.0__tar.gz

lucen_cli-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

lucen_cli-0.1.0/PKG-INFO

@@ -0,0 +1,113 @@
+Metadata-Version: 2.4
+Name: lucen-cli
+Version: 0.1.0
+Summary: MouseMouse CLI (`lucen`): push robot data, train and sim-test policies, hand them to a robot through a consent gate
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Dist: typer>=0.20
+Requires-Dist: rich>=14.0
+Requires-Dist: httpx>=0.28
+Requires-Dist: lucen-sdk>=0.1.0,<0.2
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: huggingface-hub>=1.0,<2
+Requires-Dist: mujoco==3.12.0 ; extra == 'rl'
+Requires-Dist: onnxruntime==1.30.0 ; extra == 'rl'
+Requires-Dist: numpy>=2.0,<3 ; extra == 'rl'
+Requires-Dist: defusedxml>=0.7 ; extra == 'rl'
+Requires-Dist: mujoco==3.12.0 ; extra == 'rollout'
+Requires-Dist: onnxruntime==1.30.0 ; extra == 'rollout'
+Requires-Dist: numpy>=2.0,<3 ; extra == 'rollout'
+Requires-Dist: defusedxml>=0.7 ; extra == 'rollout'
+Requires-Dist: onnxruntime==1.30.0 ; extra == 'serve'
+Requires-Dist: numpy>=2.0,<3 ; extra == 'serve'
+Requires-Dist: websockets>=14,<16 ; extra == 'serve'
+Requires-Dist: msgpack>=1.0 ; extra == 'serve'
+Requires-Dist: pyjwt[crypto]>=2.10 ; extra == 'serve'
+Requires-Dist: lerobot[smolvla,peft,dataset]>=0.4,<0.7 ; extra == 'vla'
+Requires-Python: >=3.12
+Project-URL: Homepage, https://mousemouse.ai
+Project-URL: Documentation, https://mousemouse.ai/docs/from-a-terminal
+Project-URL: Repository, https://github.com/ICE-CUBA/lucen-hub
+Provides-Extra: rl
+Provides-Extra: rollout
+Provides-Extra: serve
+Provides-Extra: vla
+Description-Content-Type: text/markdown
+
+# `lucen-cli` — the MouseMouse command line
+
+[MouseMouse](https://mousemouse.ai) is a hub for robots: datasets, models and
+robot descriptions with the provenance between them, training and sim tests in
+the cloud or on your own machine, hosted inference for the skill layer, and a
+consent gate — a person approves before a policy reaches a robot. This package
+is its command line, `lucen`, and its Python API, `from lucen import Hub`.
+
+The distribution is **`lucen-cli`**; the command is **`lucen`**. The PyPI
+project named `lucen` is an unrelated library.
+[`mousemouse`](https://pypi.org/project/mousemouse/) is the same CLI under the
+product's name.
+
+## Install
+
+```bash
+uv tool install lucen-cli        # or: pipx install lucen-cli
+lucen version
+```
+
+Extras bring the engines some commands need; everything else stays a few MB:
+
+| Install | What it adds | Used by |
+|---|---|---|
+| `uv tool install "lucen-cli[rollout]"` | MuJoCo 3.12.0, ONNX Runtime | `lucen rollout` (sim tests), `lucen robot init\|validate\|publish` |
+| `uv tool install "lucen-cli[rl]"` | the same wheels | `lucen worker run` with the built-in `ppo_mujoco` trainer |
+| `uv tool install "lucen-cli[serve]"` | ONNX Runtime, websockets, msgpack | `lucen serve` (a hosted-endpoint server on your GPU box) |
+| `uv tool install "lucen-cli[vla]"` | LeRobot, torch, PEFT | the `smolvla_lora` template |
+
+A MouseMouse hub also serves its own copy of these wheels, built from the hub's
+own commit: `curl -fsSL <hub API>/install.sh | sh -s -- cli` installs from
+there and points the CLI at that hub.
+
+## First steps
+
+```bash
+lucen auth login                 # asks for an API key; stores it in ~/.config/lucen/credentials (0600)
+lucen quickstart --robot lucen/laika
+lucen pull lucen/laika-demo ./laika-demo
+lucen push you/my-dataset ./my-dataset --kind dataset --public
+lucen train -f recipe.yaml --follow
+lucen rollout you/my-policy --robot lucen/laika --battery smoke --local
+```
+
+`lucen --help` is grouped by task (get started, robots, data and models, train
+and test, run on a robot). The key is read from `LUCEN_API_KEY` or the
+credentials file, never from a flag; the hub from `LUCEN_API_URL` or the same
+file. Every command has `--json`; stdout is the answer, stderr the progress.
+
+## From Python
+
+```python
+from lucen import Hub
+
+hub = Hub()  # LUCEN_API_URL / LUCEN_API_KEY, else the credentials file
+hub.pull("lucen/laika", "./laika")  # every sha256 verified
+run = hub.runs.create({"template": "ppo_mujoco", "robot": "lucen/laika"}, follow=True)
+```
+
+The same credentials rules, push/pull/follow code and refusal sentences as the
+commands, as records and exceptions instead of lines and exit codes.
+
+## Docs
+
+- [Work from a terminal](https://mousemouse.ai/docs/from-a-terminal)
+- [Train on your machine](https://mousemouse.ai/docs/train-on-your-machine)
+- [Add your robot](https://mousemouse.ai/docs/add-your-robot)
+- [The Python API](https://mousemouse.ai/docs/python)
+- [API reference](https://mousemouse.ai/docs/api) — the CLI is a thin surface
+  over the hub's REST API, through the generated client
+  [`lucen-sdk`](https://pypi.org/project/lucen-sdk/)
+
+The robot side of the consent gate is
+[`lucen-device`](https://pypi.org/project/lucen-device/); the hub's tools for an
+AI agent are [`lucen-mcp`](https://pypi.org/project/lucen-mcp/).
+
+Apache-2.0. © 2026 Lucen Robotics.

lucen_cli-0.1.0/README.md

@@ -0,0 +1,77 @@
+# `lucen-cli` — the MouseMouse command line
+
+[MouseMouse](https://mousemouse.ai) is a hub for robots: datasets, models and
+robot descriptions with the provenance between them, training and sim tests in
+the cloud or on your own machine, hosted inference for the skill layer, and a
+consent gate — a person approves before a policy reaches a robot. This package
+is its command line, `lucen`, and its Python API, `from lucen import Hub`.
+
+The distribution is **`lucen-cli`**; the command is **`lucen`**. The PyPI
+project named `lucen` is an unrelated library.
+[`mousemouse`](https://pypi.org/project/mousemouse/) is the same CLI under the
+product's name.
+
+## Install
+
+```bash
+uv tool install lucen-cli        # or: pipx install lucen-cli
+lucen version
+```
+
+Extras bring the engines some commands need; everything else stays a few MB:
+
+| Install | What it adds | Used by |
+|---|---|---|
+| `uv tool install "lucen-cli[rollout]"` | MuJoCo 3.12.0, ONNX Runtime | `lucen rollout` (sim tests), `lucen robot init\|validate\|publish` |
+| `uv tool install "lucen-cli[rl]"` | the same wheels | `lucen worker run` with the built-in `ppo_mujoco` trainer |
+| `uv tool install "lucen-cli[serve]"` | ONNX Runtime, websockets, msgpack | `lucen serve` (a hosted-endpoint server on your GPU box) |
+| `uv tool install "lucen-cli[vla]"` | LeRobot, torch, PEFT | the `smolvla_lora` template |
+
+A MouseMouse hub also serves its own copy of these wheels, built from the hub's
+own commit: `curl -fsSL <hub API>/install.sh | sh -s -- cli` installs from
+there and points the CLI at that hub.
+
+## First steps
+
+```bash
+lucen auth login                 # asks for an API key; stores it in ~/.config/lucen/credentials (0600)
+lucen quickstart --robot lucen/laika
+lucen pull lucen/laika-demo ./laika-demo
+lucen push you/my-dataset ./my-dataset --kind dataset --public
+lucen train -f recipe.yaml --follow
+lucen rollout you/my-policy --robot lucen/laika --battery smoke --local
+```
+
+`lucen --help` is grouped by task (get started, robots, data and models, train
+and test, run on a robot). The key is read from `LUCEN_API_KEY` or the
+credentials file, never from a flag; the hub from `LUCEN_API_URL` or the same
+file. Every command has `--json`; stdout is the answer, stderr the progress.
+
+## From Python
+
+```python
+from lucen import Hub
+
+hub = Hub()  # LUCEN_API_URL / LUCEN_API_KEY, else the credentials file
+hub.pull("lucen/laika", "./laika")  # every sha256 verified
+run = hub.runs.create({"template": "ppo_mujoco", "robot": "lucen/laika"}, follow=True)
+```
+
+The same credentials rules, push/pull/follow code and refusal sentences as the
+commands, as records and exceptions instead of lines and exit codes.
+
+## Docs
+
+- [Work from a terminal](https://mousemouse.ai/docs/from-a-terminal)
+- [Train on your machine](https://mousemouse.ai/docs/train-on-your-machine)
+- [Add your robot](https://mousemouse.ai/docs/add-your-robot)
+- [The Python API](https://mousemouse.ai/docs/python)
+- [API reference](https://mousemouse.ai/docs/api) — the CLI is a thin surface
+  over the hub's REST API, through the generated client
+  [`lucen-sdk`](https://pypi.org/project/lucen-sdk/)
+
+The robot side of the consent gate is
+[`lucen-device`](https://pypi.org/project/lucen-device/); the hub's tools for an
+AI agent are [`lucen-mcp`](https://pypi.org/project/lucen-mcp/).
+
+Apache-2.0. © 2026 Lucen Robotics.

lucen_cli-0.1.0/pyproject.toml

@@ -0,0 +1,116 @@
+[project]
+name = "lucen-cli"
+version = "0.1.0"
+description = "MouseMouse CLI (`lucen`): push robot data, train and sim-test policies, hand them to a robot through a consent gate"
+# R1: `readme`, `license`, `license-files` and `[project.urls]` are what PyPI
+# renders; the LICENSE beside this file is Apache-2.0 verbatim (docs/DECISIONS.md "R1").
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.12"
+dependencies = [
+    "typer>=0.20",
+    "rich>=14.0",
+    # Presigned blob transfers go straight to R2 and are not an SDK concern,
+    # so the CLI streams those with httpx itself (same httpx the SDK uses).
+    "httpx>=0.28",
+    # R1: a RANGE, not a bare name. `uv build` copies this line into the wheel's
+    # Requires-Dist, where `[tool.uv.sources]` below does not reach, and PyPI has
+    # to resolve it. The generated client is 0.x, so a minor bump is its breaking
+    # signal: the CLI follows the SDK within one minor.
+    "lucen-sdk>=0.1.0,<0.2",
+    # M7-RL: `lucen runs create -f recipe.yaml`. The stub template stays stdlib
+    # only and emits its own YAML; only the recipe *reader* needs a parser.
+    "pyyaml>=6.0",
+    # H1: `lucen datasets import hf://…` reads a LeRobot dataset off the Hugging
+    # Face Hub with the Hub's own client (`hf_hub_download` for meta/info.json,
+    # `snapshot_download` for the files, resumable, HF_TOKEN / HF_HOME honoured).
+    # Pure Python plus `hf-xet` (the Hub's transfer accelerator, a small native
+    # wheel) — no numpy, no torch; the lock stays on the version the `vla` extra
+    # already resolved. Imported lazily, so `lucen --help` does not pay for it.
+    "huggingface_hub>=1.0,<2",
+]
+
+[project.optional-dependencies]
+# M8: `lucen rollout` runs a policy in MuJoCo on this machine. The engine is an
+# extra so the plain CLI install (push/pull/auth) stays a few MB: MuJoCo and
+# onnxruntime are native wheels and nothing else in the CLI needs them.
+#   uv tool install --from "./packages/cli[rollout]" --with ./packages/sdk/py lucen-cli
+# Pinned: `mujoco` is the same 3.12.0 the browser Sim tab vendors (M9), so a
+# model that compiles in one compiles in the other.
+rollout = [
+    "mujoco==3.12.0",
+    "onnxruntime==1.30.0",
+    "numpy>=2.0,<3",
+    # The MJCF is user-uploaded XML: parsed with defusedxml and nothing else,
+    # on every surface that parses it in Python (docs/API.md, "Robot model").
+    "defusedxml>=0.7",
+]
+# M17b: `ppo_mujoco`, the built-in RL trainer — numpy PPO over MuJoCo envs.
+# The same pins as `rollout`, on purpose: the trainer and the sim gate compile
+# ONE plant (`lucen_cli.rollout.plant`), so an install that can train can gate
+# what it trained. It is a separate name because "can train" and "can gate" are
+# different promises that happen to need the same wheels today. No torch:
+# docs/DECISIONS.md, "M17b". onnxruntime is how the trainer re-runs its own
+# export against the trained policy before publishing it.
+#   uv tool install --from "./packages/cli[rl]" --with ./packages/sdk/py lucen-cli
+rl = [
+    "mujoco==3.12.0",
+    "onnxruntime==1.30.0",
+    "numpy>=2.0,<3",
+    "defusedxml>=0.7",
+]
+# M7-RL ③: `smolvla_lora` wraps LeRobot's own trainer (`lerobot-train`) —
+# it never reimplements SmolVLA. LeRobot pulls torch, transformers and the
+# SmolVLM weights' loader, which is why this is an extra and why the template
+# itself refuses to run without it, naming this install line:
+#   uv tool install --from "./packages/cli[vla]" --with ./packages/sdk/py lucen-cli
+# `peft` is the LoRA half (`--peft.method_type=LORA`, lerobot[peft]);
+# `dataset` is the HF `datasets` package `lerobot-train` refuses to start
+# without (found by the M7-RL ③ smoke on lerobot 0.6.1).
+vla = [
+    "lerobot[smolvla,peft,dataset]>=0.4,<0.7",
+]
+
+# M15: `lucen serve` — a self-hosted inference endpoint speaking openpi's
+# policy-server protocol (msgpack + numpy over a websocket). An extra for the
+# same reason `rollout` is: onnxruntime is a native wheel a laptop that only
+# pushes and pulls has no use for. The GPU box installs:
+#   uv tool install --from "./packages/cli[serve]" --with ./packages/sdk/py lucen-cli
+# `websockets` >= 14 for the asyncio server API; `msgpack` is what openpi uses.
+serve = [
+    "onnxruntime==1.30.0",
+    "numpy>=2.0,<3",
+    "websockets>=14,<16",
+    "msgpack>=1.0",
+    # M17e found this missing: `lucen_cli.serve.session` verifies session tokens
+    # (EdDSA) with PyJWT, which the workspace venv has through apps/api — so every
+    # test passed while a standalone `lucen-cli[serve]` install died at
+    # `import jwt` before it could claim anything. Same pin as the API and the driver.
+    "pyjwt[crypto]>=2.10",
+]
+
+[project.scripts]
+lucen = "lucen_cli.main:app"
+
+[project.urls]
+Homepage = "https://mousemouse.ai"
+Documentation = "https://mousemouse.ai/docs/from-a-terminal"
+Repository = "https://github.com/ICE-CUBA/lucen-hub"
+
+[build-system]
+requires = ["uv_build>=0.9.0,<0.10.0"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-name = ["lucen_cli", "lucen"]
+
+[tool.uv]
+# See root pyproject.toml: conda site.py breaks underscore .pth files.
+python-preference = "only-managed"
+
+[tool.uv.sources]
+# In this checkout the generated client is the workspace member (packages/sdk/py);
+# on PyPI it is `lucen-sdk` within the range above (R1). Sources never reach a
+# built wheel, which is why the range has to be in `dependencies`.
+lucen-sdk = { workspace = true }

lucen_cli-0.1.0/src/lucen/__init__.py

@@ -0,0 +1,72 @@
+"""`from lucen import Hub` — MouseMouse from a Python script.
+
+    from lucen import Hub
+
+    hub = Hub()                  # LUCEN_API_URL / LUCEN_API_KEY, else ~/.config/lucen/credentials
+    hub.pull("lucen/laika", "./laika")               # every sha256 verified
+    hub.push("./my-dataset", "you/my-dataset", kind="dataset", public=True)
+    run = hub.runs.create({"template": "ppo_mujoco", "robot": "lucen/laika"}, follow=True)
+    gate = hub.rollouts.create(run.output_model_repo, "lucen/laika", battery="smoke", local=True)
+    print(gate.scorecard)
+
+A thin, typed surface over the `lucen` CLI's own engine (P5): the same
+credentials rules, the same push/pull/follow code, the same sentence for
+every refusal — as records and exceptions instead of lines and exit codes.
+It ships inside the `lucen-cli` distribution: installing `lucen-cli` (from
+the hub's own index or a checkout) is all it takes.
+"""
+
+from __future__ import annotations
+
+from lucen.errors import Conflict, Forbidden, HubError, HubUnreachable, NotFound, NotSignedIn
+from lucen.hub import Hub
+from lucen.progress import ProgressEvent
+from lucen.results import (
+    Cell,
+    Episode,
+    Gate,
+    LogEvent,
+    Me,
+    Member,
+    Org,
+    PullResult,
+    PushResult,
+    Repo,
+    RobotDraft,
+    RobotPublishResult,
+    RobotReport,
+    Rollout,
+    Run,
+    RunEstimate,
+    RunRecommendation,
+)
+from lucen_cli import __version__ as __version__
+
+__all__ = [
+    "Cell",
+    "Conflict",
+    "Episode",
+    "Forbidden",
+    "Gate",
+    "Hub",
+    "HubError",
+    "HubUnreachable",
+    "LogEvent",
+    "Me",
+    "Member",
+    "NotFound",
+    "NotSignedIn",
+    "Org",
+    "ProgressEvent",
+    "PullResult",
+    "PushResult",
+    "Repo",
+    "RobotDraft",
+    "RobotPublishResult",
+    "RobotReport",
+    "Rollout",
+    "Run",
+    "RunEstimate",
+    "RunRecommendation",
+    "__version__",
+]