@rubytech/create-realagent 1.0.657 → 1.0.658

package/payload/platform/plugins/docs/references/platform.md

@@ -68,7 +68,7 @@ The admin UI includes a live terminal surface that opens a real shell on your Pi
 
 The tmux session outlives admin-server restarts — running an upgrade inside this terminal means you see the live shell output continuously, even through the admin server's own restart mid-upgrade. Closing the browser tab does not kill the running work; re-opening the Software Update window reattaches to the same session during an active upgrade and scrollback shows everything that happened in the meantime. Password-protected `sudo` prompts appear natively inside the terminal, and the password you type never leaves the Pi — the admin-server proxy is a raw byte pipe that never inspects frame payloads.
 
-The Software Update window mounts the terminal lazily: neither the terminal, its WebSocket, nor its black-backgrounded container render until you click Upgrade. Pre-click, the window shows a small "Ready to upgrade — click Upgrade to begin." line, no network traffic flows, and the upgrade UI is the lifecycle indicator — not the terminal. After you click, the window adds a status row above the terminal ("Upgrading to v… · elapsed: Ns · Downloading installer…" flipping to "Running installer…" on the first byte of installer output) so the 5–30 second npx cold-start window is never silent. The upgrade command is dispatched the moment the WebSocket opens — you won't see "terminal not ready" warnings on a healthy device. If the admin server cannot reach `ttyd`, the window renders an inline "Admin terminal not available" message with the exact re-install command and a Try again button. The scrollback-across-reopen behaviour above still applies during an active upgrade (a sessionStorage flag remembers that an upgrade is in flight so reopening the window re-mounts the terminal and reattaches; the elapsed counter keeps ticking from the original start time).
+The Software Update window mounts the terminal lazily: neither the terminal, its WebSocket, nor its black-backgrounded container render until you click Upgrade. Pre-click, the window shows a small "Ready to upgrade — click Upgrade to begin." line and no network traffic flows. On click, the window mounts the terminal and sends the npx command via `RemoteTerminal.onReady`; the terminal output is the only upgrade observability surface. A background version poll flips to the success row when `installed === latest` and reloads the page. The upgrade command is dispatched the moment the WebSocket opens — you won't see "terminal not ready" warnings on a healthy device. If the admin server cannot reach `ttyd`, the window renders an inline "Admin terminal not available" message with the exact re-install command and a Try again button. Closing the window does not kill the upgrade — the tmux session keeps running upstream — but the window itself starts fresh on every reopen: if you reopen during an in-flight upgrade, click Upgrade again and the scrollback shows the in-progress output.
 
 ## AI Content Provenance
 

package/payload/platform/plugins/docs/references/troubleshooting.md

@@ -125,9 +125,9 @@ npx -y @rubytech/create-maxy@latest
 
 Then return to the upgrade window and click **Try again**. The window re-probes `/api/health` and, once ttyd is listening, the terminal area mounts as normal. If the problem persists, check the boot log for `[ttyd] upstream NOT reachable on 127.0.0.1:7681` and follow the `maxy-ttyd` restart steps above.
 
-## Upgrade spinner turns but terminal stays blank
+## Upgrade terminal stays blank after clicking Upgrade
 
-**Symptom:** You clicked **Upgrade**, the progress row is showing with an elapsed counter ticking, but the terminal area below stays empty for more than about a minute with no output.
+**Symptom:** You clicked **Upgrade**, the terminal area mounted, but the terminal stays empty for more than about 60 seconds with no output.
 
 **What it means:** The upgrade command was dispatched successfully (`onReady` fired), but `ttyd` is not relaying any bytes back from the installer — the `npx` process may have crashed before it printed anything, or `ttyd` itself has lost its PTY.
 
@@ -137,7 +137,7 @@ Then return to the upgrade window and click **Try again**. The window re-probes
 sudo systemctl --user status maxy-ttyd
 ```
 
-If it's not running, restart it with `sudo systemctl --user restart maxy-ttyd`. Then close and reopen the Software Update window. If `ttyd` is healthy and the spinner keeps turning with no output, the installer process itself has died — re-run `npx -y @rubytech/create-maxy@latest` from an SSH shell directly.
+If it's not running, restart it with `sudo systemctl --user restart maxy-ttyd`. Then close and reopen the Software Update window. If `ttyd` is healthy and the terminal stays empty, the installer process itself has died — re-run `npx -y @rubytech/create-maxy@latest` from an SSH shell directly.
 
 ## Orphan Account Directory Archived to `.trash/`