deadbyte-mcp 0.9.0 → 0.11.0

package/bench/fixtures/r36/case-map.json

@@ -0,0 +1,8 @@
+{
+  "schema": "deadbyte.r36-benchmark-case-map.v1",
+  "suite_id": "r36-production-coding-v1",
+  "source_spec": "docs/superpowers/specs/2026-09-18-r36-zero-loss-autonomy-design.md#r36-h-capability-benchmark-and-competitor-evidence",
+  "case_count": 30,
+  "evidence_model": "Each case is a hermetic repository test/fixture mapping. A passing process alone is insufficient when a pass_witness is declared. Production rollback/restore is separately required by Task 10.",
+  "competitor_evidence_classes": ["documented", "direct_observation"]
+}

package/bin/WORKER-REGISTRY.txt

@@ -2,11 +2,11 @@ schema=deadbyte.worker-registry.v1
 version=0.6.0
 policy=compile-time-operation-to-executable
 launcher.executable=deadbyte-exec.exe
-launcher.sha256=1fe14b8f312f33f9cc90cb3ad1b3e7657e93235465bda62307ed837bdcee985b
+launcher.sha256=a84168020dee3bb5d63d97b1076523232872bf142859c07bfcb77a45428a1ce5
 operation.lowercase_ascii=contained-transform-v1
 operation.reverse_bytes=contained-reverse-v1
 operation.uppercase_ascii=contained-transform-v1
 worker.contained-reverse-v1.executable=contained-reverse-worker.exe
-worker.contained-reverse-v1.sha256=e4989357ba06f24e049845290ba01c35c442dcebe2b048bfea52a04fc6b96f19
+worker.contained-reverse-v1.sha256=9f3754c3c6fe71d6fe0e04889e33b39cdc64b633e0b713d5979faec748dec69d
 worker.contained-transform-v1.executable=contained-transform-worker.exe
-worker.contained-transform-v1.sha256=158c34b6c9e6d8476a31cdb34f354ace5a3c1071f2af54607e701baecc674405
+worker.contained-transform-v1.sha256=01528ffe61736cdb5010396f4b1c52203c7e1848b3aeb4181a0c04a508e1da30

package/controller/README.TXT

@@ -1,4 +1,4 @@
-DEADBYTE MCP V0.9.0 / R35 CONTROLLER
+DEADBYTE MCP V0.11.0 / R37 CONTROLLER
 ====================================
 
 ENTRY POINT
@@ -8,10 +8,12 @@ Primary operator entry point:
   npx deadbyte-mcp@latest remote
 
 Bare `remote` is a foreground device session. It starts the verified runtime, arms process,
-coding, autonomous, and host authority, verifies all four planes are ARMED, then prints compact
-human tool results only. It never dumps SHA text, request IDs, payload JSON, or duplicate Bridge
-stdout by default; use `remote --verbose` for the detailed audit/runtime stream. Ctrl+C/SIGTERM or
-foreground input closure revokes all four planes and parks
+coding, and autonomous authority, verifies those three planes are ARMED, and requires Host to stay
+DISARMED. The production Bridge uses the R37 compact capability profile (<=42 tools) while local
+stdio MCP keeps the exact full 76-tool profile. The compact console shows request-before-result
+Live Activity without raw SHA text, request IDs, payload JSON, or duplicate Bridge stdout by
+default; use `remote --verbose` for the detailed audit/runtime stream. Ctrl+C/SIGTERM or foreground
+input closure revokes process/coding/autonomous authority, applies fail-safe Host disarm, and parks
 the Bridge. A detached nonce-bound guardian performs the same fixed revoke+park cleanup if the
 foreground owner is hard-killed. The v2 session marker records owner PID, guardian PID, and random
 256-bit nonce so a guardian cannot remove a replacement session marker; a later start recovers only
@@ -94,7 +96,7 @@ policy digests and profile hashes to the explicit mutable development root; the
   armautonomous      require coding authority, then enable a standing autonomous grant
   disarmautonomous   revoke autonomous authority immediately
   autonomousstatus   report configured/standing-grant/coding-disarmed state
-  autonomoustest     run the 73-tool public catalog sampling MRTR production gate
+  autonomoustest     run the R37 compact public capability-closure MRTR production gate
 
 disarmcoding also revokes autonomous authority. No MCP tool creates or widens either
 grant. With an openai_compatible planner the MCP server starts a background supervisor;

package/controller/deadbyte-controller.ps1

@@ -19,6 +19,33 @@ function Fail([string]$Message) { throw "DEADBYTE controller: $Message" }
 function Ensure-Directory([string]$Path) { if (-not (Test-Path -LiteralPath $Path -PathType Container)) { New-Item -ItemType Directory -Path $Path -Force | Out-Null } }
 function Ledger-Path([string]$Name) { Join-Path $RuntimeDir ("{0}.instance.json" -f $Name.ToLowerInvariant()) }
 function Log-Path([string]$Name, [string]$Kind) { Join-Path $LogDir ("{0}.{1}.log" -f $Name.ToLowerInvariant(), $Kind) }
+function Controller-StartFailurePath { Join-Path $RuntimeDir 'controller-start-failure.json' }
+function Read-LogTailBounded([string]$Path, [int]$MaxChars = 8192) {
+    if (-not (Test-Path -LiteralPath $Path -PathType Leaf)) { return '' }
+    try {
+        $text = (@(Get-Content -LiteralPath $Path -Encoding UTF8 -Tail 80 -ErrorAction Stop) -join [Environment]::NewLine)
+        if ($text.Length -gt $MaxChars) { return $text.Substring($text.Length - $MaxChars) }
+        return $text
+    } catch { return '' }
+}
+function Write-ControllerStartFailure([string]$Name, [System.Exception]$Exception) {
+    Ensure-Directory $RuntimeDir; Ensure-Directory $LogDir
+    $body = [ordered]@{
+        schema = 'deadbyte.controller-start-failure.v1'
+        command = $Name
+        failed_at_utc = [DateTime]::UtcNow.ToString('o')
+        message = [string]$Exception.Message
+        bridge_stdout_tail = Read-LogTailBounded (Log-Path 'Bridge' 'stdout')
+        bridge_stderr_tail = Read-LogTailBounded (Log-Path 'Bridge' 'stderr')
+        cloud_stdout_tail = Read-LogTailBounded (Log-Path 'Cloud' 'stdout')
+        cloud_stderr_tail = Read-LogTailBounded (Log-Path 'Cloud' 'stderr')
+    }
+    $path = Controller-StartFailurePath
+    $tmp = $path + '.tmp'
+    $json = $body | ConvertTo-Json -Depth 4
+    [System.IO.File]::WriteAllText($tmp, $json, (New-Object System.Text.UTF8Encoding($false)))
+    Move-Item -LiteralPath $tmp -Destination $path -Force
+}
 
 
 function Read-TextFileSafe([string]$Path) {
@@ -409,8 +436,11 @@ function Start-OwnedComponent([string]$Name, $Spec, $Cfg = $null) {
     $previousSupervisorMarkerEnv = $env:DEADBYTE_SUPERVISOR_MARKER
     $hadAutonomousSupervisorModeEnv = Test-Path Env:DEADBYTE_AUTONOMOUS_SUPERVISOR_MODE
     $previousAutonomousSupervisorModeEnv = $env:DEADBYTE_AUTONOMOUS_SUPERVISOR_MODE
+    $hadCapabilityProfileEnv = Test-Path Env:DEADBYTE_CAPABILITY_PROFILE
+    $previousCapabilityProfileEnv = $env:DEADBYTE_CAPABILITY_PROFILE
     try {
         if ($Name -eq 'Bridge' -and $Cfg) {
+            $env:DEADBYTE_CAPABILITY_PROFILE = 'compact'
             $env:DEADBYTE_AUDIT_RUNTIME = '1'
             $env:DEADBYTE_CORE_ROOT = [string]$Cfg.CoreRoot
             $env:DEADBYTE_WORKSPACE_ROOT = [string]$Cfg.WorkspaceRoot
@@ -442,6 +472,7 @@ function Start-OwnedComponent([string]$Name, $Spec, $Cfg = $null) {
                 $env:DEADBYTE_PRIVILEGED_POLICY = [string]$Cfg.HostPolicyFile
             }
         } elseif ($Name -eq 'Supervisor' -and $Cfg) {
+            Remove-Item Env:DEADBYTE_CAPABILITY_PROFILE -ErrorAction SilentlyContinue
             Remove-Item Env:DEADBYTE_AUDIT_RUNTIME -ErrorAction SilentlyContinue
             Remove-Item Env:DEADBYTE_PRIVILEGED_POLICY -ErrorAction SilentlyContinue
             Remove-Item Env:DEADBYTE_MACHINE_RUNTIME -ErrorAction SilentlyContinue
@@ -460,6 +491,7 @@ function Start-OwnedComponent([string]$Name, $Spec, $Cfg = $null) {
             $env:DEADBYTE_SUPERVISOR_ONCE = '0'
             $env:DEADBYTE_SUPERVISOR_MARKER = Join-Path $RuntimeDir 'autonomous-supervisor-owner.json'
         } else {
+            Remove-Item Env:DEADBYTE_CAPABILITY_PROFILE -ErrorAction SilentlyContinue
             Remove-Item Env:DEADBYTE_AUDIT_RUNTIME -ErrorAction SilentlyContinue
         }
         $proc = Start-Process @start
@@ -502,6 +534,8 @@ function Start-OwnedComponent([string]$Name, $Spec, $Cfg = $null) {
         else { Remove-Item Env:DEADBYTE_SUPERVISOR_MARKER -ErrorAction SilentlyContinue }
         if ($hadAutonomousSupervisorModeEnv) { $env:DEADBYTE_AUTONOMOUS_SUPERVISOR_MODE = $previousAutonomousSupervisorModeEnv }
         else { Remove-Item Env:DEADBYTE_AUTONOMOUS_SUPERVISOR_MODE -ErrorAction SilentlyContinue }
+        if ($hadCapabilityProfileEnv) { $env:DEADBYTE_CAPABILITY_PROFILE = $previousCapabilityProfileEnv }
+        else { Remove-Item Env:DEADBYTE_CAPABILITY_PROFILE -ErrorAction SilentlyContinue }
     }
     Start-Sleep -Milliseconds 150
     $obs = Get-ProcessObservation ([int]$proc.Id)
@@ -1145,13 +1179,25 @@ function Run-Command([string]$Name) {
     }
 }
 
-if ($Command -ne 'menu') { Run-Command $Command; exit 0 }
+if ($Command -ne 'menu') {
+    $recordsStartFailure = $Command -in @('start','resume','restart')
+    if ($recordsStartFailure) { Remove-Item -LiteralPath (Controller-StartFailurePath) -Force -ErrorAction SilentlyContinue }
+    try {
+        Run-Command $Command
+        exit 0
+    } catch {
+        if ($recordsStartFailure) {
+            try { Write-ControllerStartFailure $Command $_.Exception } catch {}
+        }
+        throw
+    }
+}
 
 while ($true) {
     Clear-Host
     $cfg = Get-Config
     Assert-ControllerRootBound $cfg
-    Write-Host 'DEADBYTE MCP ON-DEMAND CONTROLLER V0.9.0 / R35'
+    Write-Host 'DEADBYTE MCP ON-DEMAND CONTROLLER V0.11.0 / R37'
     Write-Host '======================================'
     Show-State $cfg | Out-Null
     Write-Host ''

package/controller/deadbyte-process-policy.json

@@ -1,15 +1,15 @@
 {
   "schema": "deadbyte.process-policy.v1",
   "enabled": true,
-  "grant_file": "D:\\Projects\\deadbyte-mcp-r35-release-v0.9.0-r2\\controller\\runtime\\process-grant.json",
-  "state_dir": "D:\\Projects\\deadbyte-mcp-r35-release-v0.9.0-r2\\controller\\runtime\\process-state",
+  "grant_file": "D:\\Projects\\deadbyte-mcp-r36-dev\\controller\\runtime\\process-grant.json",
+  "state_dir": "D:\\Projects\\deadbyte-mcp-r36-dev\\controller\\runtime\\process-state",
   "native_host": {
-    "path": "D:\\Projects\\deadbyte-mcp-r35-release-v0.9.0-r2\\bin\\deadbyte-process-host.exe",
-    "sha256": "9fa67a2aa66a40b67828dd537ca24b1feb118d386955b81b2df2e1bf5b7b57d7"
+    "path": "D:\\Projects\\deadbyte-mcp-r36-dev\\bin\\deadbyte-process-host.exe",
+    "sha256": "8c79f30e834daf2f0a916928bc719abf27ba111f446056bf2993c84d0432747a"
   },
   "roots": {
     "core": {
-      "path": "D:\\Projects\\deadbyte-mcp-r35-release-v0.9.0-r2",
+      "path": "D:\\Projects\\deadbyte-mcp-r36-dev",
       "deny_paths": [
         "node_modules",
         "controller/runtime",

package/docs/ARCHITECTURE.md

@@ -1,4 +1,4 @@
-# DEADBYTE MCP V0.9.0 / R35 ARCHITECTURE
+# DEADBYTE MCP V0.11.0 / R37 ARCHITECTURE
 
 ```mermaid
 flowchart TD

package/docs/R36-CAPABILITY-EVIDENCE.md

@@ -0,0 +1,43 @@
+# R36 Capability Evidence
+
+Status: development evidence for R36 / planned package version 0.10.0. This document is not a release or Final claim. Release authority remains the R36 freeze, Windows gate, activation/rollback/restore, independent final closure, and npm byte-identity gates.
+
+## Reproducible DEADBYTE observation
+
+The approved R36 production-coding corpus contains 30 required cases. The latest hermetic run completed with:
+
+- cases: 30
+- correct: 30
+- capability_reachable: 30
+- evidence_verified: 30
+- stable verdict identity SHA-256: `3a1d668fcc0c3c38362d0c642c5247357ed7ec6063d89b544c7a1c090521c66e`
+- fixture identity SHA-256: `4a12567e285a4b7b59d9285e08f918357e7b560d2cb9b65f017367188839ef7e`
+- two consecutive passing observation SHA-256 values: `710d0f3ef7bbe1fa3a6b782ba6442a8161d0d5556622e3ca95f2f3baf97cbae3` and `44b52d9507dc04baeeebb5617c63d7d59dbe9b29878fc9420bc5bac3ff7fee0b` (timing-sensitive by design)
+
+The corpus covers repository exploration, literal/regex/path search, deterministic paging, bounded multi-read, stat/reparse handling, stale-edit rejection, Native Diff file and topology transactions, semantic navigation/diagnostics/implementations/rename, process lifecycle/actions/recovery, autonomous repair, release-gate refusal, provider interruption recovery, remote replay/deduplication, compact capability closure, Live Logs ordering/redaction, receipt rejection, and hermetic rollback/restore mechanism proof.
+
+The benchmark runner requires both test success and a named pass witness. A zero exit caused only by a skipped or unmatched test is not accepted as evidence. Correctness, reachability, and evidence verification are recorded as separate dimensions rather than collapsed into a marketing score.
+
+## External reference baseline
+
+The comparison references are public upstream projects:
+
+- Desktop Commander local MCP: https://github.com/wonderwhy-er/DesktopCommanderMCP
+- Remote Desktop Commander: https://github.com/desktop-commander/remote-desktop-commander
+- Serena: https://github.com/oraios/serena
+
+`documented` means a capability is described by the upstream public project documentation/source used as a behavioral reference. `direct_observation` means we executed the referenced implementation or service ourselves and retained reproducible local evidence. These evidence classes are not interchangeable.
+
+For this R36 development checkpoint, the DEADBYTE 30-case result above is `direct_observation`. Competitor capability descriptions used for design comparison are `documented` unless an explicit retained direct run is attached to a later release evidence record. Unavailable service state, quota, account requirements, or missing local authority must never be converted into a passing direct observation.
+
+## Comparison discipline
+
+R36 is evaluated for production software-engineering autonomy, not unrelated document-editing or generic desktop-administration breadth. Tool count is not a quality metric and is not used as a release verdict.
+
+The mechanisms tested directly in DEADBYTE include SHA-256 mutation preconditions, Native Diff rollback and independent verification, separately revocable process/coding/autonomous/host authority, typed capability routing, signed journals/receipts, bounded long-process observation, semantic rename through Native Diff, capability-aware autonomous execution, resumable Live Logs, compact-surface closure, and immutable release rollback/restore machinery.
+
+Desktop Commander, Remote Desktop Commander, and Serena remain useful comparison references for different strengths and breadth. Any public comparison made from R36 must name the supporting DEADBYTE benchmark case/evidence identity and identify the competitor side as `documented` or `direct_observation`. A difference in mechanism is not by itself a general product ranking.
+
+## Release boundary
+
+Case 30 is a hermetic rollback/restore mechanism test. It does not replace the production release proof. Before R36 can become Final, one exact frozen 0.10.0 candidate must still pass the full source regression and Windows gate, activate as an immutable slot, roll back to the exact sealed R35 predecessor, restore the exact same R36 candidate, pass independent final-closure verification, and then be packed and published from that verified candidate with registry tarball byte identity proved.