plesty-bench 0.2.0__tar.gz

plesty_bench-0.2.0/.gitignore

@@ -0,0 +1,71 @@
+# Custom
+.deprecated/
+logs/
+runs/
+
+# Field test and check reports. The JSON documents are the published
+# artifacts — hub.plesty.net and manager.plesty.net read them, so they are
+# committed. The markdown and JSONL forms are for whoever ran the test: they
+# carry the host name, the instrument address, its serial and the lab's file
+# paths, and a hub repository is world-readable.
+# An interrupted `plesty init field-test` leaves its answers here.
+.plesty-field-test.partial.json
+
+reports/**/*.md
+reports/**/*.jsonl
+reports/*.md
+reports/*.jsonl
+
+# Auto-generated device reference pages (regenerated by `plesty docs`)
+docs/_generated/
+
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions and shared libraries
+*.so
+*.pyd
+*.dll
+
+# Packaging and build artifacts
+build/
+dist/
+*.egg-info/
+.eggs/
+
+# Local credentials — keep `.env.example` tracked, never the real `.env`
+.env
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+.uv_cache/
+
+# Test and coverage outputs
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# Jupyter
+.ipynb_checkpoints/
+
+# Logs and runtime files
+*.log
+*.pid
+
+# IDE/editor
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS files
+.DS_Store
+Thumbs.db

plesty_bench-0.2.0/.gitlab-ci.yml

@@ -0,0 +1,152 @@
+stages:
+  - check
+  - security
+  - deploy
+  - release
+
+variables:
+  # Required for versioningit: the runner must fetch full Git history and tags.
+  GIT_DEPTH: "0"
+
+include:
+  - component: $CI_SERVER_FQDN/plesty/plesty-ci/plesty-standard-ci@main
+    inputs:
+      standard: quantum
+      extra_branch: exp
+      access_token: $CI_BOT_TOKEN
+
+# The template's hub-release publishes plesty-bench. Both PyPI publishers use
+# the same namespace/project/pipeline file, so they are told apart by the
+# GitLab environment the publishing job runs in (PyPI refuses two pending
+# publishers that differ only in the project name): pypi-bench here,
+# pypi-server below.
+hub-release:
+  environment:
+    name: pypi-bench
+    url: https://pypi.org/project/plesty-bench/
+
+# ---------------------------------------------------------------------------
+# The second distribution and the light installers — on tags.
+#
+# The standard template's hub-release publishes the wheel of this project
+# (plesty-bench, the client). The bench application is a second distribution,
+# plesty-server, assembled from the same tree by packaging/server_dist.py and
+# published here through the same trusted publisher (OIDC, no stored token).
+# The installers carry no application code: they install uv and run
+# `uv tool install "plesty-server[gui]==<version>"` on the bench.
+# ---------------------------------------------------------------------------
+.release-rules:
+  rules:
+    - if: $CI_COMMIT_TAG
+
+release:server-wheel:
+  stage: release
+  extends: .release-rules
+  image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
+  environment:
+    name: pypi-server
+    url: https://pypi.org/project/plesty-server/
+  id_tokens:
+    PYPI_ID_TOKEN:
+      aud: pypi
+  variables:
+    UV_LINK_MODE: copy
+    UV_CACHE_DIR: /tmp/uv-cache
+  before_script:
+    - git fetch --tags --force
+  script:
+    - uv sync --frozen
+    - VERSION="$(uv run python -c 'from importlib.metadata import version; print(version("plesty-bench"))')"
+    - echo "plesty-server $VERSION"
+    - uv run python packaging/server_dist.py --out dist-server --version "$VERSION"
+    - ls -la dist-server
+    - |
+      # Trusted publishing: mint an upload token from the job's ID token, as the
+      # standard template does for plesty-bench (a PYPI_TOKEN variable wins if set).
+      if [ -n "${PYPI_TOKEN:-}" ]; then
+        uv publish --token "$PYPI_TOKEN" dist-server/*
+      else
+        test -n "$PYPI_ID_TOKEN" || { echo "no OIDC ID token"; exit 1; }
+        API_TOKEN="$(python3 - <<'PY'
+      import json, os, urllib.request
+      req = urllib.request.Request("https://pypi.org/_/oidc/mint-token",
+          data=json.dumps({"token": os.environ["PYPI_ID_TOKEN"]}).encode(),
+          headers={"Content-Type": "application/json"})
+      with urllib.request.urlopen(req, timeout=30) as r:
+          print(json.load(r)["token"])
+      PY
+      )"
+        uv publish --token "$API_TOKEN" dist-server/*
+      fi
+  artifacts:
+    paths:
+      - dist-server/*.whl
+    expire_in: 1 year
+
+installer:windows:
+  stage: release
+  extends: .release-rules
+  tags:
+    - saas-windows-medium-amd64
+  before_script:
+    - powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+    - $env:Path = "$env:USERPROFILE\.local\bin;$env:Path"
+    - choco install innosetup -y --no-progress | Out-Null
+    - git fetch --tags --force
+  script:
+    - uv sync --frozen --group build
+    - $VERSION = (uv run python -c "from importlib.metadata import version; print(version('plesty-bench'))")
+    - uv run --group build python -c "from PIL import Image; Image.open('packaging/plesty-mark.png').save('packaging/plesty-mark.ico', sizes=[(256,256),(128,128),(64,64),(48,48),(32,32),(16,16)])"
+    - '& "C:\Program Files (x86)\Inno Setup 6\ISCC.exe" "/DAppVersion=$VERSION" packaging\windows\plesty-server.iss'
+    - Get-ChildItem dist
+  artifacts:
+    paths:
+      - dist/plesty-server-*-windows-setup.exe
+    expire_in: 1 year
+
+# The GitLab release for a tag: the Windows installer and the install script
+# for macOS/Linux from the package registry (permanent), plus the two PyPI
+# distributions — the Releases page is the download list.
+release:assets:
+  stage: release
+  extends: .release-rules
+  image: registry.gitlab.com/gitlab-org/release-cli:latest
+  needs:
+    - job: installer:windows
+      artifacts: true
+    - job: release:server-wheel
+      artifacts: false
+  variables:
+    REGISTRY: "$CI_API_V4_URL/projects/$CI_PROJECT_ID/packages/generic/plesty-server/$CI_COMMIT_TAG"
+  script:
+    - apk add --no-cache curl >/dev/null
+    - ls -la dist
+    - |
+      setup="$(ls dist/plesty-server-*-windows-setup.exe | head -1)"
+      [ -n "$setup" ] || { echo "no Windows installer"; exit 1; }
+      curl --fail --silent --show-error --header "JOB-TOKEN: $CI_JOB_TOKEN" \
+        --upload-file "$setup" "$REGISTRY/plesty-server-$CI_COMMIT_TAG-windows-setup.exe"
+      curl --fail --silent --show-error --header "JOB-TOKEN: $CI_JOB_TOKEN" \
+        --upload-file packaging/install.sh "$REGISTRY/install.sh"
+  release:
+    tag_name: $CI_COMMIT_TAG
+    name: "plesty-server $CI_COMMIT_TAG"
+    description: >-
+      Windows: run the installer (it installs uv and the application from PyPI;
+      Start-menu entry, optional desktop shortcut). macOS/Linux:
+      `curl -LsSf <install.sh link> | sh`. Developer machines: `uv tool install plesty-bench`.
+      Update a bench with `uv tool upgrade plesty-server`. See CHANGELOG.md.
+    assets:
+      links:
+        - name: "plesty-server-$CI_COMMIT_TAG-windows-setup.exe (Windows installer)"
+          url: "$REGISTRY/plesty-server-$CI_COMMIT_TAG-windows-setup.exe"
+          link_type: package
+        - name: "install.sh (macOS / Linux: curl -LsSf … | sh)"
+          url: "$REGISTRY/install.sh"
+          link_type: other
+        - name: "plesty-server on PyPI (the bench application)"
+          url: "https://pypi.org/project/plesty-server/"
+          link_type: other
+        - name: "plesty-bench on PyPI (the client)"
+          url: "https://pypi.org/project/plesty-bench/"
+          link_type: other

plesty_bench-0.2.0/CHANGELOG.md

@@ -0,0 +1,46 @@
+# Changelog
+
+The format is based on [Keep a Changelog](https://keepachangelog.com).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-08-19
+
+### Added
+- The bench application is published on PyPI as **`plesty-server`**
+  (`uv tool install "plesty-server[gui]"`; `plesty-server-gui` is a GUI
+  script — no console window on Windows), assembled by
+  `packaging/server_dist.py` next to `plesty-bench`.
+- Light installers that carry no application code: Windows `setup.exe`
+  (installs `uv`, then the pinned `plesty-server[gui]` from PyPI; Start-menu
+  entries, optional desktop shortcut, uninstaller) and `install.sh` for
+  macOS (`~/Applications/PLESTY Bench.app` launcher, Launchpad) and Linux
+  (`.desktop` entry). Application icons from the PLESTY mark.
+- The console remembers the last fleet it used (`<home>/last-fleet`) so a
+  double-click reopens it.
+
+### Changed
+- Repository renamed to `plesty/core/plesty-bench` (the old URL redirects).
+- The PyInstaller bundles of 0.1.0 are gone: a bench installs from PyPI.
+
+## [0.1.0] - 2026-08-19
+
+First release: the bench application and the `plesty-bench` client.
+
+### Added
+- `plesty.server`: the bench application — model (fleet file, inventory keyed by
+  version or `git-<ref>`, jobs, processes, field tests, catalogue, `.env`),
+  services (installer with `uv`/`git`, detached launcher, job runner,
+  supervisor with `describe` probe and port ownership, agent, catalogue),
+  presenter `Bench`, the `plesty-server` CLI (`declare/install/update/start/
+  stop/status/log/field-test/reports/jobs/fleet up|down|run/agent/gui`), and
+  the Qt console on plesty-lib's theme (working-fleet check column, device and
+  fleet button bars, declare/config/fleet-file/catalogue/field-test/job
+  dialogs).
+- `plesty.bench`: the client published to PyPI — `BenchClient`
+  (describe/exec/fetch/follow over the plesty-lib wire) and the `plesty-bench`
+  command, "the CLI is the API".
+- `host.py`: every platform difference in one module (guarded by a test);
+  `reexec.py`: source vs PyInstaller bundle.
+- Packaging: PyInstaller bundles per OS (console + windowed executables) built
+  by CI and listed on the GitLab Release from the package registry.

plesty_bench-0.2.0/LICENSE

@@ -0,0 +1,184 @@
+Copyright (C) 2026 Plesty Development Team
+
+This file is part of Plesty.
+
+Plesty is free software: you can redistribute it and/or modify
+it under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+Plesty is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public License
+along with Plesty. If not, see <https://www.gnu.org/licenses/> or the copy below.
+
+#########################################################################
+
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

plesty_bench-0.2.0/LICENSES/LGPL-3.0-or-later.txt

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

plesty_bench-0.2.0/PKG-INFO

@@ -0,0 +1,45 @@
+Metadata-Version: 2.5
+Name: plesty-bench
+Version: 0.2.0
+Summary: Client for a PLESTY bench running plesty-server: run its commands and fetch its reports from another machine.
+Author-email: Yunshuang Yuan <yuanyunshuang@gmail.com>
+Maintainer-email: Plesty Development Team <plesty.dev@example.com>
+License-Expression: LGPL-3.0-or-later
+License-File: LICENSE
+License-File: LICENSES/LGPL-3.0-or-later.txt
+Requires-Python: >=3.12
+Requires-Dist: click>=8.1
+Requires-Dist: pyzmq>=26
+Provides-Extra: gui
+Requires-Dist: plesty-lib>=0.3.3; extra == 'gui'
+Requires-Dist: plesty-lib[gui]>=0.3.3; extra == 'gui'
+Requires-Dist: pyyaml>=6.0; extra == 'gui'
+Provides-Extra: server
+Requires-Dist: plesty-lib>=0.3.3; extra == 'server'
+Requires-Dist: pyyaml>=6.0; extra == 'server'
+Description-Content-Type: text/markdown
+
+# plesty-server
+
+The bench PC's own console for the PLESTY platform: installs hub device
+modules (several versions side by side), launches and supervises their device
+servers, runs field tests against the instruments, and keeps the logs — so
+running the platform on a lab bench is no longer hand work.
+
+Two deliverables from one repository:
+
+- **`plesty.server`** — the bench application (CLI `plesty-server`, Qt
+  console `plesty-server-gui`, agent), on PyPI as **`plesty-server`**:
+  `uv tool install "plesty-server[gui]"` — or the light installers from the
+  [releases](https://gitlab.com/plesty/core/plesty-bench/-/releases) (Windows
+  `setup.exe`; `install.sh` for macOS/Linux), which do exactly that plus the
+  Start-menu / Launchpad entry.
+- **`plesty.bench`** — the remote client, on PyPI as **`plesty-bench`**
+  (`uv tool install plesty-bench`). The CLI is the API:
+  `plesty-bench -b lab-bench-03 field-test pm100d` runs it on the bench and
+  follows the job.
+
+Built as model – services – presenter – view, with one module (`host`) for
+everything that differs between Windows and POSIX. See `docs/` for the
+architecture, the process-management and cross-platform primers, the console
+and the remote loop.