Ship to Desktop and /Applications; restructure Settings; add reset

Version pinned to 0.0.1 and staying on 0.x while this is in beta.

`npm run ship` now exports twice from one build: /Applications/Work.app
to test here, and ~/Desktop/Work-<version>.zip to send someone. One
build, so a tester runs byte for byte what was verified rather than a
second build that drifted. Packed with ditto rather than zip - a plain
zip mangles the bundle's symlinks and it will not open on the far end.

Settings: groups move up under apps, and the hidden-element list moves
into its own window behind a one-line summary. It had grown to 21
selectors of framework class names and was most of the page, in front of
the things people actually open Settings for.

Reset puts apps, groups, hidden elements and zoom back to defaults, and
leaves sessions alone - those live in WebKit's own store, and throwing
them away would mean signing back into every tool to undo a change to
the nav.
This commit is contained in:
2026-09-01 16:04:54 +02:00
parent 07bb22eb2d
commit 2a0b934d04
11 changed files with 210 additions and 101 deletions
+12 -1
View File
@@ -98,7 +98,18 @@ Build, replace the copy in `/Applications`, and relaunch — one command:
npm run ship
```
No disk image; nothing here is being distributed.
One build, two destinations, every time:
- `/Applications/Work.app` — the copy tested here
- `~/Desktop/Work-<version>.zip` — the copy to send someone else
Both come from the same build, so a tester runs byte for byte what was just verified
rather than a second build that drifted. The zip is made with `ditto`, not `zip`: a plain
zip mangles the bundle's symlinks and the app will not open on the other machine.
The app is ad-hoc signed, so the first launch on someone else's Mac needs
**right-click → Open** rather than a double-click. Gatekeeper refuses it silently
otherwise.
## Configuration