prusaslicer-py 0.1.0__tar.gz

prusaslicer_py-0.1.0/.github/dependabot.yml

@@ -0,0 +1,20 @@
+version: 2
+updates:
+  # The pins live in pyproject.toml's [dependency-groups] and uv.lock; there is
+  # no requirements.txt left for the pip ecosystem to read.
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: build
+    groups:
+      python:
+        patterns: ["*"]
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ci

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

@@ -0,0 +1,70 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  # No branch filter: a stacked pull request is based on its parent branch, not
+  # on main, and a base change fires `edited`, which is not a default activity
+  # type -- so filtering on main means a retargeted PR gets no checks at all.
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  check:
+    name: Check
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - run: just setup
+      - run: just check
+
+  test:
+    name: Test (Python ${{ matrix.python-version }}, ${{ matrix.os }})
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 10
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+        os: [ubuntu-latest]
+        include:
+          - python-version: "3.11"
+            os: windows-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python-version }}
+      # PrusaSlicer is not installed on these runners, so the engine-dependent
+      # tests skip. That is an environment fault, not a pass -- the skip count
+      # in the log says how many tests were withheld. Do not set
+      # PRUSASLICER_PY_REQUIRE_ENGINE here until a runner actually has the
+      # engine; see docs/DECISIONS.md D3.
+      - run: just setup
+      - run: just test
+
+  ok:
+    name: ok
+    if: always()
+    needs: [check, test]
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - name: Fail if any upstream job failed or was cancelled
+        if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+        run: exit 1
+      - name: Pass
+        run: echo 'All checks passed'

prusaslicer_py-0.1.0/.github/workflows/engine.yml

@@ -0,0 +1,158 @@
+name: Engine
+
+# The real engine, across the ways people actually install it.
+#
+# ci.yml runs the mocked suite everywhere and SKIPS the engine tests, because
+# no standard runner has PrusaSlicer. That leaves the end-to-end slice path --
+# the reason this package exists -- covered by stubs alone, and stubs are what
+# hid `--version` (which PrusaSlicer has never supported) and the fact that a
+# Flatpak install was invisible to discovery.
+#
+# Every job here sets PRUSASLICER_PY_REQUIRE_ENGINE=1, so a failed install is a
+# LOUD failure rather than a green run full of skips. A job that cannot get the
+# engine must not look like a job that tested it.
+#
+# Not on every push: these install a large GUI application and are slower and
+# more fragile than the gate. Run on demand, and weekly so upstream packaging
+# changes surface without anyone remembering to look.
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: "0 6 * * 1" # Mondays, 06:00 UTC
+
+permissions:
+  contents: read
+
+concurrency:
+  group: engine-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  PRUSASLICER_PY_REQUIRE_ENGINE: "1"
+
+jobs:
+  flatpak:
+    name: Linux / Flatpak (Flathub)
+    runs-on: ubuntu-latest
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - name: Install PrusaSlicer from Flathub
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y flatpak
+          sudo flatpak remote-add --if-not-exists flathub \
+            https://dl.flathub.org/repo/flathub.flatpakrepo
+          sudo flatpak install -y --noninteractive flathub com.prusa3d.PrusaSlicer
+      - name: Show what was installed
+        run: flatpak info com.prusa3d.PrusaSlicer | head -20
+      - run: just setup
+      - name: Full suite, engine required
+        # PRUSASLICER_PY_REQUIRE_ENGINE is set at workflow level, so a missing
+        # engine fails here rather than skipping. `just test` rather than
+        # `just test-engine`: the latter prefixes `VAR=x cmd`, which is
+        # POSIX-only and does not run on the Windows job.
+        run: just test
+      - name: Capture and extract the CLI surface
+        run: |
+          just capture-cli
+          just extract-cli
+      - name: Full suite again, now with the captured corpus present
+        # The corpus tests skip when scripts/01_helps is empty; this is the one
+        # place they actually run, against a real PrusaSlicer's real --help.
+        run: just test
+
+  linux-apt:
+    name: Linux / distro package on PATH
+    runs-on: ubuntu-latest
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - name: Install PrusaSlicer from the distro archive
+        # Was an AppImage job. PrusaSlicer publishes NO Linux assets on its
+        # GitHub releases -- checked across the last five, including 2.9.6:
+        # only setup.exe, .dmg and a Windows .zip. Linux is Flathub and distro
+        # packages, so this exercises plain PATH discovery via the distro
+        # package rather than an artifact that does not exist.
+        run: |
+          set -euo pipefail
+          sudo apt-get update
+          sudo apt-get install -y prusa-slicer
+          command -v prusa-slicer
+          prusa-slicer --help | head -1
+      - run: just setup
+      - name: Full suite, engine required
+        run: just test
+
+  macos:
+    name: macOS / Homebrew cask
+    runs-on: macos-latest
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - name: Install PrusaSlicer
+        run: |
+          set -euo pipefail
+          brew install --cask prusaslicer
+          # The cask installs an .app bundle; expose the CLI on PATH.
+          sudo ln -sf "/Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer" \
+            /usr/local/bin/prusa-slicer
+          command -v prusa-slicer
+      - run: just setup
+      - name: Full suite, engine required
+        # PRUSASLICER_PY_REQUIRE_ENGINE is set at workflow level, so a missing
+        # engine fails here rather than skipping. `just test` rather than
+        # `just test-engine`: the latter prefixes `VAR=x cmd`, which is
+        # POSIX-only and does not run on the Windows job.
+        run: just test
+
+  windows:
+    name: Windows / official portable zip
+    runs-on: windows-latest
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - name: Install PrusaSlicer from the official portable zip
+        # Was `choco install prusaslicer`. The package exists, but its install
+        # location is not something to guess at, and a recursive sweep of
+        # Program Files reported "not found" for an install that had probably
+        # succeeded. The upstream .zip is the same build the installer ships,
+        # needs no admin, pins an exact version, and lands the layout discovery
+        # expects: <dir>/prusa-slicer-console.exe beside <dir>/resources/shapes.
+        shell: pwsh
+        run: |
+          $ErrorActionPreference = 'Stop'
+          $rel = Invoke-RestMethod https://api.github.com/repos/prusa3d/PrusaSlicer/releases/latest
+          $asset = $rel.assets | Where-Object { $_.name -like '*.zip' } | Select-Object -First 1
+          if (-not $asset) { throw "no .zip asset in $($rel.tag_name)" }
+          Write-Host "downloading $($asset.name)"
+          Invoke-WebRequest $asset.browser_download_url -OutFile prusaslicer.zip
+          Expand-Archive prusaslicer.zip -DestinationPath "$env:RUNNER_TEMP\ps"
+          $exe = Get-ChildItem "$env:RUNNER_TEMP\ps" -Recurse -Filter 'prusa-slicer-console.exe' |
+                 Select-Object -First 1
+          if (-not $exe) { throw 'prusa-slicer-console.exe not present in the zip' }
+          Write-Host "found: $($exe.FullName)"
+          Add-Content -Path $env:GITHUB_PATH -Value $exe.DirectoryName
+      - name: Confirm it is on PATH
+        shell: pwsh
+        run: (Get-Command prusa-slicer-console.exe).Source
+      - run: just setup
+      - name: Full suite, engine required
+        run: just test

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

@@ -0,0 +1,87 @@
+name: Release
+
+# Publishes to PyPI via Trusted Publishing (OIDC). No API token is stored.
+#
+# The publisher on PyPI is pinned to heibench/prusaslicer-py, this workflow
+# filename, and the `pypi` environment -- all three must match or the publish
+# is refused.
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      expected_version:
+        description: "Exact version the dist must carry (e.g. 0.1.0) — guards against publishing the wrong ref"
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build and verify
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v7
+      - uses: extractions/setup-just@v4
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Gate on the same checks a pull request runs
+        run: |
+          just setup
+          just check
+          just test
+
+      - name: Build sdist and wheel
+        run: uv build
+
+      - name: Guard built version against the intended release
+        # A tag and a version are two statements of one fact; publishing when
+        # they disagree ships something nobody asked for under a name someone
+        # will trust.
+        run: |
+          set -eu
+          version=$(ls dist/*.tar.gz | sed -E 's|.*/prusaslicer_py-(.+)\.tar\.gz|\1|')
+          echo "built: $version"
+          case "${{ github.event_name }}" in
+            release) want="${GITHUB_REF_NAME#v}" ;;
+            workflow_dispatch) want="${{ inputs.expected_version }}" ;;
+          esac
+          if [ "$version" != "$want" ]; then
+            echo "::error::built version '$version' does not match intended release '$want'"
+            exit 1
+          fi
+          case "$version" in
+            *.dev*|*rc*|*a[0-9]*|*b[0-9]*)
+              echo "::error::refusing to publish pre-release version '$version'"
+              exit 1 ;;
+          esac
+
+      - name: Check the metadata PyPI will see
+        run: uv run --with twine twine check dist/*
+
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    environment: pypi
+    permissions:
+      id-token: write # PyPI Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

prusaslicer_py-0.1.0/.gitignore

@@ -0,0 +1,89 @@
+# Python bytecode files
+__pycache__/
+*.py[cod]
+
+# Distribution / packaging
+.Python
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# mypy
+.mypy_cache/
+
+# Pytest
+.cache/
+
+# Coverage reports
+.coverage
+.coverage.*
+
+# dotenv
+.env
+.env.*
+
+# VS Code settings
+.vscode/
+
+# PyCharm
+.idea/
+
+# Operating system files
+.DS_Store
+Thumbs.db
+
+# Jupyter Notebook
+.ipynb_checkpoints/
+
+# PrusaSlicer Python egg-info
+prusaslicer_py.egg-info/
+
+# Python wheels
+*.whl
+
+# Cython build
+build/
+dist/
+
+# Sphinx documentation
+docs/_build/
+
+# PyInstaller
+*.spec
+
+# JetBrains IDE files
+.idea/
+
+# Sublime Text project files
+*.sublime-project
+*.sublime-workspace
+
+# MacOS Finder files
+._*
+
+# Windows Installer files
+*.cab
+*.msi
+*.msm
+*.msp
+
+# Ignore the output directory
+output/
+# uv / virtualenv
+.venv/
+
+# Tool caches
+.ruff_cache/
+.pytest_cache/
+
+# Captured PrusaSlicer help and everything derived from it (D8).
+# Regenerate with `just capture-cli` + `just extract-cli`.
+scripts/01_helps/
+scripts/02_structured_data/
+scripts/03_restructured_data/

prusaslicer_py-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,21 @@
+repos:
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.27.2
+    hooks:
+      - id: gitleaks
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-merge-conflict
+      - id: check-added-large-files
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.11.12
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

prusaslicer_py-0.1.0/AGENTS.md

@@ -0,0 +1,120 @@
+# AGENTS.md
+
+Instructions for humans and AI coding agents working in this repository.
+
+The org-wide contract at <https://github.com/heibench/.github/blob/main/AGENTS.md>
+is the floor. This file carries what is specific to this repository; where the
+two conflict, this file wins.
+
+## Project
+
+`prusaslicer-py` is a **driver**, not a checker. It puts the PrusaSlicer
+command-line interface under program control: locating the executable, invoking
+it, and returning what it established about the engine's output. It does not
+adjudicate a design, and it does not post-process G-code.
+
+`scripts/` holds a small extraction pipeline that turns PrusaSlicer's own
+`--help` output into a machine-readable description of its CLI surface
+(`scripts/03_restructured_data/*.json`). That artifact is a large part of what
+this repository is for. Each entry is
+`{option, aliases, value, description}`; see `docs/DECISIONS.md` D6, and treat
+the schema as stable.
+
+## Stack
+
+- **Python >= 3.11**, packaged with `hatchling`, dependencies managed by `uv`
+  against a committed `uv.lock`.
+- **No runtime dependencies.** The engine boundary is `subprocess`; keep it
+  that way. Adding a runtime dependency needs a decision entry.
+- **`prusaslicer_py/slicer.py` is the only module in the package that may
+  import `subprocess` or name an executable.** `scripts/01_store_helps.py` is
+  the one recorded exception; see `docs/DECISIONS.md` D1.
+- **Tooling** -- `ruff` (format + lint), `mypy` (types), `pytest` (tests),
+  `just` (task runner), `pre-commit`.
+
+## Layout
+
+```
+prusaslicer_py/     the driver; the only module that touches the engine
+tests/              pytest suite
+examples/           runnable usage examples
+scripts/            CLI-surface extraction pipeline (01 -> 02 -> 03)
+docs/DECISIONS.md   numbered decisions and their reasoning
+```
+
+## Commands
+
+```sh
+just setup          # uv sync
+just fmt            # format + autofix
+just check          # fmt-check + lint + typecheck (CI-equivalent)
+just test           # run tests; engine tests skip if PrusaSlicer is absent
+just test-engine    # run tests; engine tests FAIL if PrusaSlicer is absent
+just extract-cli    # regenerate scripts/02_ and 03_ data from captured help
+```
+
+Run `just check && just test` before every commit. Never `--no-verify`.
+
+## The engine is optional at test time, and that is load-bearing
+
+PrusaSlicer is not installed on most machines that will run this suite,
+including CI. A missing engine is an **environment fault, not a verdict**: it
+says nothing about whether this code is correct.
+
+- Tests that need the engine request the `engine` fixture in
+  `tests/conftest.py`. It skips when PrusaSlicer is not on `PATH`.
+- Setting `PRUSASLICER_PY_REQUIRE_ENGINE` turns that skip into a hard failure.
+  Use it on any machine where the engine is supposed to be present.
+- **A skipped test is not a passing test.** Guard per-test, never at module
+  import: a module-level gate reports one skipped line and silently takes every
+  test in the file with it.
+
+## Never let silence read as success
+
+The engine can exit `0` without producing the file it was asked for. A driver
+call that did not do the thing must not return as though it did:
+
+- Verify the artifact before reporting it. `slice_model` checks that the G-code
+  file exists and is non-empty, and returns a result describing it.
+- Capture the engine's `stdout`/`stderr` and hand them to the caller. A
+  diagnostic that only reaches the parent process's terminal is unavailable to
+  the program that needs it.
+- **Decode the engine's output with `errors="replace"`, always.** A strict
+  decode raises before the result can be checked, so a byte we cannot read
+  becomes a verdict on a slice that succeeded. See `docs/DECISIONS.md` D5.
+- Failure carries the same fields as success. Both `SliceEngineError` and
+  `SliceOutputError` expose `output_path`, `returncode`, `stdout` and `stderr`;
+  do not put a fact in a message string that the success path returns.
+- Do not add an "assume it worked" escape hatch.
+
+## Status -- what has actually been established
+
+Treat these lines as code: if a change makes one false, the change is not
+finished.
+
+- **The end-to-end path runs against a real engine on four install modes**,
+  in the `Engine` workflow: Flathub Flatpak, a Linux distro package on PATH,
+  a macOS Homebrew cask `.app` bundle, and the official Windows portable zip.
+  Each runs the whole suite with `PRUSASLICER_PY_REQUIRE_ENGINE=1`, including
+  `test_slice_produces_gcode_with_the_real_engine`.
+- **`CI` runs the mocked suite** on Linux (3.11/3.12/3.13) and Windows with no
+  engine, so the engine tests skip and the count says how many were withheld.
+- Earlier revisions of this file claimed `check_version` was in regular use on
+  Windows. That was false -- it called `--version`, which PrusaSlicer supports
+  on no platform. Kept here as a reminder that a Status line is a claim.
+
+## Constraints
+
+- Do not hand-edit `scripts/02_structured_data/` or
+  `scripts/03_restructured_data/`. They are generated; fix the generator and run
+  `just extract-cli`. A test regenerates them and fails if the committed files
+  have drifted from the committed parser.
+- Always name an encoding when reading or writing the help output and the JSON
+  -- in every stage, `01_store_helps.py` included. The help contains non-ASCII
+  characters, and a locale-dependent `open()` is how the data came to say
+  `°C`. Decode the engine itself with `errors="replace"`.
+- Do not reimplement PrusaSlicer's arithmetic. The premise is that the engine
+  knows what the slice is and we do not.
+- Do not add AI attribution to commits or PR descriptions -- no co-author
+  trailers, session links, or "generated with" footers.
+- Do not name, link, or describe any private repository in public output.

prusaslicer_py-0.1.0/CHANGELOG.md

@@ -0,0 +1,64 @@
+# Changelog
+
+All notable changes to prusaslicer-py are documented here. Follows
+[Keep a Changelog](https://keepachangelog.com) and
+[Semantic Versioning](https://semver.org).
+
+## [Unreleased]
+
+## [0.1.0] — 2026-09-06
+
+### Added
+
+First release. Notable, given this began as a thin `subprocess` wrapper:
+
+- Flatpak discovery. `shutil.which` cannot see a Flatpak — the app is not on
+  PATH and there is no binary to find — so a Flathub install, which is how
+  PrusaSlicer is normally installed on Linux, previously read as "not
+  installed". `PrusaSlicer.engine_kind` reports `path` or `flatpak` so a caller
+  can branch (D9).
+- `SliceResult` returned from `slice_model`, carrying `output_path`,
+  `size_bytes`, `returncode`, `stdout` and `stderr`. The artifact is verified to
+  exist and be non-empty before a result is returned, so "the engine produced
+  the file" and "the call did not raise" stop being the same claim (D5).
+- `SliceError`, with `SliceEngineError` and `SliceOutputError` siblings. Both
+  carry the same fields, so the failure path is as inspectable as the success
+  path.
+- `just capture-cli` regenerates PrusaSlicer's help locally, through the driver
+  rather than a hardcoded Windows executable name.
+- Real-engine CI across install modes — Flathub Flatpak, AppImage on PATH,
+  Homebrew cask, Chocolatey — each with a missing engine as a hard failure
+  rather than a skip.
+- Repository floor: `pyproject` + `uv` with a committed lock, `justfile`, CI on
+  Linux and Windows, pre-commit, `AGENTS.md`, `docs/DECISIONS.md`.
+
+### Fixed
+
+- `check_version()` called `--version`, which PrusaSlicer has never supported —
+  2.9.6 answers `Unknown option --version` and exits 1. The version is read
+  from the first line of `--help`, which is the only place the engine prints
+  it. Every stub in the suite answered `--version`, so the tests agreed with
+  the code and both were wrong.
+- `get_example_shapes()` ignored an explicitly supplied `slicer_path` and
+  re-ran discovery, raising `FileNotFoundError` even when handed a working
+  engine.
+- A Flatpak's own files are mounted at `/app` inside the sandbox, so bundled
+  example shapes were real to the caller and absent to the engine. Paths under
+  the app tree are translated; paths outside it are granted with
+  `--filesystem=<dir>`, only for the directories involved.
+- An undecodable byte in the engine's output raised `UnicodeDecodeError` before
+  the result could be verified, reporting failure for a slice that succeeded.
+- The CLI-surface extraction dropped 68 distinct options — every one whose
+  description began on the following line — mis-split 7 aliased options, and
+  carried cp1252 mojibake from a Windows capture. It also discarded any section
+  whose name matched none of three hardcoded buckets, which silently lost
+  PrusaSlicer 2.9.6's entire `input:` section.
+
+### Changed
+
+- Licensed under Apache-2.0, superseding MIT (D7).
+- PrusaSlicer's captured `--help` output is no longer committed; regenerate it
+  with `just capture-cli` (D8).
+
+[Unreleased]: https://github.com/heibench/prusaslicer-py/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/heibench/prusaslicer-py/releases/tag/v0.1.0

prusaslicer_py-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing
+
+## Getting set up
+
+```sh
+just setup          # sync the environment
+just check          # format check + lint + typecheck
+just test           # the suite
+```
+
+`just check && just test` is what CI runs. Run it before every commit, and
+never bypass hooks.
+
+## Tests and the engine
+
+Most of the suite runs without PrusaSlicer installed. The tests that need the
+real engine request the `engine` fixture, which **skips** when it is absent —
+a missing engine is an environment fault, not a verdict on the code.
+
+Set `PRUSASLICER_PY_REQUIRE_ENGINE=1` to turn that skip into a hard failure.
+CI does this on the runners that install the engine, so "the engine is missing"
+cannot masquerade as a green run.
+
+```sh
+just test-engine    # the whole suite, engine required (POSIX shells)
+```
+
+If you have PrusaSlicer installed, please run it and report what happens. The
+engine is installed several different ways — PATH, Flatpak, AppImage, macOS
+bundle, Windows installer — and discovery has been wrong about at least one of
+them before.
+
+## The CLI surface data
+
+`scripts/01_helps/` and everything derived from it are **not committed**: they
+are PrusaSlicer's own output and this repository is Apache-2.0 (D8). Regenerate
+with:
+
+```sh
+just capture-cli    # needs PrusaSlicer installed
+just extract-cli
+```
+
+The extraction tests skip without that corpus, and say so.
+
+## Conventions
+
+- Conventional Commits: `type(scope): description`, imperative, lowercase, no
+  trailing period, subject ≤ 72 characters.
+- One logical change per commit; branch and open a pull request.
+- Decisions with consequences go in [`docs/DECISIONS.md`](docs/DECISIONS.md),
+  numbered. Do not relitigate a numbered decision — supersede it.
+- A check that cannot fail is not a check. If you add one, break the thing it
+  checks and watch it go red before you trust it.