the commander file panel could list a directory and not open anything in it. it
already mounts the same `FileBrowserApp` as /files — what it did not mount is the
VIEWER, which on /files is a separate ephemeral panel and not part of the browser
at all.
THE PARAM COULD NOT BE READ, which is why this is more than mounting a panel. on
/files the folder is in the PATHNAME, so `?view=notes.md` is a name inside it and
that is all it needs to be. a browser mounted anywhere else keeps its folder in
panel-local state, so the same name is unresolvable by anything except the
component that wrote it — the commander panel was writing `?view=notes.md` with
no reader able to tell which of its folders that meant.
so off the files route the param carries the whole path, and `viewRoot` with it:
a panel that overrides the root is exactly the case where "home" is the wrong
guess. `viewRoot` joins VIEWER_PARAMS so closing an overlay clears it — a stale
root outliving its view would send the next file to the wrong tree.
the split is VERTICAL where /files is horizontal. this panel is already the narrow
half of a screen whose other half is a transcript; splitting it sideways again
leaves two columns too thin to read anything in.
closing the file clears the overlay params by NAME rather than resetting the
query, because `files=1` — the thing keeping this whole panel open — lives in the
same string, and the obvious version closes the browser along with the file.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
pastilhasandClaude Opus 5
15392ae6c2