feat: local browser-based register editor (addresses the nano/editing wall, EF-ISS-4)

UAT dry run proved a non-technical owner cannot edit estate.yaml in a
terminal editor (nano was a hard wall) — the dry-run evidence SPEC-v1
§9 said the parked GUI decision was waiting for. First response:

- web/editor.html — a single, local, dependency-free page: fill the
  register as a form (dropdowns for every enum, plain-English help,
  auto IDs, contacts + documents), Save writes a valid estate.yaml.
  Runs entirely in the browser: no server, no network, nothing sent
  anywhere; holds pointers only. Best-effort loader re-opens a register
  the tool emitted, for editing.
- scripts/edit.sh + double-clickable Edit-Executor-File.command to open
  it without touching the terminal.
- README points owners to it as the no-YAML path.

The generated YAML was tested against BOTH validator tiers (baseline
awk + strict Python/JSON-Schema) with apostrophes, unknown dates,
depends_on, transfer/beneficiary, closed assets, contacts and
documents — passes clean. Sealing (setup.sh) still uses one Terminal
command for now; that wall is the next target.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: TheWayWithin

Edit-Executor-File.command

@@ -0,0 +1,4 @@
+#!/bin/sh
+# Double-click me (macOS) to fill in your Executor File as a browser form.
+cd "$(dirname "$0")" || exit 1
+exec scripts/edit.sh

ISSUES.md

@@ -0,0 +1,27 @@
+# executor-file — Issue & Project Register
+
+**This is the single source of truth for what is open in this repo.** One row per
+issue/project. Detail lives in the linked doc; this file is the index the Mission
+Control reconcile (`repo-reconcile.py`) reads and mirrors to the cockpit.
+
+## ID convention (collision-safe)
+
+Mission Control owns the bare `ISS-`/`PRJ-`/`T-` namespaces. **Every executor-file ID
+carries the `EF-` prefix** so it can never collide with a Mission-Control-native
+ID or another repo's. Raise issues here with `python3 ~/shared/scripts/repo-issue.py`.
+
+---
+
+## Open
+
+| ID | Title | Status | Severity | Detail | MC-SYNC |
+|----|-------|--------|----------|--------|---------|
+| EF-ISS-4 | Editing the register in a terminal editor (nano) is a hard wall for non-technical owners: dry-run tester could not use nano, accidental ^V wrote junk, could not exit. This is the dry-run evidence the parked GUI/editing-interface decision (SPEC-v1 §9) was explicitly waiting for. Needs a humane edit path (GUI or form/web editor) before the tool is usable by its target audience. | Open | critical | — | pending |
+| EF-ISS-3 | Onboarding requires holding instructions across multiple pages — violates the product's own 'you don't have to hold it in your head' principle; non-technical owners should be funnelled to executorfile.com/get-started, not raw GitHub | Open | high | — | pending |
+| EF-ISS-2 | GitHub release page is a dead-end for non-technical users: no 'download this / do this next', assets collapsed under Assets, and competing with GitHub's auto Source-code downloads; install instructions are stranded back on the README (can't be recalled on the release page) | Open | high | — | pending |
+| EF-ISS-1 | README quickstart assumes the repo is already on disk: no download/unpack/cd step for tarball users | Open | low | — | pending |
+
+## Recently closed
+
+| ID | Title | Status | Commit | Detail |
+|----|-------|--------|--------|--------|

README.md

@@ -58,6 +58,8 @@ cd executor-file
 
 Either way you are now "in the folder" — every command below is typed into that same Terminal window, and the `scripts/...` paths will just work.
 
+**Prefer not to hand-edit a text file?** Double-click **`Edit-Executor-File.command`** in the folder (or run `scripts/edit.sh`) to fill your register in as a form in your browser — dropdowns, plain-English help, no YAML. It runs entirely on your machine, saves `estate.yaml` to your Downloads, and you still seal it once with `scripts/setup.sh`.
+
 **Two small tools to install once** (these do the encryption and the share-splitting; both are free, open-source, and standard):
 
 ```bash

scripts/edit.sh

@@ -0,0 +1,19 @@
+#!/bin/sh
+# edit.sh — open the friendly register editor in your web browser.
+#
+# Fill your register in as a form (dropdowns, plain-English help) instead
+# of hand-editing YAML. It runs entirely in your browser on this machine:
+# no server, no network, nothing sent anywhere. When you click Save it
+# writes estate.yaml to your Downloads folder; then seal it once with
+# scripts/setup.sh.
+#
+# Usage:  scripts/edit.sh
+set -u
+DIR=$(cd "$(dirname "$0")/.." && pwd)
+PAGE="$DIR/web/editor.html"
+[ -f "$PAGE" ] || { echo "error: editor not found at $PAGE" >&2; exit 1; }
+echo "Opening the register editor in your browser…"
+echo "  (it runs locally — nothing you type is sent anywhere)"
+if command -v open >/dev/null 2>&1; then open "$PAGE"
+elif command -v xdg-open >/dev/null 2>&1; then xdg-open "$PAGE"
+else echo "Open this file in your browser: $PAGE"; fi