deadbyte-mcp 0.15.45 → 0.15.46

package/README.txt

@@ -1,4 +1,4 @@
-DEADBYTE MCP V0.15.45 / R71 STABLE BASELINE CANDIDATE
+DEADBYTE MCP V0.15.46 / R72 REMOTE HOTFIX CANDIDATE
 =========================
 
 AUTHENTICATED MACHINE TRUTH + DURABLE AGENT + CODING + AUTONOMOUS PRODUCTION ENGINE
@@ -16,12 +16,12 @@ check `--version` before issuing a stateful command. The compatibility CMD
 fails with an explanation when npm is detected rather than forwarding the
 wrong command to the controller.
 
-  npx -y deadbyte-mcp@0.15.45 mcp
-  npx -y deadbyte-mcp@0.15.45 remote
-  npx -y deadbyte-mcp@0.15.45 remote status
-  npx -y deadbyte-mcp@0.15.45 remote restart
-  npx -y deadbyte-mcp@0.15.45 audit status
-  npx -y deadbyte-mcp@0.15.45 audit verify
+  npx -y deadbyte-mcp@0.15.46 mcp
+  npx -y deadbyte-mcp@0.15.46 remote
+  npx -y deadbyte-mcp@0.15.46 remote status
+  npx -y deadbyte-mcp@0.15.46 remote restart
+  npx -y deadbyte-mcp@0.15.46 audit status
+  npx -y deadbyte-mcp@0.15.46 audit verify
 
 MAJOR MCP CLIENT STDIO CONFIGS
 -------------------------------
@@ -32,7 +32,7 @@ CLAUDE DESKTOP
     "mcpServers": {
       "deadbyte": {
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -44,7 +44,7 @@ Save as .cursor/mcp.json:
     "mcpServers": {
       "deadbyte": {
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -57,7 +57,7 @@ Save as .vscode/mcp.json:
       "deadbyte": {
         "type": "stdio",
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -67,13 +67,14 @@ Add to the Codex MCP configuration:
 
   [mcp_servers.deadbyte]
   command = "npx"
-  args = ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+  args = ["-y", "deadbyte-mcp@0.15.46", "mcp"]
 
 The `mcp` command is the quiet stdio server entry for local MCP clients; stdout is reserved for MCP.
 The remote CLI invokes the stable active-release PowerShell launcher directly with shell=false.
-Bare `remote` is a foreground device session: it starts/resumes the verified runtime, arms process,
-coding, and autonomous authority, independently verifies those three planes are ARMED, and requires
-Desktop and Host to remain DISARMED. Desktop observation/UIA grounding is read-only; guarded GUI input
+Bare `remote` is a foreground observation-only session. It starts/resumes the verified runtime
+without arming Process, Coding, Autonomous, Desktop, or Host; all five must be DISARMED.
+Use `remote --operator` to request Process/Coding/Autonomous explicitly, subject to
+independent R70 owner approval, bound policy and signed authority checks. Desktop observation/UIA grounding is read-only; guarded GUI input
 requires the separate explicit Desktop standing grant (`armdesktop`) and is never implied by Autonomous authority. The single remote console shows device/bridge/cloud/session readiness plus a
 unified live timeline (`RUN`, `OK`, `ERR`, interrupted/recovery, cursors, and sanitized Bridge IN/OUT/ERR
 diagnostics) without dumping raw JSON payloads, tokens, private keys, or full Bridge payload records. Session shutdown
@@ -355,7 +356,7 @@ CONTROLLER
 ----------
 Primary operator entry point:
 
-  npx -y deadbyte-mcp@0.15.45 remote
+  npx -y deadbyte-mcp@0.15.46 remote
 
 The legacy CMD entry remains compatibility-only for R33 rollback safety.
 
@@ -416,7 +417,7 @@ MCP CLIENT CONFIGURATION
 ------------------------
 The local stdio entry point is quiet and suitable for MCP hosts:
 
-  npx -y deadbyte-mcp@0.15.45 mcp
+  npx -y deadbyte-mcp@0.15.46 mcp
 
 CLAUDE DESKTOP
 Use the standard local-server entry in claude_desktop_config.json:
@@ -425,7 +426,7 @@ Use the standard local-server entry in claude_desktop_config.json:
     "mcpServers": {
       "deadbyte": {
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -438,7 +439,7 @@ Create .cursor/mcp.json:
       "deadbyte": {
         "type": "stdio",
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -451,7 +452,7 @@ Create .vscode/mcp.json:
       "deadbyte": {
         "type": "stdio",
         "command": "npx",
-        "args": ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+        "args": ["-y", "deadbyte-mcp@0.15.46", "mcp"]
       }
     }
   }
@@ -461,9 +462,9 @@ Add this to ~/.codex/config.toml:
 
   [mcp_servers.deadbyte]
   command = "npx"
-  args = ["-y", "deadbyte-mcp@0.15.45", "mcp"]
+  args = ["-y", "deadbyte-mcp@0.15.46", "mcp"]
 
-The remote device path remains `npx -y deadbyte-mcp@0.15.45 remote`. Remote public MCP uses the
+The remote device path remains `npx -y deadbyte-mcp@0.15.46 remote`. Remote public MCP uses the
 verified HTTPS named-tunnel URL selected by the active generation; do not commit a private device
 URL or tunnel token into a repository.