Skip to content

v0.3.5 — the pass that never ran

Choose a tag to compare

@devclone20 devclone20 released this 31 Jul 23:49
· 21 commits to main since this release

⬇️ The download

CLONE-FRAME-HUB-0.3.5.zip — unzip it, double-click install.command, and CLONE FRAME HUB
lands in your ~/Applications with the whole program inside the bundle. The folder you
downloaded can then go in the Trash.

If Finder refuses the first double-click that is Gatekeeper, not a broken file: right-click
install.commandOpenOpen, once. START HERE.txt in the zip says the same.

clone-frame-hub-0.3.5.html is also attached, for anyone who only wants to read the app
file. It is byte-identical to index.html in the repository, and it is not installable on
its own — the app needs its local daemon to touch your machine at all, and that is what the
zip carries.


A fix to v0.3.4,
found by re-reading yesterday's own change instead of trusting it.

One of the three reap passes had never run

When you close an iT window, 0.3.4 ends its shells three ways. The third covers the
workspaces you restored but never opened — no terminal on screen, because iT builds a
workspace the first time you visit it, yet their shells are real and still running from
before your last reload.

That pass was guarded on a flag meaning this window owns the saved layout. The flag is
cleared by the first statement of the same function. So by the time the third pass
looked, it was always false. It never ran once since it was written.

It reviewed correctly and it tested green, because the test pinned the line:

assert.match(dispose, /if\(primary&&!w\.grid&&w\.spec\)specPsids/)

A line cannot see what ran before it. The test now pins the order, and was watched
failing against the bytes v0.3.4 shipped.

Measured on the fix, against a real daemon: three workspaces saved, page reloaded, iT
reopened as the layout owner — three restored, one terminal on screen, three live shells.
Closed the window: nothing left, including the two with no terminal at all.

If you only ever use the workspaces you can see, v0.3.4 already reaped them. This
closes the case where you had parked work in a workspace and had not been back to it yet.

Also corrected

  • The curriculum the agent reads claimed "27 panels" in two places while its own
    generated table listed 20 — and the same wrong number sat in the daemon's app-control
    header and in the extension. There are 20. Every claim says so now, and the
    generated docs were rebuilt from the code rather than hand-edited.
  • open_panel's description in the curriculum now states the one-window rule, which the
    extension already carried and the curriculum did not.
  • Two comments in the browser panel still described a second ⧉ window.

Why a new version instead of replacing v0.3.4's file

v0.3.4 publishes a sha256 and tells you to check it. Someone may already have downloaded
that file. Swapping it silently would make the number on that page a lie, so this is its
own release.


sha256  fc234feb88219b6e01d5660decc94e37b89567aa9ee1b910aaca25aa2a8df975

shasum -a 256 index.html must print that line. 923 tests pass upstream.