rehuco-agent 0.1.1

The first release to reach PyPI, so pip install rehuco-agent and uv tool install rehuco-agent now get
the application instead of the 0.0.1 name-reservation stub that had been sitting there. The application
is byte-for-byte what 0.1.0 shipped — no fixes, no new behaviour, and the installers attached here are
rebuilt from the same sources. What is new is the publishing path itself.

Changed

• The PyPI project page now shows a screenshot of the editor, and describes the package's maturity
  without naming a version series that goes stale at the next bump.

rehuco-agent 0.1.0

The first release built from this repository, and the first to ship a working application rather than a
stub — published to exercise the release plumbing end to end rather than because the app is ready to be
depended on. It starts a new minor series because 0.0.0 and 0.0.1 were spent on PyPI name-reservation
stubs that contained no application.

Added

• Edits a resource's details from a .rehu file: title, authors, publisher, release date, URL, durations,
  sizes, rating, level, tags, flags, and a Markdown description.
• Shows a resource's screenshots in a strip beside the fields, with arrow-key and wheel navigation, and
  control over which images the strip shows.
• Converts legacy .tc catalogs to .rehu, keeping backups it can roll back if a conversion goes wrong.
• Leaves unrecognized fields untouched across a save, and opens a file written by a newer format version
  read-only rather than rewriting it.
• Saves atomically, and remembers each file's panel layout between sessions.
• Registers as the .rehu handler on Windows and Linux, from the app or via --register/--unregister;
  --version and --info report the version and the current registration.
• Ships installers for Windows (.msi), macOS (.dmg) and Linux (.AppImage).

Known limitations

• The installers are neither code-signed nor notarized, so Windows SmartScreen and macOS Gatekeeper warn on
  first run and have to be overridden by hand.
• On Windows the packaged executable is a GUI-subsystem binary and prints nothing to a console, so
  --version and --info report through their exit code there; a source checkout prints normally.