Bump to 0.6.33 — one version per app in the shared OTP root (MOB-143) (#60)

The OTP root is keyed by OTP hash rather than by project, so every app on the
machine shares one lib/. Installing a dependency without removing its other
versions left them side by side, and the code server resolves an application to
the highest version it finds there — while the app's own beams come from its
lock. An app locking exqlite 0.38.0 loaded 0.38.0's beams and 0.40.0's
sqlite3_nif.so, on_load failed with bad_lib, every database connection died and
the boot never reached a root screen. The visible error blamed database
credentials.

Non-local too: an app that built fine yesterday broke because a different app
upgraded a dependency. Three of four local projects were already mismatched.

pythonx always swept by wildcard and never had this. exqlite, emlx and the
generic installer removed only a malformed empty-version dir and let real
versions accumulate. All four now sweep, keep the target, and log removals.

The first native build after upgrading may report removing stale versions.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: GenericJam

CHANGELOG.md

@@ -10,6 +10,32 @@ Full module documentation: [hexdocs.pm/mob_dev](https://hexdocs.pm/mob_dev).
 
 ## [Unreleased]
 
+## [0.6.33] - 2026-09-04
+
+### Fixed
+- **The shared OTP root keeps one version of an app, not every version it has
+  ever seen** (MOB-143). The root is keyed by OTP hash rather than by project,
+  so every app on the machine shares one `lib/`. Installing a dependency
+  without removing its other versions left them side by side, and the code
+  server resolves an application to the **highest** version it finds there.
+
+  That splits an app in half. Its beams come from its own `mix.lock` and are
+  pushed to the device; `code:lib_dir/1` — and so `code:priv_dir/1`, which is
+  where `load_nif` looks — resolves against the shared directory. An app
+  locking exqlite 0.38.0 would load 0.38.0's beams and 0.40.0's
+  `sqlite3_nif.so`, and `on_load` would fail with `bad_lib`, taking down every
+  database connection and the boot with it. The visible error talked about
+  database credentials and said nothing about a cached artifact.
+
+  It was also **non-local**: an app that built fine yesterday broke because a
+  *different* app upgraded a dependency. `pythonx` always swept by wildcard and
+  never had this; `exqlite`, `emlx` and the generic installer removed only a
+  malformed empty-version directory and let real versions accumulate.
+
+  All four install paths now sweep other versions, keep the target, and log
+  what they removed. A stale version left by an earlier build is cleaned on the
+  next native build, so the first build after upgrading may report removals.
+
 ## [0.6.32] - 2026-08-31
 
 ### Fixed

mix.exs

@@ -4,7 +4,7 @@ defmodule MobDev.MixProject do
   def project do
     [
       app: :mob_dev,
-      version: "0.6.32",
+      version: "0.6.33",
       elixir: "~> 1.19",
       description: "Development tooling for the Mob mobile framework",
       source_url: "https://github.com/genericjam/mob_dev",