io.github.UnicornGraveyard/slicerbridge

- The MCP server's read-only tools state all four behaviour hints (not destructive, idempotent, as well as
  read-only and closed to the network), as `convert_model` already did. A client may read a missing hint as its
  default, and some directories refuse a tool that leaves one out.
- A tall print rebuilt at a heavier tower than placement found room for kept the 3 mm brim placement squeezed an
  auto-brim tower to, not the heavier tower's 10 mm, so check 14 refused a printable file (and took back that
  printer's earlier file). It keeps the 10 mm.
- The checks cached each source's paint and sizes, and each printer's template, by path alone. The MCP server
  runs as one process for hours, so a source saved again, or a template rebuilt after a slicer update, was
  checked against its old self and a correct file could fail. The caches now see a changed file.
- A Snapmaker U1 file that fails partway through being written leaves no `partial - …` file behind, and takes
  back SlicerBridge's earlier file for it, as the other engines do.
- The stray `uv.lock` at the repository's root is gone: nothing used it. The plugin's own lock stays.
- Snapmaker Orca 2.4.1's command line slices Gatefang's U1 file, which 2.4.0's crashed on (exit -11) and
  still does. The docs say so.
- A setting Snapmaker Orca won't load is found anywhere in its log, not only in the last six lines check 13
  shows, so the U1's file is written again with the template's value instead of refused. Check 13's result is
  kept as what happened (exit status, crash, refused settings, each plate's G-code facts) and worded only when
  it's printed.
- A Prusa printer that is refused or fails partway takes back SlicerBridge's earlier files for it and leaves no
  `partial - …` file, and an OrcaSlicer-family printer that fails partway leaves no `partial - …` file either.
  The three engines land a file, move one they didn't write to `_previous/`, and take back their own with one
  module (`output.py`), where each had its own copy.
- The U1's file is read back in Snapmaker Orca whenever it's installed, not only with `--slice`: it loads the
  U1 template's cube with the file's settings and saves it again (about 2 seconds), and a carried setting it
  won't load keeps the template's value. One the file can't do without (the template's, the tall tower's) is a
  refusal. The three engines read what a slicer says it won't load with one helper (`refused_settings`).
- The U1's file takes a sliced source's palette from its project settings, as the other engines and the checks
  do, not from `slice_info.config`, which lists the colors as they were when it was sliced.
- [The checks](docs/checks.md#what-the-checks-share-with-the-engines) say which of them share the engine's
  tower geometry: check 13, slicing the file, is the one that measures the tower independently. CI now runs the
  orca engine's write path, read-back and tall-tower rebuild, with a stand-in for OrcaSlicer.