jkctl 0.1.0__tar.gz

jkctl-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,51 @@
+name: CI
+
+on:
+  push:
+    branches: ["**"]
+  # A pull request from a branch of this repository was already checked by
+  # the push above; listening to both would run every one of them twice.
+  # A fork's branch produces no push event here, so the `if` on the job
+  # below lets those -- and only those -- through.
+  pull_request:
+  # release.yml calls this workflow before it builds, so a tag cannot
+  # publish what the checks have not passed.
+  workflow_call:
+
+permissions:
+  contents: read
+
+# A newer commit on the same branch makes the older run's answer moot.
+concurrency:
+  group: ci-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    if: >-
+      github.event_name != 'pull_request' ||
+      github.event.pull_request.head.repo.full_name != github.repository
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.12", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+      # --locked: a uv.lock that no longer matches pyproject.toml is a
+      # mistake to report, not one to paper over with a fresh resolution.
+      # --group browser: the V8 htmcheck parses templates in is kept out of
+      # the default set so that installing and developing jkctl stays light
+      # on an armv7 host.  CI is where it must not be missing: without it
+      # htmcheck and its tests would skip, and skip green.
+      - run: uv sync --locked --group browser
+      - run: uv run ruff format --check .
+      - run: uv run ruff check .
+      - run: uv run ty check
+      # The browser half: Biome parses and lints it, and the two cross-file
+      # checks out of `devicectl.devtools` run under pytest.
+      - run: uv run pytest

jkctl-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,53 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  # A tag must not publish what the checks have not passed.
+  check:
+    uses: ./.github/workflows/ci.yml
+
+  publish:
+    needs: check
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: write   # to create the GitHub release
+      id-token: write   # for PyPI trusted publishing; no token to keep
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      # The version lives in one place.  A tag that disagrees with it would
+      # publish something under a name nobody can reproduce from the source.
+      - name: The tag must match __version__
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          version="$(grep -Po '(?<=^__version__ = ")[^"]+' src/jkctl/__init__.py)"
+          if [ "$tag" != "$version" ]; then
+            echo "tag $tag does not match __version__ $version" >&2
+            exit 1
+          fi
+
+      - run: uv build
+
+      # Install the wheel that is about to be published, on its own, and see
+      # that it runs -- a missing package data file would show up here.
+      - name: Smoke-test the built wheel
+        run: |
+          uv run --no-project --with dist/*.whl jkctl --version
+          uv run --no-project --with dist/*.whl jkctl protocols list --can
+
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Create the GitHub release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release create "$GITHUB_REF_NAME" --generate-notes dist/*

jkctl-0.1.0/.gitignore

@@ -0,0 +1,23 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+venv/
+
+# Never commit vendor firmware images or encrypted datasource containers
+*.jkbms
+*.jsonds
+*.bin
+*.hex
+
+# Probe output and local scratch
+probe-result*.json
+probe-result*.log
+probe*.json
+probe*.log
+
+# Build output and tool caches
+/dist/
+.ruff_cache/
+.pytest_cache/

jkctl-0.1.0/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+Notable changes, newest first. The version is set in `src/jkctl/__init__.py`;
+tagging `vX.Y.Z` publishes it (see `.github/workflows/release.yml`).
+
+## 0.1.0 — 2026-09-26
+
+The first release. A tool for JK BMS battery management systems on an RS485
+bus, reimplemented from JK's own Windows application and register-map
+documents. It requires `devicectl-core>=0.1.0`.
+
+What it does:
+
+- **Finds and reads a bus.** Scans the sixteen addresses, reports nameplate,
+  live pack data, per-cell voltages and resistances, alarms, the board's own
+  fault history, and every register of every table -- one board or the whole
+  bank at once, as text or `--json`.
+- **Writes the configuration.** The whole settings table, typed, scaled and
+  range-checked against JK's own datasource before anything goes out, with a
+  write always showing what it will change; the one-key chemistry presets, the
+  three main switches, the multiplexed on/off settings, the port protocols and
+  the dry contacts.
+- **Board actions.** The emergency start, the power-off, calibration, the
+  address, the clock, and the three actions JK's document does not list.
+- **Firmware.** Validates and flashes a `.jkbms` file the way JK's own
+  application does, needing no crypto package (PyCryptodome, `cryptography`,
+  system OpenSSL, or a bundled pure-Python AES).
+- **A web interface, first.** `jkctl` with no command serves a local page and
+  opens a browser on it -- the bank as tiles, live dashboards, draggable
+  setpoint bands, and every command the terminal has -- built on the shared
+  `devicectl-core` design system with no build step.
+- **Diagnostics.** `jkctl probe` characterises a silent bus, `jkctl doctor`
+  reports what looks wrong, `jkctl simulate` serves a fake BMS, and a serial
+  trace can be turned on from the page and sent on.
+
+See the [README](README.md) and [docs](docs/) for what each of those does.

jkctl-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,144 @@
+# Contributing
+
+## Getting set up
+
+```sh
+uv sync
+uv run pytest
+```
+
+That is the light set -- pytest, ruff, ty -- pure Python, quick, and it
+installs anywhere the program does. The two checks that need a real engine
+(an embedded V8, a headless Chromium) are in a separate `browser` group:
+
+```sh
+uv sync --group browser
+```
+
+Take it if you touch the web UI. It is opt-in because jkctl is meant to run
+on small hosts -- a Raspberry Pi 3 reports `armv7l`, and `mini-racer`
+publishes no armv7 wheel, so having it in the default set would turn
+`uv run jkctl` in a checkout into a V8 build. Once the group is synced a
+plain `uv run` keeps it; a plain `uv sync` trims back to the light set.
+
+Everything the checks run:
+
+```sh
+uv run ruff format --check .
+uv run ruff check .
+uv run ty check
+uv run pytest
+biome ci src/jkctl/web/static/          # the browser half
+```
+
+[Biome] is a single native binary and needs no Node (`pacman -S biome`, a
+release binary, or `npx @biomejs/biome`). It is not a project dependency, and
+the two Python checks run under `pytest` as well, so a plain `uv run pytest`
+covers the browser half too -- `htmcheck` and its tests skip themselves,
+saying which group to sync, when the V8 is not there.
+
+Two more need a browser, so they are not in that list and are not run under
+`pytest`. They drive the real page over `jkctl ui --simulate`, which puts a
+bank of fake boards on an in-memory bus and needs no hardware:
+
+```sh
+uv sync --group browser                        # once: playwright
+uv run python -m playwright install chromium   # once: the browser itself
+uv run tools/rendercheck.py    # what only a layout engine sees
+uv run tools/screenshot.py     # docs/img/, for the README
+```
+
+`rendercheck` is worth running after anything that touches the page. Every
+defect it looks for got past all seven checks above: a value column wide
+enough to push four columns off-screen, a model number split across two
+lines, a tab that renders nothing because an import was mistyped. None of
+them is a crash, so nothing without a layout engine can see them.
+
+[Biome]: https://biomejs.dev/
+
+## How the code is laid out
+
+`src/jkctl/` is one module per subject, and **none of them prints**. Only
+`cli/` prints, prompts, or returns exit codes. That is what keeps the device
+logic testable and what would let a second front end reuse it unchanged.
+
+- `modbus.py` is the wire: framing, CRC, retries, the register bases.
+- `protocol.py` is the field layout, parsed from JK's own datasource.
+- `registers.py` joins the two: a named, typed, bounded, addressable register,
+  and whether JK's document marks it writable.
+- `values.py` turns what someone typed into what the wire takes, and refuses
+  what will not fit.
+- `device.py` is one BMS, read and written by field name.
+- `identity.py`, `runtime.py`, `settings.py`, `controls.py` are one subject
+  each, built on `device.py`.
+- `firmware.py` and `upgrade.py` are the `.jkbms` container and the transfer.
+- `doctor.py` is composition over those: one read, and everything that can be
+  concluded from holding two of its numbers up against each other.
+- `history.py` and `logcodes.py` are the board's own stored records: the
+  layout, and what JK calls each code.
+- `web/` is the second front end, and it obeys the same rule: it prints
+  nothing and decides nothing about the device, it calls the same modules the
+  commands call. `web/session.py` owns the serial port and runs every request
+  through one worker, because only one program can hold a port and only one
+  place should know that.
+
+## The browser half
+
+`src/jkctl/web/static/` is plain ES modules and plain CSS -- edit and reload,
+there is nothing to build, and the files that ship in the wheel are the files
+you edit. Three things check it in place of a build step:
+
+- **Biome** parses and lints it, better than anything hand-written here could.
+- **`devicectl.devtools.frontlint`** looks across the files, which is normally
+  a bundler's job: every import has to name a file that exists and a name it
+  exports, and every export has to be imported by somebody. Without it a
+  mistyped path is a blank page found by reloading and not before.
+- **`devicectl.devtools.htmcheck`** renders every `html` template through the vendored
+  preact-htm bundle -- the same parser the browser runs -- and reports the one
+  shape no valid output contains. An attribute that lost its `$` does not
+  crash the page; it quietly swallows the markup up to the next `}`.
+
+Adding a tab means a module in `static/js/`, an entry in `TABS` in `app.js`,
+and an endpoint in `web/api.py` that calls the module the CLI already calls.
+Do not reach for the device from a request handler: hand the work to the
+worker, which owns the port.
+
+## Adding a command
+
+Write the handler in the right module of `src/jkctl/cli/commands/`, describe
+it in that module's `add_parsers`, and name it in that module's `COMMANDS`.
+Nothing outside that file changes. If the command needs no serial port, or
+only a bus rather than one addressed unit, say so with `Need` in the
+`Command` -- do not open anything yourself.
+
+## Tests
+
+No test may need hardware, a serial port or a network. The suite wires a real
+`modbus.Bus` straight to `simulator.Sim` in memory (`tests/conftest.py`), so a
+CLI test exercises the actual framing, chunking and decoding. If you teach the
+tool about a new device behaviour, teach the simulator about it too -- that is
+what stops the tool being tested against a model of the device that is kinder
+than the device.
+
+CLI tests call `cli.main([...])` and assert on the exit code and `capsys`.
+Prompts are tested by patching `builtins.input`, including the `EOFError`
+case, because a command left running unattended must stop rather than raise.
+
+## Writing about the device
+
+Every non-obvious constant, refusal and workaround in this codebase exists
+because a real unit behaved that way. Say so in the comment, and say how it is
+known -- a measurement, JK's own document, or a function in the decompiled
+application. A comment that says *what* the code does is worth little; one
+that says why the device made it necessary is worth a great deal, and it is
+the only defence against someone later "simplifying" a workaround away.
+
+Anything not yet proven against hardware must say so, in the docstring and in
+`docs/reference.md`.
+
+## Before you send it
+
+- `uv run ruff format . && uv run ruff check . && uv run ty check && uv run pytest`
+- New device behaviour recorded in `research/windows/windows-findings.md`
+  with its evidence.
+- `docs/reference.md` updated if you changed what is proven or what is not.

jkctl-0.1.0/LICENSE

@@ -0,0 +1,287 @@
+                      EUROPEAN UNION PUBLIC LICENCE v. 1.2
+                      EUPL © the European Union 2007, 2016
+
+This European Union Public Licence (the ‘EUPL’) applies to the Work (as defined
+below) which is provided under the terms of this Licence. Any use of the Work,
+other than as authorised under this Licence is prohibited (to the extent such
+use is covered by a right of the copyright holder of the Work).
+
+The Work is provided under the terms of this Licence when the Licensor (as
+defined below) has placed the following notice immediately following the
+copyright notice for the Work:
+
+        Licensed under the EUPL
+
+or has expressed by any other means his willingness to license under the EUPL.
+
+1. Definitions
+
+In this Licence, the following terms have the following meaning:
+
+- ‘The Licence’: this Licence.
+
+- ‘The Original Work’: the work or software distributed or communicated by the
+  Licensor under this Licence, available as Source Code and also as Executable
+  Code as the case may be.
+
+- ‘Derivative Works’: the works or software that could be created by the
+  Licensee, based upon the Original Work or modifications thereof. This Licence
+  does not define the extent of modification or dependence on the Original Work
+  required in order to classify a work as a Derivative Work; this extent is
+  determined by copyright law applicable in the country mentioned in Article 15.
+
+- ‘The Work’: the Original Work or its Derivative Works.
+
+- ‘The Source Code’: the human-readable form of the Work which is the most
+  convenient for people to study and modify.
+
+- ‘The Executable Code’: any code which has generally been compiled and which is
+  meant to be interpreted by a computer as a program.
+
+- ‘The Licensor’: the natural or legal person that distributes or communicates
+  the Work under the Licence.
+
+- ‘Contributor(s)’: any natural or legal person who modifies the Work under the
+  Licence, or otherwise contributes to the creation of a Derivative Work.
+
+- ‘The Licensee’ or ‘You’: any natural or legal person who makes any usage of
+  the Work under the terms of the Licence.
+
+- ‘Distribution’ or ‘Communication’: any act of selling, giving, lending,
+  renting, distributing, communicating, transmitting, or otherwise making
+  available, online or offline, copies of the Work or providing access to its
+  essential functionalities at the disposal of any other natural or legal
+  person.
+
+2. Scope of the rights granted by the Licence
+
+The Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
+sublicensable licence to do the following, for the duration of copyright vested
+in the Original Work:
+
+- use the Work in any circumstance and for all usage,
+- reproduce the Work,
+- modify the Work, and make Derivative Works based upon the Work,
+- communicate to the public, including the right to make available or display
+  the Work or copies thereof to the public and perform publicly, as the case may
+  be, the Work,
+- distribute the Work or copies thereof,
+- lend and rent the Work or copies thereof,
+- sublicense rights in the Work or copies thereof.
+
+Those rights can be exercised on any media, supports and formats, whether now
+known or later invented, as far as the applicable law permits so.
+
+In the countries where moral rights apply, the Licensor waives his right to
+exercise his moral right to the extent allowed by law in order to make effective
+the licence of the economic rights here above listed.
+
+The Licensor grants to the Licensee royalty-free, non-exclusive usage rights to
+any patents held by the Licensor, to the extent necessary to make use of the
+rights granted on the Work under this Licence.
+
+3. Communication of the Source Code
+
+The Licensor may provide the Work either in its Source Code form, or as
+Executable Code. If the Work is provided as Executable Code, the Licensor
+provides in addition a machine-readable copy of the Source Code of the Work
+along with each copy of the Work that the Licensor distributes or indicates, in
+a notice following the copyright notice attached to the Work, a repository where
+the Source Code is easily and freely accessible for as long as the Licensor
+continues to distribute or communicate the Work.
+
+4. Limitations on copyright
+
+Nothing in this Licence is intended to deprive the Licensee of the benefits from
+any exception or limitation to the exclusive rights of the rights owners in the
+Work, of the exhaustion of those rights or of other applicable limitations
+thereto.
+
+5. Obligations of the Licensee
+
+The grant of the rights mentioned above is subject to some restrictions and
+obligations imposed on the Licensee. Those obligations are the following:
+
+Attribution right: The Licensee shall keep intact all copyright, patent or
+trademarks notices and all notices that refer to the Licence and to the
+disclaimer of warranties. The Licensee must include a copy of such notices and a
+copy of the Licence with every copy of the Work he/she distributes or
+communicates. The Licensee must cause any Derivative Work to carry prominent
+notices stating that the Work has been modified and the date of modification.
+
+Copyleft clause: If the Licensee distributes or communicates copies of the
+Original Works or Derivative Works, this Distribution or Communication will be
+done under the terms of this Licence or of a later version of this Licence
+unless the Original Work is expressly distributed only under this version of the
+Licence — for example by communicating ‘EUPL v. 1.2 only’. The Licensee
+(becoming Licensor) cannot offer or impose any additional terms or conditions on
+the Work or Derivative Work that alter or restrict the terms of the Licence.
+
+Compatibility clause: If the Licensee Distributes or Communicates Derivative
+Works or copies thereof based upon both the Work and another work licensed under
+a Compatible Licence, this Distribution or Communication can be done under the
+terms of this Compatible Licence. For the sake of this clause, ‘Compatible
+Licence’ refers to the licences listed in the appendix attached to this Licence.
+Should the Licensee's obligations under the Compatible Licence conflict with
+his/her obligations under this Licence, the obligations of the Compatible
+Licence shall prevail.
+
+Provision of Source Code: When distributing or communicating copies of the Work,
+the Licensee will provide a machine-readable copy of the Source Code or indicate
+a repository where this Source will be easily and freely available for as long
+as the Licensee continues to distribute or communicate the Work.
+
+Legal Protection: This Licence does not grant permission to use the trade names,
+trademarks, service marks, or 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 copyright notice.
+
+6. Chain of Authorship
+
+The original Licensor warrants that the copyright in the Original Work granted
+hereunder is owned by him/her or licensed to him/her and that he/she has the
+power and authority to grant the Licence.
+
+Each Contributor warrants that the copyright in the modifications he/she brings
+to the Work are owned by him/her or licensed to him/her and that he/she has the
+power and authority to grant the Licence.
+
+Each time You accept the Licence, the original Licensor and subsequent
+Contributors grant You a licence to their contributions to the Work, under the
+terms of this Licence.
+
+7. Disclaimer of Warranty
+
+The Work is a work in progress, which is continuously improved by numerous
+Contributors. It is not a finished work and may therefore contain defects or
+‘bugs’ inherent to this type of development.
+
+For the above reason, the Work is provided under the Licence on an ‘as is’ basis
+and without warranties of any kind concerning the Work, including without
+limitation merchantability, fitness for a particular purpose, absence of defects
+or errors, accuracy, non-infringement of intellectual property rights other than
+copyright as stated in Article 6 of this Licence.
+
+This disclaimer of warranty is an essential part of the Licence and a condition
+for the grant of any rights to the Work.
+
+8. Disclaimer of Liability
+
+Except in the cases of wilful misconduct or damages directly caused to natural
+persons, the Licensor will in no event be liable for any direct or indirect,
+material or moral, damages of any kind, arising out of the Licence or of the use
+of the Work, including without limitation, damages for loss of goodwill, work
+stoppage, computer failure or malfunction, loss of data or any commercial
+damage, even if the Licensor has been advised of the possibility of such damage.
+However, the Licensor will be liable under statutory product liability laws as
+far such laws apply to the Work.
+
+9. Additional agreements
+
+While distributing the Work, You may choose to conclude an additional agreement,
+defining obligations or services consistent with this Licence. However, if
+accepting obligations, You may act only on your own behalf and on your sole
+responsibility, not on behalf of the original Licensor or 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
+the fact You have accepted any warranty or additional liability.
+
+10. Acceptance of the Licence
+
+The provisions of this Licence can be accepted by clicking on an icon ‘I agree’
+placed under the bottom of a window displaying the text of this Licence or by
+affirming consent in any other similar way, in accordance with the rules of
+applicable law. Clicking on that icon indicates your clear and irrevocable
+acceptance of this Licence and all of its terms and conditions.
+
+Similarly, you irrevocably accept this Licence and all of its terms and
+conditions by exercising any rights granted to You by Article 2 of this Licence,
+such as the use of the Work, the creation by You of a Derivative Work or the
+Distribution or Communication by You of the Work or copies thereof.
+
+11. Information to the public
+
+In case of any Distribution or Communication of the Work by means of electronic
+communication by You (for example, by offering to download the Work from a
+remote location) the distribution channel or media (for example, a website) must
+at least provide to the public the information requested by the applicable law
+regarding the Licensor, the Licence and the way it may be accessible, concluded,
+stored and reproduced by the Licensee.
+
+12. Termination of the Licence
+
+The Licence and the rights granted hereunder will terminate automatically upon
+any breach by the Licensee of the terms of the Licence.
+
+Such a termination will not terminate the licences of any person who has
+received the Work from the Licensee under the Licence, provided such persons
+remain in full compliance with the Licence.
+
+13. Miscellaneous
+
+Without prejudice of Article 9 above, the Licence represents the complete
+agreement between the Parties as to the Work.
+
+If any provision of the Licence is invalid or unenforceable under applicable
+law, this will not affect the validity or enforceability of the Licence as a
+whole. Such provision will be construed or reformed so as necessary to make it
+valid and enforceable.
+
+The European Commission may publish other linguistic versions or new versions of
+this Licence or updated versions of the Appendix, so far this is required and
+reasonable, without reducing the scope of the rights granted by the Licence. New
+versions of the Licence will be published with a unique version number.
+
+All linguistic versions of this Licence, approved by the European Commission,
+have identical value. Parties can take advantage of the linguistic version of
+their choice.
+
+14. Jurisdiction
+
+Without prejudice to specific agreement between parties,
+
+- any litigation resulting from the interpretation of this License, arising
+  between the European Union institutions, bodies, offices or agencies, as a
+  Licensor, and any Licensee, will be subject to the jurisdiction of the Court
+  of Justice of the European Union, as laid down in article 272 of the Treaty on
+  the Functioning of the European Union,
+
+- any litigation arising between other parties and resulting from the
+  interpretation of this License, will be subject to the exclusive jurisdiction
+  of the competent court where the Licensor resides or conducts its primary
+  business.
+
+15. Applicable Law
+
+Without prejudice to specific agreement between parties,
+
+- this Licence shall be governed by the law of the European Union Member State
+  where the Licensor has his seat, resides or has his registered office,
+
+- this licence shall be governed by Belgian law if the Licensor has no seat,
+  residence or registered office inside a European Union Member State.
+
+Appendix
+
+‘Compatible Licences’ according to Article 5 EUPL are:
+
+- GNU General Public License (GPL) v. 2, v. 3
+- GNU Affero General Public License (AGPL) v. 3
+- Open Software License (OSL) v. 2.1, v. 3.0
+- Eclipse Public License (EPL) v. 1.0
+- CeCILL v. 2.0, v. 2.1
+- Mozilla Public Licence (MPL) v. 2
+- GNU Lesser General Public Licence (LGPL) v. 2.1, v. 3
+- Creative Commons Attribution-ShareAlike v. 3.0 Unported (CC BY-SA 3.0) for
+  works other than software
+- European Union Public Licence (EUPL) v. 1.1, v. 1.2
+- Québec Free and Open-Source Licence — Reciprocity (LiLiQ-R) or Strong
+  Reciprocity (LiLiQ-R+).
+
+The European Commission may update this Appendix to later versions of the above
+licences without producing a new version of the EUPL, as long as they provide
+the rights granted in Article 2 of this Licence and protect the covered Source
+Code from exclusive appropriation.
+
+All other changes or additions to this Appendix require the production of a new
+EUPL version.

jkctl-0.1.0/NOTICE

@@ -0,0 +1,34 @@
+NOTICE
+======
+
+This project is licensed under the European Union Public Licence v1.2
+(EUPL-1.2) -- see LICENSE. Five files shipped in this distribution are not
+covered by that license and remain under their own terms:
+
+* ``src/jkctl/protocol_en.json`` and ``src/jkctl/protocol_zh.json`` -- the
+  BMS frame and field layout, decrypted from ``config/en_US.jsonds`` and
+  ``config/zh_CN.jsonds`` as shipped with JK BMS Monitor 3.11.0. Copyright
+  Chengdu JIKONG Technology Co., Ltd. Included unmodified (beyond
+  decryption) for interoperability with JK battery management systems; no
+  license to redistribute them is granted by this project beyond what
+  their copyright holder allows.
+
+* ``src/jkctl/protocols.json`` -- the UART, CAN and trigger-source lists
+  the same application shows in its drop-downs, extracted from its
+  resources. The English column beside each is this project's own
+  translation and is covered by the EUPL like the rest of it. Same
+  copyright holder for the original strings, same terms.
+
+* ``src/jkctl/logcodes.json`` -- what the same application calls each code
+  a JK board writes into its stored fault records, extracted from its
+  code. Same copyright holder, same terms.
+
+  How all four were obtained is recorded in ``docs/how-it-works.md`` and,
+  in full, in ``research/windows/windows-findings.md``.
+
+* ``src/jkctl/web/static/vendor/preact-htm.module.js`` -- Preact and htm,
+  bundled as one ES module. Copyright Jason Miller and contributors, MIT
+  License; the full notice is embedded as a comment at the top of the file.
+  Upstream: https://preactjs.com/ and https://github.com/developit/htm
+
+Everything else in this distribution is licensed under the EUPL-1.2.