msdev 0.10.1__tar.gz → 0.12.0__tar.gz

{msdev-0.10.1 → msdev-0.12.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: msdev
-Version: 0.10.1
+Version: 0.12.0
 Summary: Portable nodes and execution environments for msModelSlim development
 Author: msModelSlim Agent Contributors
 License-Expression: MulanPSL-2.0
@@ -25,16 +25,15 @@ Dynamic: license-file
 
 # msdev
 
-`msdev` manages connection Nodes and execution Envs. A Node owns SSH and its
-per-user `msdevd`; an Env references a Node and adds a host/Docker runtime plus
-optional conda/venv/uv layers.
+`msdev` exposes three capabilities: **`node`** (connect + host agent),
+**`env`** (shared execution context, shell, files), and **`exec`** (commands).
 
-The CLI is intentionally stateless:
+A Node owns SSH reachability and `msdevd` deployment. An Env owns the full
+execution context: host or Docker runtime, conda/venv/uv layers, optional
+`setup` script (root switch, proxy, etc.), command `wrap`, and static env vars.
 
-- Node-scoped NPU/model operations name `--node` or use `--all`;
-- execution names `--env`;
-- no harness conversation binding or implicit current Env exists;
-- MCP is not part of the architecture.
+The CLI is intentionally stateless: execution always names `--env` explicitly.
+MCP is not part of the architecture.
 
 ## Install
 
@@ -62,6 +61,12 @@ implement ControlMaster multiplexing, so msdev:
   `env put`/`get` stay on scp/ssh streams (file bytes do not go through JSON RPC);
 - hides SSH console windows (`CREATE_NO_WINDOW`) and kills process trees with
   `taskkill /T` on timeout or cancel;
+- SSH is non-interactive: `BatchMode` unless a password is supplied, host keys
+  use `accept-new`, and there is no password/passphrase/yes-no prompt. When a
+  password is known, injects OpenSSH `SSH_ASKPASS` so `node connect` (and later
+  ssh/scp) can authenticate without a TTY; the local public key is then
+  installed on the Node so later logins are passwordless. The password is
+  never written to the node registry;
 - serves a TCP loopback endpoint for local `msdevd` when this Python build has
   no `AF_UNIX` sockets.
 
@@ -85,17 +90,44 @@ msdev node list
 msdev node status dev-122
 ```
 
-Adding a Node atomically creates a same-named host Env. Bootstrap or refresh
-the remote user daemon:
+Adding a Node atomically creates a same-named host Env. Connect deploys and
+starts the remote `msdevd` when needed:
 
 ```bash
-msdev node bootstrap dev-122
+msdev node connect dev-122
+```
+
+Connect uploads a **static Go msdevd** binary matching the node architecture
+(`linux-amd64` / `linux-arm64`) when the agent is missing or stale. No Python
+is required on the node.
+
+Build the static daemons before release or local testing:
+
+```bash
+bash msdevd/build-static.sh
+bash file-helper/build-static.sh
 ```
 
-Persistent OpenSSH masters are optional:
+Packaged artifacts live under `src/msdev/helpers/` (gitignored until built).
+The Go source is in `msdev/`.
+
+Persistent OpenSSH masters are optional. All SSH from msdev is
+non-interactive: host keys use `accept-new`, and password/passphrase prompts
+are disabled. Supply a password via environment or file (never a prompt);
+connect then installs the local public key (`~/.ssh/id_ed25519`, generated
+if missing) so later connections are passwordless:
 
 ```bash
+# Environment (also used by exec / env put after connect if persist is off)
+export MSDEV_SSH_PASSWORD='...'
+export MSDEV_SSH_PASSWORD_DEV_122='...'   # per-node override
+
 msdev node connect dev-122
+msdev node connect dev-122 --password-file FILE
+msdev node connect dev-122 --password-env VAR
+msdev node connect dev-122 --password PASSWORD   # non-interactive; visible in ps
+msdev node connect dev-122 --identity FILE     # choose which key to install
+msdev node connect dev-122 --no-install-key    # password only, do not copy key
 msdev node disconnect dev-122
 ```
 
@@ -109,8 +141,17 @@ msdev env guide dev-122 --write ./host-env-guide.md
 ```
 
 Guides are stored under `~/.config/msdev/guides/nodes/` and
-`~/.config/msdev/guides/environments/`, with private permissions and a 256 KiB
-limit. Agents read the applicable guides once before first use in a session.
+`~/.config/msdev/guides/environments/`. **Node guides** document how to
+connect; **Env guides** document how to initialize shared context (`setup`).
+
+```bash
+msdev env add dev-122-root \
+  --node dev-122 \
+  --setup-file ./setup-root.sh \
+  --wrap sudo --wrap -n --wrap --
+
+msdev env open dev-122-root
+```
 
 Open a human-operated interactive shell in an Env:
 
@@ -119,21 +160,7 @@ msdev env shell dev-122
 msdev env shell dev-122 --cwd /srv/project
 ```
 
-The command allocates an OpenSSH PTY and enters the Env's Docker runtime and
-conda/venv/uv layers. Exiting returns
-to the local shell. Only the shell session start and final status are visible
-to msdev; commands typed inside it are not individually logged. Agent
-automation should continue using `msdev exec`.
-
-Create another Env on the same Node for Docker and Python layers:
-
-```bash
-msdev env add dev-122-vllm \
-  --node dev-122 \
-  --docker-container vllm-ascend \
-  --layer conda:base \
-  --layer venv:/srv/project/.venv
-```
+Agent automation should use `msdev exec`, not `env shell`.
 
 ## File put, get, read, and write
 
@@ -162,13 +189,6 @@ msdev env write dev-122 /srv/project/note.md --file /tmp/note.md \
 Read before replacing an existing file. `--expected-sha256` is compare-and-swap
 replacement that refuses to overwrite a changed remote file.
 
-## NPU inventory
-
-```bash
-msdev npu list --node dev-122 --json
-msdev npu list --all --json
-```
-
 ## Command execution
 
 Commands execute synchronously and stream stdout and stderr to the terminal as
@@ -185,6 +205,13 @@ msdev exec \
   -- python3 run.py
 ```
 
+Quoted pipelines and `|` tokens are executed through a remote POSIX shell
+(`sh -c`), so they run on the Node instead of being treated as a single
+executable name. On a Windows `local` Env they use `cmd.exe /s /c`. Prefer
+`sh -c '…'` for complex scripts. Default streaming writes POSIX newlines as
+CRLF on a Windows console so remote line output does not staircase; piped
+CLI output keeps LF.
+
 `--timeout-seconds` defaults to `-1` (no deadline). Any positive finite duration
 is also accepted. A positive timeout kills the complete command
 process group and returns exit code 124. Cancelling the local CLI closes the RPC
@@ -195,30 +222,13 @@ serialization.
 `--result-json` selects captured, non-streaming execution and prints one
 structured JSON result containing stdout and stderr.
 
-## Model inventory
-
-Examples:
-
-```bash
-msdev model discover --node dev-122 --root /data/models
-msdev model list --node dev-122 --json
-msdev model list --all --json
-msdev model inspect model://qwen/Qwen3-32B@main --node dev-122
-msdev model validate model://qwen/Qwen3-32B@main --node dev-122
-msdev model audit --node dev-122
-```
-
-Use `msdev model --help` and the individual subcommand help for register,
-update, replicas, refresh, verify, export, import, and rebind.
-
 ## Architecture
 
 ```text
 msdev CLI
   -> typed core service
   -> UnixRpcTransport or SshRpcTransport
-  -> per-user msdevd
-  -> host/container command, env file transfer, NPU, or inventory
+  -> per-user msdevd (env session + job runner + files)
 ```
 
 Remote RPC responses and command output are bounded. Node/Env registries use

{msdev-0.10.1 → msdev-0.12.0}/README.md

@@ -1,15 +1,14 @@
 # msdev
 
-`msdev` manages connection Nodes and execution Envs. A Node owns SSH and its
-per-user `msdevd`; an Env references a Node and adds a host/Docker runtime plus
-optional conda/venv/uv layers.
+`msdev` exposes three capabilities: **`node`** (connect + host agent),
+**`env`** (shared execution context, shell, files), and **`exec`** (commands).
 
-The CLI is intentionally stateless:
+A Node owns SSH reachability and `msdevd` deployment. An Env owns the full
+execution context: host or Docker runtime, conda/venv/uv layers, optional
+`setup` script (root switch, proxy, etc.), command `wrap`, and static env vars.
 
-- Node-scoped NPU/model operations name `--node` or use `--all`;
-- execution names `--env`;
-- no harness conversation binding or implicit current Env exists;
-- MCP is not part of the architecture.
+The CLI is intentionally stateless: execution always names `--env` explicitly.
+MCP is not part of the architecture.
 
 ## Install
 
@@ -37,6 +36,12 @@ implement ControlMaster multiplexing, so msdev:
   `env put`/`get` stay on scp/ssh streams (file bytes do not go through JSON RPC);
 - hides SSH console windows (`CREATE_NO_WINDOW`) and kills process trees with
   `taskkill /T` on timeout or cancel;
+- SSH is non-interactive: `BatchMode` unless a password is supplied, host keys
+  use `accept-new`, and there is no password/passphrase/yes-no prompt. When a
+  password is known, injects OpenSSH `SSH_ASKPASS` so `node connect` (and later
+  ssh/scp) can authenticate without a TTY; the local public key is then
+  installed on the Node so later logins are passwordless. The password is
+  never written to the node registry;
 - serves a TCP loopback endpoint for local `msdevd` when this Python build has
   no `AF_UNIX` sockets.
 
@@ -60,17 +65,44 @@ msdev node list
 msdev node status dev-122
 ```
 
-Adding a Node atomically creates a same-named host Env. Bootstrap or refresh
-the remote user daemon:
+Adding a Node atomically creates a same-named host Env. Connect deploys and
+starts the remote `msdevd` when needed:
 
 ```bash
-msdev node bootstrap dev-122
+msdev node connect dev-122
+```
+
+Connect uploads a **static Go msdevd** binary matching the node architecture
+(`linux-amd64` / `linux-arm64`) when the agent is missing or stale. No Python
+is required on the node.
+
+Build the static daemons before release or local testing:
+
+```bash
+bash msdevd/build-static.sh
+bash file-helper/build-static.sh
 ```
 
-Persistent OpenSSH masters are optional:
+Packaged artifacts live under `src/msdev/helpers/` (gitignored until built).
+The Go source is in `msdev/`.
+
+Persistent OpenSSH masters are optional. All SSH from msdev is
+non-interactive: host keys use `accept-new`, and password/passphrase prompts
+are disabled. Supply a password via environment or file (never a prompt);
+connect then installs the local public key (`~/.ssh/id_ed25519`, generated
+if missing) so later connections are passwordless:
 
 ```bash
+# Environment (also used by exec / env put after connect if persist is off)
+export MSDEV_SSH_PASSWORD='...'
+export MSDEV_SSH_PASSWORD_DEV_122='...'   # per-node override
+
 msdev node connect dev-122
+msdev node connect dev-122 --password-file FILE
+msdev node connect dev-122 --password-env VAR
+msdev node connect dev-122 --password PASSWORD   # non-interactive; visible in ps
+msdev node connect dev-122 --identity FILE     # choose which key to install
+msdev node connect dev-122 --no-install-key    # password only, do not copy key
 msdev node disconnect dev-122
 ```
 
@@ -84,8 +116,17 @@ msdev env guide dev-122 --write ./host-env-guide.md
 ```
 
 Guides are stored under `~/.config/msdev/guides/nodes/` and
-`~/.config/msdev/guides/environments/`, with private permissions and a 256 KiB
-limit. Agents read the applicable guides once before first use in a session.
+`~/.config/msdev/guides/environments/`. **Node guides** document how to
+connect; **Env guides** document how to initialize shared context (`setup`).
+
+```bash
+msdev env add dev-122-root \
+  --node dev-122 \
+  --setup-file ./setup-root.sh \
+  --wrap sudo --wrap -n --wrap --
+
+msdev env open dev-122-root
+```
 
 Open a human-operated interactive shell in an Env:
 
@@ -94,21 +135,7 @@ msdev env shell dev-122
 msdev env shell dev-122 --cwd /srv/project
 ```
 
-The command allocates an OpenSSH PTY and enters the Env's Docker runtime and
-conda/venv/uv layers. Exiting returns
-to the local shell. Only the shell session start and final status are visible
-to msdev; commands typed inside it are not individually logged. Agent
-automation should continue using `msdev exec`.
-
-Create another Env on the same Node for Docker and Python layers:
-
-```bash
-msdev env add dev-122-vllm \
-  --node dev-122 \
-  --docker-container vllm-ascend \
-  --layer conda:base \
-  --layer venv:/srv/project/.venv
-```
+Agent automation should use `msdev exec`, not `env shell`.
 
 ## File put, get, read, and write
 
@@ -137,13 +164,6 @@ msdev env write dev-122 /srv/project/note.md --file /tmp/note.md \
 Read before replacing an existing file. `--expected-sha256` is compare-and-swap
 replacement that refuses to overwrite a changed remote file.
 
-## NPU inventory
-
-```bash
-msdev npu list --node dev-122 --json
-msdev npu list --all --json
-```
-
 ## Command execution
 
 Commands execute synchronously and stream stdout and stderr to the terminal as
@@ -160,6 +180,13 @@ msdev exec \
   -- python3 run.py
 ```
 
+Quoted pipelines and `|` tokens are executed through a remote POSIX shell
+(`sh -c`), so they run on the Node instead of being treated as a single
+executable name. On a Windows `local` Env they use `cmd.exe /s /c`. Prefer
+`sh -c '…'` for complex scripts. Default streaming writes POSIX newlines as
+CRLF on a Windows console so remote line output does not staircase; piped
+CLI output keeps LF.
+
 `--timeout-seconds` defaults to `-1` (no deadline). Any positive finite duration
 is also accepted. A positive timeout kills the complete command
 process group and returns exit code 124. Cancelling the local CLI closes the RPC
@@ -170,30 +197,13 @@ serialization.
 `--result-json` selects captured, non-streaming execution and prints one
 structured JSON result containing stdout and stderr.
 
-## Model inventory
-
-Examples:
-
-```bash
-msdev model discover --node dev-122 --root /data/models
-msdev model list --node dev-122 --json
-msdev model list --all --json
-msdev model inspect model://qwen/Qwen3-32B@main --node dev-122
-msdev model validate model://qwen/Qwen3-32B@main --node dev-122
-msdev model audit --node dev-122
-```
-
-Use `msdev model --help` and the individual subcommand help for register,
-update, replicas, refresh, verify, export, import, and rebind.
-
 ## Architecture
 
 ```text
 msdev CLI
   -> typed core service
   -> UnixRpcTransport or SshRpcTransport
-  -> per-user msdevd
-  -> host/container command, env file transfer, NPU, or inventory
+  -> per-user msdevd (env session + job runner + files)
 ```
 
 Remote RPC responses and command output are bounded. Node/Env registries use

{msdev-0.10.1 → msdev-0.12.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "msdev"
-version = "0.10.1"
+version = "0.12.0"
 description = "Portable nodes and execution environments for msModelSlim development"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -44,7 +44,7 @@ package-dir = { "" = "src" }
 where = ["src"]
 
 [tool.setuptools.package-data]
-msdev = ["helpers/msdev-file-helper-*"]
+msdev = ["helpers/msdev-file-helper-*", "helpers/msdevd-linux-*"]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{msdev-0.10.1 → msdev-0.12.0}/src/msdev/__init__.py

@@ -1,3 +1,3 @@
 """Portable node and execution-environment tooling for msModelSlim."""
 
-__version__ = "0.10.1"
+__version__ = "0.12.0"