DEADBYTE MCP V0.7.0 WINDOWS TARGET GATE
======================================
STATUS=PENDING

Run on the intended Windows target from the extracted V0.7.0 package:

  npm ci
  npm run gate:windows

Then additionally configure controller/deadbyte-controller.config.psd1 from the trusted
bridge/cloud launch commands and run:

  controller\DEADBYTE-MCP.cmd start
  controller\DEADBYTE-MCP.cmd test
  controller\DEADBYTE-MCP.cmd fulltest
  controller\DEADBYTE-MCP.cmd park
  controller\DEADBYTE-MCP.cmd resume
  controller\DEADBYTE-MCP.cmd stop

Required lifecycle proof:
  exit/close controller after start -> runtime remains alive
  reopen status -> same PID + creation time + image path + SHA-256 identity
  park -> cloud only
  resume -> same Quick Tunnel origin when cloud process remained alive
  stop -> no owned runtime process
