b55a35f9

test: e2e — every wall on a terminal gets a hosts file of its own

a73x   2026-08-28 19:53

test: e2e — every wall on a terminal gets a hosts file of its own

The suite's shared `$XDG_STATE_HOME` is now a WALL: every `mux TARGET`
records the daemon it attached to, and every `mux` on a terminal opens on
every line it finds. By group 03 that file is a dozen daemons, all but
one of them stopped, so a pty leg's own tile arrived under a screenful of
`[unreachable]` stripes and the geometry it asserted was somebody else's.

`hostroom NAME` (e2e_lib.sh) spells a private state home for one leg, and
every pty leg that runs `mux` passes it. Per LEG and not per group: within
a group the earlier legs' daemons are stopped by the time the later ones
run, which is the same problem one scope in.

Three consequences of the model that the legs had to be told about:

  * a leg that asserts the DEFAULT cut removes any saved tree first. A
    wall on a terminal saves its tree on the way out, so a second
    ptyclient run in the same state home restores the first one's — and
    the aspect rule only applies when nothing is saved.
  * `exit` in the focused tile ends `mux` only when that tile was the
    wall. A daemon always holds its own default session, so a leg that
    named a second one has two tiles and leaves by chord instead; the
    legs whose daemon has exactly one session keep asserting the other
    half of the rule.
  * scenario 09's wall runs at 80 columns, not 100: the aspect rule cuts
    four stripes BESIDE at 100x44, twenty columns each, and `labelText`
    spends a narrow bar on the state word — the socket path those
    assertions grep for is the first thing to go.

`make e2e`: 81 scenarios, 37 convergence points, green.