v0.3.1 — a friendlier way in

Executor File v0.3.1 — a friendlier way in

The point of this release: you no longer need a terminal editor to build or maintain your register. Everything from v0.3.0 stays; this adds a humane editing path and smooths the first-run rough edges the first real dry run exposed.

What's new since v0.3.0

• Browser register editor (web/editor.html, double-click Edit-Executor-File.command or run scripts/edit.sh): fill your register in as a form with dropdowns and plain-English help. No YAML, no terminal editor. It runs entirely in your browser on your own machine: no server, no network, nothing sent anywhere. Holds pointers only.
• Review in the browser: scripts/review.sh now opens that same editor by default for a non-technical owner, keeping its decrypt then same-passphrase re-encrypt then verify then shred flow, so your holders' shares stay valid. Power users who have set $EDITOR keep it; force either with EXECUTOR_FILE_EDIT=browser|terminal.
• Any register opens: the editor's loader now reads folded/literal block scalars, so hand-authored and example-style files load, not only editor-made ones.
• README "Get the tool" section: download, unpack, and open a Terminal in the right folder, written for someone who has never cloned a repo.

What's verified, and what isn't (unchanged honesty)

Machine-verified, green at tag time: 116 scripted tests on macOS and Ubuntu CI under both encryption mechanisms; the browser editor's output was checked against both validator tiers; the new review bridge is covered by a deterministic end-to-end test; and this exact tarball was unpacked clean and exercised (validate, render, seal, edit-server) before release.

Still pending, by design: the two human gates in RELEASE-CHECKLIST.md — a Windows dry run by a non-author and a physical fire drill with real printed shares — remain open. This release, like v0.3.0, ships ahead of them by deliberate owner decision (pre-launch, live testing). The Mac/Linux path is CI-proven; treat the printed Windows sheet as carefully written but not yet field-tested.

Still a terminal step

Sealing a brand-new register (scripts/setup.sh) still needs one Terminal command. Creating and maintaining the register's content are now terminal-free; the one-time encrypt-and-split is the last wall (tracked as EF-ISS-7).

Tool versions tested

age 1.3.1 (batchpass) and age 1.1.x (stock interactive, Ubuntu CI); ssss 0.5.

Checksum

d67e2f90fdfbe84fabb98c901053df6efdd89edcd4dc543666f8a2c8f2fa4bb2  executor-file-v0.3.1.tar.gz