6 Commits

Include renames

Author	SHA1	Message	Date
jochen	cfe1dffa45	zsh: let a machine withhold node-login-shell's execute ... execute runs any command as the operator account, which can become root without a person. The operator withholds it on the control-node until a call needs a person's approval (hq ADR 0268); the other machines keep it for now. The setting execute (serve by default) is written into a root-owned file the tools bundle reads at start, and anything but serve withholds the verb, so the machine's runtime does not offer it.	2026-10-09 00:10:28 +02:00
jochen	328d90fb88	zsh: keep each PATH directory once ... Every nested shell, and every sourced file that prepends, added the same directories again; a workstation's PATH carried each of several entries three times. typeset -U in the .zshenv block applies to every zsh.	2026-10-04 11:34:36 +02:00
jochen	5fd0f72221	zsh: save history and initialise completion ... zsh saves no history by default (SAVEHIST=0) and nothing called compinit, so every machine had 30 lines of unsaved history and only basic completion. Found reviewing the shell on its first machine (hq to-be 41).	2026-10-04 11:33:17 +02:00
jochen	42c80fa9e1	zsh: no doubled blank line in the block when the first slot is empty	2026-10-04 04:05:30 +02:00
jochen	566739e02c	zsh: hold the mesh's login-shell seat, source the environment, and leave the rest to slots ... The seat is now the mesh's node-login-shell, which a shell module claims rather than declares (novox/hq ADR 0204), and the environment is one module's that every module contributes to (ADR 0203). Per hq to-be 41 WP3: - no seat declaration; the claim is node-login-shell serving execute; - EDITOR, VISUAL, XDG_CONFIG_HOME and the three PATH entries are an environment contribution, not exports in the block; - a ~/.zshenv block sources ~/.config/mesh/environment.sh, so a script, a login and execute all see the environment; - the ~/.zshrc block goes at the start, so the operator's lines run after it, and holds today's shared defaults between the first, normal and last slots. The prompt, the plugins and the operator's own lines are no longer in it; - execute is bounded below the runtime's call limit (20 s default, 25 s at most), kills its whole process group on timeout, cuts each stream at 256 KiB and says so, runs in the account's home without the mesh's words, with the account's session words. The dead runuser branch is gone, because the runtime is the account; - zsh_config shows both files with their block line counts; - the README lists the one-off migration (ADR 0182).	2026-10-04 04:02:54 +02:00
jochen	5548b0f4e9	zsh: the shell as a module — package, the mesh's ~/.zshrc block, the login-shell seat and execute ... The first module of the operator's environment (novox/hq to-be 37 §1, ADR 0173, 0176). A package, the mesh's default configuration as a block inside the account's ~/.zshrc so the operator's own lines around it survive every push (ADR 0174 as the host's `into: block` realises it), a `user` shape that makes zsh the account's login shell, the `login-shell` seat declared with its one verb, and a tools bundle: `execute` under the seat's name, `zsh_config` under the module's. No container, no process: the tools are served by the node tools runtime (ADR 0175), which does not exist yet — the bundle builds and the manifest registers ahead of it. `module check` passes; the tools type-check against the SDK. Two things the manifest cannot yet say, left for the controller: the `user` shape applies wherever the module is assigned, not only where it holds the seat; and the runtime learns the account from MESH_OPERATOR_ACCOUNT, which nothing sets yet.	2026-10-04 02:32:34 +02:00