v0.3.8 — the audit's six

⬇️ The download

CLONE-FRAME-HUB-0.3.8.zip — unzip, double-click install.command. Updating: Trash the old app, run this
installer. Your data lives in ~/CloneFrame and ~/.clone-frame-hub, never inside the app.

---

An adversarial audit read this release from six angles — the download path, the release zip,
the installer, the window model, the iT close path, and every checkable claim in the
published docs — and confirmed 33 findings out of 40 examined. This release closes the six
that cost you something, including a blocker introduced two versions ago, and the
documentation that sent you to screens that were demolished.

A parked BROWSER could vanish with no square to bring it back

Dock BROWSER. Close it with its ✕. Reopen it from anywhere that is not its square. Dock it
again — and the window hid behind a square that was never actually created. No icon on
the canvas, nothing to click, nothing written to disk. Your pages were still loaded, still
using memory, and completely unreachable.

v0.3.6 taught the frame to refuse duplicate squares. That was right. The code that docks a
window never read the refusal. Reproduced against the published v0.3.7 build, driving the
real interface, before a line was changed:

ghost cell  6,8 → research      a key to a hidden window, on a square with no tile

If there is nowhere to put a window now, it folds in place where you can still see it,
rather than disappearing.

Five more that were costing you something

• it was broken in every installed copy. The shim the daemon writes carried a
  percent-encoded path, so inside CLONE FRAME HUB.app — two spaces in the name — it
  pointed at a file that does not exist. Latent for years in a developer's checkout, and
  guaranteed from the moment the installer began putting the daemon inside a bundle.
• The uninstaller was not in the app, while the installer told you, in consecutive
  lines, to run it and to Trash the folder holding it. It now travels with the app, and a
  copy lands in ~/Applications where you will find it.
• The uninstaller killed whatever held port 8765 — a dev server, a tunnel, anything —
  while its own comment claimed it only ever stopped the HUB. It now checks.
• Removing one frame square could close a window another square still pointed at,
  taking your CODE session and every agent running in it.
• Closing an iT workspace you had restored but never opened left its shells running,
  with nothing left that could ever name them.
• ⌘T / ⌘L / ⌘F kept reaching a browser you had just parked, invisibly.

The front door pointed at rooms that had been demolished

docs/CONNECT.md — the guide the README sends you to — told you to open CLI ECONOMY OS
to connect a wallet, and to install EXO LAB from an INTEGRATIONS tab. None of those
exist. Wallet sign-in is the button in the header (and MY AGENTS → Connect wallet); the
local cluster is MATRIX, one of the four top-bar rooms. HOW-IT-WORKS.md gave both
demolished rooms a full guided tour.

All retargeted at what shipped. The tools that were never bundled are now marked as a design
note instead of instructions. ARCHITECTURE.md's terminal-session cap corrected from 12 to
the real 24.

Not in this release: roughly twenty smaller documentation findings from the same audit —
a stale BYOK-storage claim in SECURITY.md, a catastrophic-guard promise the live terminal
does not keep, a bundled-integrations table in the README, a token-lifetime claim in
INSTALL.md. They are listed rather than quietly dropped, and they are next.

---

sha256  e842392f1535348b5cb261158988a9b575f549157eb4f4a6be6b9498fcdd708c

929 tests pass upstream.