v0.0.4 — in-chat workspace, model, and status commands

/cd points a conversation at a directory and /ws lists every workspace the host registry knows, each reachable by bare name — every (conversation × directory) pair owns a durable session, so returning to a directory resumes the context built there. /model use switches this conversation's route from the next message on, with the SAME session resuming context-intact; the catalog comes from the host llm registry. /status reports workspace, route, session, turn activity, pending approvals, and the running version — before a first message exists.

Both mappings persist through the host settings service. workspaceRoots can fence /cd; the filesystem root and home are never accepted.

Fixed: the packed tarball ships lib wholesale (a shared bundler chunk was missing from the enumerated files list and crash-looped installs); a packaging spec now packs the real tarball in pnpm test to keep that class impossible. Plus race hardening around switches (stale-binding self-heal, running-mark cleanup).

v0.0.3 — Linux log relay, lingering, logs verb

systemd units now send the bot's console to ~/.dsh-lark-channel.log instead of the journal, which had left the file empty on Linux — start could never relay the first-run QR code there. start under systemd attempts loginctl enable-linger and says so when lingering stays off. New: dsh-lark-channel logs [-f].

v0.0.2 — one-command deployment

npx dsh-lark-channel start provisions a dedicated profile, runs it in the background under launchd or systemd --user from the first moment, and relays the log to the terminal until the QR scan lands. stop / restart / status manage it afterwards; systems with no supervisor fall back to a foreground run. Unit files carry an explicit PATH, are user-only, escape everything interpolated, and forward environment-supplied Lark credentials. CI now runs typecheck and tests on push and pull request.