lr-lumentest-sdk 0.6.1__tar.gz

lr_lumentest_sdk-0.6.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 LumenRadio AB
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

lr_lumentest_sdk-0.6.1/Makefile

@@ -0,0 +1,120 @@
+VENV := .venv
+PY   := $(VENV)/bin/python
+PIP  := $(VENV)/bin/pip
+
+# Resolve black config from the repo root (one directory up).
+# This avoids duplicating line-length / target-version across the sub-packages.
+ROOT_DIR := $(abspath $(dir $(lastword $(MAKEFILE_LIST)))/..)
+
+# setuptools_scm version, resolved on the host from the installed _version.py.
+# Injected via SETUPTOOLS_SCM_PRETEND_VERSION_FOR_* so the sdist build skips the
+# VCS file-finder (which root=".." would otherwise use to pull in the whole
+# monorepo), and so in-container builds (no git / no repo-root mount) get it too.
+DIST_ENV := SETUPTOOLS_SCM_PRETEND_VERSION_FOR_LR_LUMENTEST_SDK
+SCM_VERSION = $(shell $(PY) -c "import lumentest_station._version as v; print(v.version)" 2>/dev/null)
+
+# Only the sdist and wheel are valid PyPI distributions.
+DIST_FILES := dist/*.whl dist/*.tar.gz
+
+PYPI_REPOSITORY ?= https://upload.pypi.org/legacy/
+TEST_PYPI_REPOSITORY ?= https://test.pypi.org/legacy/
+
+# The PyPI token lives in the releasing developer's shell, exported by hand
+# before running `publish`/`publish-test` — the same arrangement lr-gladiator
+# and lr-qrm use. No CI job holds it, so a release reaches PyPI only when a
+# person runs the target.
+#
+# setuptools_scm derives SCM_VERSION from the `lumentest-*` tag: any commit
+# past the tag carries a `.devN+g<sha>` suffix. PyPI rejects a local (`+…`)
+# segment outright, and a `.dev` upload permanently spends a version number
+# the index can never reuse — so both upload targets refuse anything but a
+# clean tag.
+CHECK_RELEASE_VERSION = case "$(SCM_VERSION)" in *dev*|*+*|"") echo "error: refusing to upload $(SCM_VERSION) — build from a clean 'lumentest-X.Y.Z' tag"; exit 2 ;; esac
+
+# The staging tree this package ships is generated, not authored: each module
+# has exactly one canonical home, under service/src/lumentest_station/. This
+# list is an allowlist — sdk/tests/ asserts that its closure (every
+# lumentest_station.X import reachable from these files) never reaches outside
+# it, so a station-side change that adds a new intra-package import fails the
+# SDK's own test suite instead of silently shipping a broken wheel.
+STATION_SRC := ../service/src/lumentest_station
+SDK_MODULES := __init__.py decorators.py limits.py manifest.py run_tool.py \
+               sequence.py step_executor.py step_main.py test_context.py
+
+SRC_DIR := src/lumentest_station
+
+.DEFAULT_GOAL := install
+
+.PHONY: install dev sync test test-only format dist check publish publish-test shell clean
+
+$(VENV)/bin/activate:
+	python3.12 -m venv $(VENV)
+	$(PIP) install --upgrade pip
+
+# Regenerates the staging tree from scratch every time: a module dropped from
+# SDK_MODULES (or renamed upstream) must disappear from the wheel too, not
+# linger from a previous sync. _version.py is never copied here — setuptools_scm
+# writes it into $(SRC_DIR) itself at build/install time.
+sync:
+	rm -rf $(SRC_DIR)
+	mkdir -p $(SRC_DIR)
+	@for f in $(SDK_MODULES); do \
+		test -f $(STATION_SRC)/$$f || { echo "error: $(STATION_SRC)/$$f not found — sdk/Makefile's SDK_MODULES names a module the station does not have"; exit 2; }; \
+		cp $(STATION_SRC)/$$f $(SRC_DIR)/$$f; \
+	done
+
+install: $(VENV)/bin/activate sync
+	$(PIP) install .
+
+dev: $(VENV)/bin/activate sync
+	$(PIP) install -e ".[dev]"
+
+# `test` is the whole job: sync the venv, then run pytest. `test-only` is the
+# pytest half on its own, for a driver that has already done the `dev` pass and
+# wants to run several sub-trees at once -- the editable installs `dev` performs
+# write in-tree build artefacts, so they must not overlap; pytest runs may.
+test: dev test-only
+
+test-only:
+	$(VENV)/bin/pytest \
+		--junit-xml=test-results.xml \
+		tests/
+
+# src/ is generated from already-formatted upstream sources; formatting it here
+# would edit a tree `sync` throws away on the next run.
+format: dev
+	$(VENV)/bin/black --config $(ROOT_DIR)/pyproject.toml tests/
+
+# Clearing the previous sdist and wheel is what keeps `$(DIST_FILES)` meaning
+# "this build": every artefact accumulates under its own version, and an upload
+# globbing the directory would carry a stale version along with the current one.
+dist: dev
+	rm -f dist/*.whl dist/*.tar.gz
+	$(DIST_ENV)="$(SCM_VERSION)" $(PY) -m build
+
+check: dist
+	$(VENV)/bin/twine check $(DIST_FILES)
+
+# Both upload targets pass credentials through TWINE_USERNAME/TWINE_PASSWORD,
+# which twine reads natively, and silence the upload line with `@`. `-u`/`-p`
+# would put the token in the echoed recipe line and in the upload process's
+# argv, where `ps` can read it — visible in a developer's scrollback and, since
+# this target also runs as a CI job, in a captured job log.
+publish-test: check
+	@$(CHECK_RELEASE_VERSION)
+	@if [ -z "$$TEST_PYPI_TOKEN" ]; then echo "error: TEST_PYPI_TOKEN is required — create one at https://test.pypi.org/manage/account/token/"; exit 2; fi
+	@TWINE_USERNAME=__token__ TWINE_PASSWORD="$$TEST_PYPI_TOKEN" $(VENV)/bin/twine upload --repository-url $(TEST_PYPI_REPOSITORY) $(DIST_FILES)
+
+publish: check
+	@$(CHECK_RELEASE_VERSION)
+	@if [ -z "$$PYPI_TOKEN" ]; then echo "error: PYPI_TOKEN is required — create one at https://pypi.org/manage/account/token/"; exit 2; fi
+	@TWINE_USERNAME=__token__ TWINE_PASSWORD="$$PYPI_TOKEN" $(VENV)/bin/twine upload --repository-url $(PYPI_REPOSITORY) $(DIST_FILES)
+
+shell:
+	@echo "source $(VENV)/bin/activate"
+
+clean:
+	rm -rf $(VENV) dist/ build/ htmlcov/ test-results.xml .coverage $(SRC_DIR)
+	find . -type d -name __pycache__ -exec rm -rf {} + 2>/dev/null; true
+	find . -name "*.pyc" -delete 2>/dev/null; true
+	find . -name "*.egg-info" -type d -exec rm -rf {} + 2>/dev/null; true

lr_lumentest_sdk-0.6.1/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: lr-lumentest-sdk
+Version: 0.6.1
+Summary: Step-authoring SDK for LumenTest test sequences: write and run steps against the same lumentest_station API the station imports, from a standalone .venv with no monorepo checkout.
+Author-email: Jonas Estberger <jonas.estberger@lumenradio.com>
+License-Expression: MIT
+Project-URL: Homepage, https://gitlab.com/lumenradio/production/lumentest
+Project-URL: Changelog, https://gitlab.com/lumenradio/production/lumentest/-/blob/main/CHANGELOG.md
+Keywords: LumenRadio,LumenTest,production test,test station,step SDK
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Classifier: Environment :: Console
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic>=2.8
+Requires-Dist: pyserial>=3.5
+Provides-Extra: dev
+Requires-Dist: build>=1.2.1; extra == "dev"
+Requires-Dist: twine>=6.1; extra == "dev"
+Requires-Dist: pytest>=8.4; extra == "dev"
+Requires-Dist: pytest-cov>=5.0; extra == "dev"
+Requires-Dist: black>=25.9; extra == "dev"
+Dynamic: license-file
+
+# lr-lumentest-sdk
+
+Step-authoring SDK for LumenRadio LumenTest test sequences.
+
+This package is for an embedded developer writing or updating test steps and
+sequences for a LumenTest production station, who wants a `.venv` and an
+editor with working imports, type hints and autocomplete for the step API —
+without checking out or installing the station itself. It ships the exact
+same `lumentest_station` source files the station runs, so a step written and
+tested against this package behaves identically when the station loads it.
+
+## Installation
+
+```bash
+pip install lr-lumentest-sdk
+```
+
+> **This package and `lumentest-station` both provide the `lumentest_station`
+> import name and must never be installed into the same environment.** A
+> station developer already has the real package — install `lr-lumentest-sdk`
+> only in a separate `.venv` dedicated to authoring steps and sequences.
+
+## Public API
+
+```python
+from lumentest_station import (
+    step_options,      # decorator: attaches step metadata (type, timeout, limits section)
+    sequence_options,  # decorator: attaches sequence metadata (name, serial handling)
+    run_tool,          # run an external tool as a supervised subprocess
+    StepFailed,        # raise to fail the step; optionally carrying the ToolResult that failed
+    ToolResult,        # what run_tool() returns: exit_code, stdout, stderr, timed_out
+    Measurement,       # a single limits-checked measurement to report
+    step_main,         # run this step standalone from the command line
+)
+```
+
+## Running a single step
+
+A step module can run itself directly, with no separate harness:
+
+```python
+from lumentest_station import step_options, step_main
+
+
+@step_options("PROGRAMMING", display_name="Flash Firmware")
+def flash_firmware(test):
+    ...
+
+
+if __name__ == "__main__":
+    raise SystemExit(step_main(flash_firmware))
+```
+
+```bash
+python my_step.py --limits limits.toml --manifest artifact-manifest.json
+```
+
+For a step file with no `__main__` guard, use the `lumentest-step` console
+script instead:
+
+```bash
+lumentest-step validate my_step.py
+lumentest-step run my_step.py --limits limits.toml --manifest artifact-manifest.json --env NRF_TOOLS=/opt/nrf --results-dir ./results
+```
+
+`validate` is a static check only — it never imports the file, so it needs no
+hardware and no environment. It enforces the two rules the station's loader
+enforces: exactly one `@step_options`-decorated top-level function, and no
+direct `subprocess` use (steps call `run_tool` instead). `run` performs the
+same check, then imports and executes the step.
+
+Options for `run`, and for `step_main` under a `__main__` guard:
+
+| Option | Purpose |
+|---|---|
+| `--limits PATH` | TOML file of measurement limits; repeatable, later files win. Needed by any step that returns measurements. |
+| `--manifest PATH` | A package directory, or its `artifact-manifest.json`, so `manifest.resolve(...)` works against a real package |
+| `--env NAME=VALUE` | Set an environment variable for the step's run, repeatable. Production steps read station configuration from the environment, so this stands in for the station's `[env]` config. |
+| `--dut`, `--article`, `--revision`, `--station` | The identity fields the step sees on its `test` context |
+| `--timeout SECONDS` | Override the step's own `@step_options(timeout=...)` |
+| `--results-dir DIR` | Where captured `stdout.txt`, `stderr.txt` and `traceback.txt` land |
+
+The exit status is `0` when the step passed, `1` when it failed (an explicit
+`StepFailed`, or an out-of-limit measurement), and `2` on an error — an
+unexpected exception, a timeout, or a file the loader rejects.
+
+A station does far more than run one step: it uploads to QRM, validates serial
+numbers, curates the `PATH` a tool is resolved against, and runs a whole
+sequence in order. None of that is reproduced here. A green standalone run says
+the step's own logic holds, not that the sequence will pass on a station.
+
+## Full authoring guide
+
+For the complete authoring reference — sequence structure, limits files,
+manifests, the step SDK's allowed third-party imports, and the full
+`lumentest-step` command reference — see
+[`doc/step-sdk.md`](https://gitlab.com/lumenradio/production/lumentest/-/blob/main/doc/step-sdk.md)
+in the LumenTest repository.

lr_lumentest_sdk-0.6.1/README.md

@@ -0,0 +1,98 @@
+# lr-lumentest-sdk
+
+Step-authoring SDK for LumenRadio LumenTest test sequences.
+
+This package is for an embedded developer writing or updating test steps and
+sequences for a LumenTest production station, who wants a `.venv` and an
+editor with working imports, type hints and autocomplete for the step API —
+without checking out or installing the station itself. It ships the exact
+same `lumentest_station` source files the station runs, so a step written and
+tested against this package behaves identically when the station loads it.
+
+## Installation
+
+```bash
+pip install lr-lumentest-sdk
+```
+
+> **This package and `lumentest-station` both provide the `lumentest_station`
+> import name and must never be installed into the same environment.** A
+> station developer already has the real package — install `lr-lumentest-sdk`
+> only in a separate `.venv` dedicated to authoring steps and sequences.
+
+## Public API
+
+```python
+from lumentest_station import (
+    step_options,      # decorator: attaches step metadata (type, timeout, limits section)
+    sequence_options,  # decorator: attaches sequence metadata (name, serial handling)
+    run_tool,          # run an external tool as a supervised subprocess
+    StepFailed,        # raise to fail the step; optionally carrying the ToolResult that failed
+    ToolResult,        # what run_tool() returns: exit_code, stdout, stderr, timed_out
+    Measurement,       # a single limits-checked measurement to report
+    step_main,         # run this step standalone from the command line
+)
+```
+
+## Running a single step
+
+A step module can run itself directly, with no separate harness:
+
+```python
+from lumentest_station import step_options, step_main
+
+
+@step_options("PROGRAMMING", display_name="Flash Firmware")
+def flash_firmware(test):
+    ...
+
+
+if __name__ == "__main__":
+    raise SystemExit(step_main(flash_firmware))
+```
+
+```bash
+python my_step.py --limits limits.toml --manifest artifact-manifest.json
+```
+
+For a step file with no `__main__` guard, use the `lumentest-step` console
+script instead:
+
+```bash
+lumentest-step validate my_step.py
+lumentest-step run my_step.py --limits limits.toml --manifest artifact-manifest.json --env NRF_TOOLS=/opt/nrf --results-dir ./results
+```
+
+`validate` is a static check only — it never imports the file, so it needs no
+hardware and no environment. It enforces the two rules the station's loader
+enforces: exactly one `@step_options`-decorated top-level function, and no
+direct `subprocess` use (steps call `run_tool` instead). `run` performs the
+same check, then imports and executes the step.
+
+Options for `run`, and for `step_main` under a `__main__` guard:
+
+| Option | Purpose |
+|---|---|
+| `--limits PATH` | TOML file of measurement limits; repeatable, later files win. Needed by any step that returns measurements. |
+| `--manifest PATH` | A package directory, or its `artifact-manifest.json`, so `manifest.resolve(...)` works against a real package |
+| `--env NAME=VALUE` | Set an environment variable for the step's run, repeatable. Production steps read station configuration from the environment, so this stands in for the station's `[env]` config. |
+| `--dut`, `--article`, `--revision`, `--station` | The identity fields the step sees on its `test` context |
+| `--timeout SECONDS` | Override the step's own `@step_options(timeout=...)` |
+| `--results-dir DIR` | Where captured `stdout.txt`, `stderr.txt` and `traceback.txt` land |
+
+The exit status is `0` when the step passed, `1` when it failed (an explicit
+`StepFailed`, or an out-of-limit measurement), and `2` on an error — an
+unexpected exception, a timeout, or a file the loader rejects.
+
+A station does far more than run one step: it uploads to QRM, validates serial
+numbers, curates the `PATH` a tool is resolved against, and runs a whole
+sequence in order. None of that is reproduced here. A green standalone run says
+the step's own logic holds, not that the sequence will pass on a station.
+
+## Full authoring guide
+
+For the complete authoring reference — sequence structure, limits files,
+manifests, the step SDK's allowed third-party imports, and the full
+`lumentest-step` command reference — see
+[`doc/step-sdk.md`](https://gitlab.com/lumenradio/production/lumentest/-/blob/main/doc/step-sdk.md)
+in the LumenTest repository.

lr_lumentest_sdk-0.6.1/pyproject.toml

@@ -0,0 +1,71 @@
+[build-system]
+requires = ["setuptools>=77", "setuptools_scm>=8", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "lr-lumentest-sdk"
+dynamic = ["version"]
+description = "Step-authoring SDK for LumenTest test sequences: write and run steps against the same lumentest_station API the station imports, from a standalone .venv with no monorepo checkout."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+  { name = "Jonas Estberger", email = "jonas.estberger@lumenradio.com" }
+]
+# pydantic backs the manifest/limits models a step imports transitively.
+# pyserial is the pinned step-SDK library step code is allowed to import (see
+# the "Step SDK" table in instructions.md) — it is a direct dependency here,
+# not just a transitive one, so a developer's venv matches exactly what the
+# station gives a step at run time.
+dependencies = [
+  "pydantic>=2.8",
+  "pyserial>=3.5",
+]
+keywords = ["LumenRadio", "LumenTest", "production test", "test station", "step SDK"]
+classifiers = [
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.12",
+  "Operating System :: OS Independent",
+  "Environment :: Console",
+  "Topic :: Software Development :: Testing",
+]
+
+[project.optional-dependencies]
+dev = [
+  "build>=1.2.1",
+  "twine>=6.1",
+  "pytest>=8.4",
+  "pytest-cov>=5.0",
+  "black>=25.9",
+]
+
+[project.scripts]
+lumentest-step = "lumentest_station.step_main:main"
+
+[project.urls]
+Homepage = "https://gitlab.com/lumenradio/production/lumentest"
+Changelog = "https://gitlab.com/lumenradio/production/lumentest/-/blob/main/CHANGELOG.md"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+include-package-data = true
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+# Single source of truth: the monorepo `lumentest-*` git tag (see service
+# pyproject for the rationale). root=".." points at the repo root so the version
+# resolves. NB: the `dist` make target sets SETUPTOOLS_SCM_PRETEND_VERSION_FOR_*
+# so the sdist build skips the VCS file-finder — otherwise root=".." would pull
+# the whole monorepo into the sdist.
+[tool.setuptools_scm]
+root = ".."
+tag_regex = "^lumentest-(?P<version>[0-9].+)$"
+git_describe_command = ["git", "describe", "--dirty", "--tags", "--long", "--match", "lumentest-*"]
+version_file = "src/lumentest_station/_version.py"
+fallback_version = "0.0.0"
+
+[tool.pytest.ini_options]
+addopts = "-ra"
+testpaths = ["tests"]

lr_lumentest_sdk-0.6.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: lr-lumentest-sdk
+Version: 0.6.1
+Summary: Step-authoring SDK for LumenTest test sequences: write and run steps against the same lumentest_station API the station imports, from a standalone .venv with no monorepo checkout.
+Author-email: Jonas Estberger <jonas.estberger@lumenradio.com>
+License-Expression: MIT
+Project-URL: Homepage, https://gitlab.com/lumenradio/production/lumentest
+Project-URL: Changelog, https://gitlab.com/lumenradio/production/lumentest/-/blob/main/CHANGELOG.md
+Keywords: LumenRadio,LumenTest,production test,test station,step SDK
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Classifier: Environment :: Console
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic>=2.8
+Requires-Dist: pyserial>=3.5
+Provides-Extra: dev
+Requires-Dist: build>=1.2.1; extra == "dev"
+Requires-Dist: twine>=6.1; extra == "dev"
+Requires-Dist: pytest>=8.4; extra == "dev"
+Requires-Dist: pytest-cov>=5.0; extra == "dev"
+Requires-Dist: black>=25.9; extra == "dev"
+Dynamic: license-file
+
+# lr-lumentest-sdk
+
+Step-authoring SDK for LumenRadio LumenTest test sequences.
+
+This package is for an embedded developer writing or updating test steps and
+sequences for a LumenTest production station, who wants a `.venv` and an
+editor with working imports, type hints and autocomplete for the step API —
+without checking out or installing the station itself. It ships the exact
+same `lumentest_station` source files the station runs, so a step written and
+tested against this package behaves identically when the station loads it.
+
+## Installation
+
+```bash
+pip install lr-lumentest-sdk
+```
+
+> **This package and `lumentest-station` both provide the `lumentest_station`
+> import name and must never be installed into the same environment.** A
+> station developer already has the real package — install `lr-lumentest-sdk`
+> only in a separate `.venv` dedicated to authoring steps and sequences.
+
+## Public API
+
+```python
+from lumentest_station import (
+    step_options,      # decorator: attaches step metadata (type, timeout, limits section)
+    sequence_options,  # decorator: attaches sequence metadata (name, serial handling)
+    run_tool,          # run an external tool as a supervised subprocess
+    StepFailed,        # raise to fail the step; optionally carrying the ToolResult that failed
+    ToolResult,        # what run_tool() returns: exit_code, stdout, stderr, timed_out
+    Measurement,       # a single limits-checked measurement to report
+    step_main,         # run this step standalone from the command line
+)
+```
+
+## Running a single step
+
+A step module can run itself directly, with no separate harness:
+
+```python
+from lumentest_station import step_options, step_main
+
+
+@step_options("PROGRAMMING", display_name="Flash Firmware")
+def flash_firmware(test):
+    ...
+
+
+if __name__ == "__main__":
+    raise SystemExit(step_main(flash_firmware))
+```
+
+```bash
+python my_step.py --limits limits.toml --manifest artifact-manifest.json
+```
+
+For a step file with no `__main__` guard, use the `lumentest-step` console
+script instead:
+
+```bash
+lumentest-step validate my_step.py
+lumentest-step run my_step.py --limits limits.toml --manifest artifact-manifest.json --env NRF_TOOLS=/opt/nrf --results-dir ./results
+```
+
+`validate` is a static check only — it never imports the file, so it needs no
+hardware and no environment. It enforces the two rules the station's loader
+enforces: exactly one `@step_options`-decorated top-level function, and no
+direct `subprocess` use (steps call `run_tool` instead). `run` performs the
+same check, then imports and executes the step.
+
+Options for `run`, and for `step_main` under a `__main__` guard:
+
+| Option | Purpose |
+|---|---|
+| `--limits PATH` | TOML file of measurement limits; repeatable, later files win. Needed by any step that returns measurements. |
+| `--manifest PATH` | A package directory, or its `artifact-manifest.json`, so `manifest.resolve(...)` works against a real package |
+| `--env NAME=VALUE` | Set an environment variable for the step's run, repeatable. Production steps read station configuration from the environment, so this stands in for the station's `[env]` config. |
+| `--dut`, `--article`, `--revision`, `--station` | The identity fields the step sees on its `test` context |
+| `--timeout SECONDS` | Override the step's own `@step_options(timeout=...)` |
+| `--results-dir DIR` | Where captured `stdout.txt`, `stderr.txt` and `traceback.txt` land |
+
+The exit status is `0` when the step passed, `1` when it failed (an explicit
+`StepFailed`, or an out-of-limit measurement), and `2` on an error — an
+unexpected exception, a timeout, or a file the loader rejects.
+
+A station does far more than run one step: it uploads to QRM, validates serial
+numbers, curates the `PATH` a tool is resolved against, and runs a whole
+sequence in order. None of that is reproduced here. A green standalone run says
+the step's own logic holds, not that the sequence will pass on a station.
+
+## Full authoring guide
+
+For the complete authoring reference — sequence structure, limits files,
+manifests, the step SDK's allowed third-party imports, and the full
+`lumentest-step` command reference — see
+[`doc/step-sdk.md`](https://gitlab.com/lumenradio/production/lumentest/-/blob/main/doc/step-sdk.md)
+in the LumenTest repository.

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/SOURCES.txt

@@ -0,0 +1,29 @@
+LICENSE
+Makefile
+README.md
+pyproject.toml
+src/lr_lumentest_sdk.egg-info/PKG-INFO
+src/lr_lumentest_sdk.egg-info/SOURCES.txt
+src/lr_lumentest_sdk.egg-info/dependency_links.txt
+src/lr_lumentest_sdk.egg-info/entry_points.txt
+src/lr_lumentest_sdk.egg-info/requires.txt
+src/lr_lumentest_sdk.egg-info/scm_file_list.json
+src/lr_lumentest_sdk.egg-info/scm_version.json
+src/lr_lumentest_sdk.egg-info/top_level.txt
+src/lumentest_station/__init__.py
+src/lumentest_station/_version.py
+src/lumentest_station/decorators.py
+src/lumentest_station/limits.py
+src/lumentest_station/manifest.py
+src/lumentest_station/run_tool.py
+src/lumentest_station/sequence.py
+src/lumentest_station/step_executor.py
+src/lumentest_station/step_main.py
+src/lumentest_station/test_context.py
+tests/_helpers.py
+tests/conftest.py
+tests/unit/test_allowlist_closed.py
+tests/unit/test_no_undeclared_dependency.py
+tests/unit/test_public_surface.py
+tests/unit/test_staging_tree_matches_allowlist.py
+tests/unit/test_sync_matches_station_source.py

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+lumentest-step = lumentest_station.step_main:main

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/requires.txt

@@ -0,0 +1,9 @@
+pydantic>=2.8
+pyserial>=3.5
+
+[dev]
+build>=1.2.1
+twine>=6.1
+pytest>=8.4
+pytest-cov>=5.0
+black>=25.9

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/scm_file_list.json

@@ -0,0 +1,15 @@
+{
+  "files": [
+    "LICENSE",
+    "Makefile",
+    "README.md",
+    "pyproject.toml",
+    "tests/_helpers.py",
+    "tests/conftest.py",
+    "tests/unit/test_allowlist_closed.py",
+    "tests/unit/test_no_undeclared_dependency.py",
+    "tests/unit/test_public_surface.py",
+    "tests/unit/test_staging_tree_matches_allowlist.py",
+    "tests/unit/test_sync_matches_station_source.py"
+  ]
+}

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/scm_version.json

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

lr_lumentest_sdk-0.6.1/src/lr_lumentest_sdk.egg-info/top_level.txt

@@ -0,0 +1 @@
+lumentest_station

lr_lumentest_sdk-0.6.1/src/lumentest_station/__init__.py

@@ -0,0 +1,21 @@
+"""LumenRadio Station — public API surface for step and sequence authors."""
+
+try:
+    from lumentest_station._version import __version__
+except ImportError:  # pragma: no cover - _version.py is generated by setuptools_scm
+    __version__ = "0.0.0+unknown"
+
+from lumentest_station.decorators import step_options, sequence_options
+from lumentest_station.run_tool import run_tool, StepFailed, ToolResult
+from lumentest_station.limits import Measurement
+from lumentest_station.step_main import step_main
+
+__all__ = [
+    "step_options",
+    "sequence_options",
+    "run_tool",
+    "StepFailed",
+    "ToolResult",
+    "Measurement",
+    "step_main",
+]