Skip to content

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 06:14
· 31 commits to main since this release

Added

  • Version-skew marker in the TUI status bar (#852). While
    the daemon's version and the client's differ, the workspaces
    status line carries a warning-colored marker after the URL
    naming both versions (msksd 1.2.3 ≠ client 1.2.4); the
    CLI's one-line notice with its remedy keeps its own behavior.
    The marker refreshes on the listing's five-second reload, a
    /health connection that fails leaves the standing marker in place,
    and the marker leaves when the versions agree. The URL and the
    state summary crop before the marker does, so the marker stays
    visible at 80 columns.

  • Open-shell counts in the TUI (#858). Every interactive
    msks ssh writes a heartbeat session record under
    ~/.local/state/msks/sessions (relocatable with the state_dir
    key / MSKSC_STATE_DIR), and the workspaces list shows the live
    count beside a row's status word (»2) and on the detail strip
    (shells »2); the workspace page's header carries the count
    beside the status (2 shells open). The count covers the shells
    open on the host the TUI runs on, survives a tree restart, and a
    session killed without cleanup stops counting about twenty
    seconds after its death. Windows the tree opens carry the
    workspace's name and the session record's five-character token in
    their title (msks tree-vm f8x2n); a later release will use the
    token to match a session to its window.

  • Detail strip at the bottom of the workspaces list (#849).
    A two-line strip renders at the bottom of the listing's box
    and carries the focused workspace's quick facts: name, id,
    image, cpu count, memory, egress mode, the mounts-issue count,
    and the storage the workspace charges the state disk (the same
    root-plus-home cost msks storage reports). The strip follows
    the selection and refreshes on the list's standing cadence;
    the storage figure uses a cached capacity report, so moving
    the selection costs no roundtrip. An empty list hides the
    strip.

  • State summary in the TUI status bar (#853). The workspaces
    count now carries a summary of the fleet's states:
    4 workspaces · all stopped when every row holds one state,
    or each state's count (4 workspaces · 1 running 3 stopped)
    when they mix. The summary follows the standing five-second
    refresh. The daemon's URL comes after the summary, and it crops
    first when the terminal runs narrow.

  • ? key overlay in the TUI (#851). Every page of the tree
    answers ? with an overlay listing that page's bindings,
    hidden ones included (the escape leaves among them), each with
    its action label. Any key closes the overlay. The footer stays
    as it was. The overlay is where the full key list lives.

  • Sortable listing columns in the TUI (#854). Clicking a column
    header in the workspaces list sorts by that column; clicking the
    active header flips the direction, and the arrow in the header
    shows the active sort. CREATED sorts by creation date (newest
    first by default), STATUS in lifecycle order, the other columns
    by their text. You sort by clicking a header; the keymap stays
    as it was, and the sort holds across the standing refresh.

  • Agent reference card (#842). msks agent-card prints the agent
    reference card: one markdown text grouped by task (read state,
    lifecycle, run inside, egress consent) with the status vocabulary
    and the exit-code table whole. The same text is the
    Agent Reference Card
    docs chapter. The card covers the status vocabulary, the exit-code
    table, and the non-interactive egress-consent flow.

  • Machine-readable CLI (#841). Every printing msks command takes
    --json: the mutating commands emit the affected workspace row as one
    JSON document (create, clone, start, stop, resize, mount,
    umount; rm prints one JSON line per removed id), the read commands
    emit their documents, and failures print
    {"error": {"status": ..., "detail": ...}} on stderr. The exit codes
    are a documented table (docs/cli.md): 3 not found, 4 name conflict,
    5 wrong state. msksd doctor --json prints its check rows as one
    document. Human output is unchanged.

  • host.msks (#816). Every egress workspace's resolver answers the
    name with its own tap address, so a guest connects to the gateway by name
    (https://host.msks:8660 with a -R 8660:localhost:8660 proxy stored)
    instead of discovering it through ip route show default. The name
    answers in every consent mode, feeds no policy row or address pin, and
    a well-formed internet-class query for it is never sent upstream.

  • The proxies docs chapter (#814). docs/proxies.md owns the whole
    proxies story in one place: the persistent proxy port concept, the
    -L/-R directions in ssh's grammar, the live status vocabulary, and
    worked examples for both the CLI and the TUI. The networking, CLI, and
    TUI chapters link to it where they introduce proxies.

  • The TUI's proxies page (#809, part of #807). Each workspace's
    page opens its own proxies page (the action row, or p), which adds
    and removes that workspace's persisted -L/-R proxies with the
    same spec grammar msks proxy add reads, and shows live status —
    refreshed on every proxy transition the daemon publishes beside a
    five-second standing re-read. The workspace page carries a compact
    port-pair line (8888 -> 8889 | 8881 <- 8882), each pair green
    while it listens and red while its bind refused.

  • msks proxy (#808). A new command manages the daemon's
    persisted workspace proxies: add with ssh's own spec shape
    (-L [BIND:]PORT:HOST:PORT binds the daemon host and bridges to
    the workspace; -R RPORT:HOST:TPORT binds the workspace's
    gateway and bridges to a daemon-side service), ls with live
    status, and rm. The daemon owns every listener, rows live in its
    database, every workspace start re-establishes them, and add
    is idempotent for an identical spec. Part of #807.

Changed

  • The workspaces list's ID column (#849). The EGRESS column
    became an ID column: each row carries its immutable workspace
    id. The egress posture reads on the detail strip instead,
    beside the row's other facts. Clicking the ID header sorts by
    the id itself; the NAME header keeps the name sort.

  • Graded status colors in the TUI listing (#850). The
    workspaces list colors the status column by state class:
    running keeps the success color, stopped and created
    render in the muted text color, starting, stopping, and
    paused in the warning color, and absent and unknown in
    the error color. A fleet at rest reads calm. The transitional,
    paused, or lost row is the one the eye finds. The ✗N mounts-issue
    marker keeps the warning color beside whatever color the
    status word takes.

  • The arm64 stop caveat is documented (#826). cloud-hypervisor's
    arm64 power button (the PL061 gpio key) delivers only the first
    press, so a msks stop cannot rescue a lost press by re-pressing.
    The fallback kill at the MSKSD_SHUTDOWN_TIMEOUT_S deadline carries
    the stop instead. Size that setting to cover the guest's slowest
    clean shutdown. A value above 120s outlives the client's wait, and
    the client reports a timeout while the daemon still finishes the
    stop.

Breaking

  • terminal_title / MSKSC_TERMINAL_TITLE removed (#858). The
    window title template setting is gone; every terminal window msks
    opens for a workspace shell now carries one fixed title,
    msks <workspace-name> <token>, and windows msks does not open keep
    the terminal emulator's own title. The client refuses a config
    file that still carries the terminal_title key, on every
    command, until the key is deleted — delete it from your
    msks.yaml and unset the variable. The refusal names the key.

Fixed

  • The legacy create default cmdline (#833). A create with
    explicit kernel/rootfs paths and no cmdline now boots with
    this host's console device in the default: ttyAMA0 on an
    aarch64 daemon, ttyS0 elsewhere. The console answers on
    both; the catalog-record path was already per-arch and is
    unchanged.

  • msks doctor qemu-kvm apk hint (#832). The hint now
    prints this host's Alpine emulator package:
    qemu-system-aarch64 on an aarch64 host,
    qemu-system-x86_64 elsewhere.

  • msks doctor cloud-hypervisor install hint (#831). The
    hint now prints this host's release assets: the -aarch64
    builds on an aarch64 host, the unsuffixed x86-64 builds
    elsewhere. The installation chapter states the same
    architecture distinction beside its install block, and
    installs ch-remote under the unsuffixed command name the
    demo and dev tooling calls.

  • Egress slice release on a failed teardown (#828). A detach
    whose table or tap delete raised left the workspace's slice
    claimed with no retry path, so the next msks start was refused
    with "held by another live workspace" until the daemon
    restarted. A failed teardown now leaves a record the
    workspace's next stop or start retries, and the slice releases
    when that retry completes.

  • Workspace starts after a guest-initiated poweroff (#825). A
    VMM that exited outside the stop flow — the guest's own poweroff,
    or a guest landing its shutdown just past a stop deadline — left a
    stale entry that refused every later msks start with "VM already
    exists" until an operator passed a stop. The start now reconciles
    the dead VMM's residue (its tracked entry, share daemons, and tap)
    and boots.

  • Fedora guest's sshd address-wait wiring (#819). The Fedora
    image's sshd ordering dropin now lands in sshd.service.d (Fedora's
    own unit names) instead of Debian's ssh.service.d, so
    msks-wait-address.service actually runs on a Fedora egress
    workspace and sshd listens once the NIC has its address. The image
    build fails when the wiring names a unit the image does not ship.

  • The NixOS guest's arch-dependent module set (#821). The
    runtime module list and the nested-KVM unit's modprobe line now
    follow the evaluating architecture: aarch64 loads crc32c-generic
    and the gpio_keys power-button driver and probes the plain kvm
    module; x86_64 keeps crc32c-intel and the kvm-intel/kvm-amd
    pair. An aarch64 NixOS workspace now exposes /dev/kvm on hosts
    that pass nested virtualization, and stop runs through the
    guest's own shutdown. The image build pins the split per arch.

  • The console's first prompt carries the workspace's name
    (#818).
    Both guests' console getty now orders after
    cloud-init-network.service, the cloud-init stage that sets
    the seed's hostname, so the first prompt and an interactive
    root session's $HOSTNAME show the workspace's name instead of
    the image default msks-guest. The image builds now fail when
    a systemd dropin names a unit the image does not ship — the
    same dead-ordering class #819 fixed by hand, caught here for
    every dropin the images carry.

  • scripts/cut-release.sh (#805). One command pushes a
    release cut in the order the docs deploy needs: the tag alone
    first, then main once the tag's versioned docs deploy has
    finished green. Pushing the tag and main together races the
    docs workflow's concurrency group, and the release publishes
    without its versioned docs and the site's latest alias keeps
    the previous version until the cancelled run is re-run by hand.

What's Changed

  • Sequence the release cut's pushes behind the docs deploy (#805) by @mcdonc in #806
  • Make the listing's focus-walk test converge from a settled startup (#811) by @mcdonc in #812
  • Workspace proxies: daemon fundamentals, persistence, and CLI (#808) by @mcdonc in #810
  • Workspace proxies: TUI management page (#809) by @mcdonc in #813
  • Docs: the proxies chapter (#814) by @mcdonc in #815
  • A DNS name for each workspace's tap gateway (#816) by @mcdonc in #817
  • Fix the Fedora guest's sshd address-wait unit names (#819) by @mcdonc in #823
  • Split the NixOS guest module set by arch (#821) by @mcdonc in #822
  • Reconcile a self-exited VMM at launch (#825) by @mcdonc in #827
  • Order the console getty behind cloud-init's hostname stage (#818) by @mcdonc in #824
  • Document the arm64 stop caveat: the PL061 pulse is one-way (#826) by @mcdonc in #829
  • Release the egress slice when a detach teardown raises (#828) by @mcdonc in #830
  • Doctor's cloud-hypervisor hint names this host's release assets (#831) by @mcdonc in #834
  • Doctor's qemu-kvm apk hint names this host's emulator package (#832) by @mcdonc in #836
  • The legacy default cmdline names this host's console device (#833) by @mcdonc in #839
  • The paced seed tests keep their budget on a loaded runner (#838) by @mcdonc in #845
  • Remove the FIPS-readiness rules from AGENTS.md (#835) by @mcdonc in #846
  • Machine-readable CLI: --json everywhere, structured errors, exit codes (#841) by @mcdonc in #847
  • Ship an agent reference card for harnesses operating msks (#842) by @mcdonc in #848
  • Sortable columns in the workspace listing (#854) by @mcdonc in #855
  • Grade the TUI listing's status colors by state (#850) by @mcdonc in #860
  • A ? help overlay listing each screen's bindings (#851) by @mcdonc in #861
  • A state summary beside the workspace count in the TUI (#853) by @mcdonc in #862
  • Gate: cap Python modules at 2000 lines (#863) by @mcdonc in #865
  • Add a detail strip under the TUI workspace list (#849) by @mcdonc in #864
  • Count open shells per workspace from msks ssh session records (#858) by @mcdonc in #868
  • Document Konsole's tab title format beside the msks window title (#869) by @mcdonc in #870
  • Show daemon version drift in the TUI status line (#852) by @mcdonc in #871
  • Replace "ride" and "dial" with plain language in docs (#872) by @mcdonc in #873

Full Changelog: v0.8.3...v0.9.0