# OrbitHub

## Release checklist

Every release (new tag + build + publish) must include:

- **Update `README.md`** to match current reality before tagging:
  latest published release version/link, the Implemented Features list
  (add/adjust bullets for anything shipped since the last release), and
  any status notes (e.g. VNC/Apple-auth caveats) that changed.
- Update `docs/PROGRESS.md` with a bullet describing what shipped.
- Bump the version in `CMakeLists.txt`.
- Build and test all reachable platforms (Linux local, Windows and macOS
  over SSH — see prior release commits/sessions for the build scripts
  used) before publishing.

`docs/USER_GUIDE.md` (in-app `Help -> User Guide` and the release PDF)
should also be checked for drift when a change affects user-facing
behavior, though it doesn't need a pass on every single release the way
README.md does.