zerogterm 0.7.0-alpha3 → 0.8.0-alpha

package/README.md

@@ -37,9 +37,9 @@ See the project walkthrough on [YouTube](https://youtu.be/4aJZCxLHD14).
 
 ## Release status
 
-ZeroG Terminal is currently a public alpha. The current release is `0.7.0-alpha3`; the version history is tracked in [versions.txt](versions.txt). The running version is shown beside the wordmark in the title bar, read from the app itself rather than written into the interface, so it is accurate in a packaged build too.
+ZeroG Terminal is currently a public alpha. The current release is `0.8.0-alpha`; the version history is tracked in [versions.txt](versions.txt). The running version is shown beside the wordmark in the title bar, read from the app itself rather than written into the interface, so it is accurate in a packaged build too.
 
-The npm package contains the built Electron application and project documentation. It is intended for early adopters and testing rather than production use.
+The GitHub Releases page provides a Windows x64 installer and portable executable for each desktop release. These alpha builds are intended for early adopters and testing rather than production use. The npm package remains available for developers who prefer to launch ZeroG from Node.js.
 
 ## Terminal shortcuts
 
@@ -413,6 +413,11 @@ required whichever shell you start them from.
 for Windows and macOS, so a C/C++ toolchain is a Linux requirement rather than a
 general one — there, `npm install` compiles it.
 
+### Windows desktop release
+
+Download the latest Windows x64 installer from [GitHub Releases](https://github.com/HappyMonkeyAI/ZeroGTerm/releases). The installer adds ZeroG Terminal to the current user's applications. The portable `.exe` can be run without installation.
+
+These binaries are unsigned alpha builds, so Windows SmartScreen may show a warning on first launch. If you downloaded the release from the official repository, choose **More info → Run anyway**. Review the release notes before installing; SSH, WSL, PowerShell, Git Bash, and any remote `screen` sessions are provided by the host system rather than bundled with the app.
 ### Linux
 
 ```bash

package/dist/main/main/main.js

@@ -44,10 +44,53 @@ function parsePtySize(value) {
         return undefined;
     return { cols: cols, rows: rows };
 }
-// GPU is unstable under Toolbox/Wayland on this host; allow override.
-if (process.env.ZEROG_ENABLE_GPU !== '1') {
+/**
+ * Software rendering, on the one platform that needs it.
+ *
+ * The GPU is unstable under Toolbox/Wayland, which is where this was found and
+ * why the switch exists. It was applied everywhere, though, and on Windows that
+ * is a straight loss: every pane is then rasterised on the CPU, and a window
+ * holding a dozen terminals can stall long enough for the compositor to grey it
+ * out — which reads to the user as a crash. Scoped to Linux, with an override in
+ * each direction so a machine that disagrees can say so.
+ */
+if (process.env.ZEROG_DISABLE_GPU === '1') {
+    app.disableHardwareAcceleration();
+}
+else if (process.platform === 'linux' && process.env.ZEROG_ENABLE_GPU !== '1') {
     app.disableHardwareAcceleration();
 }
+/**
+ * How long the main process may block before it is worth saying so.
+ *
+ * Every pty write, every IPC reply and every window event goes through this one
+ * loop, so a stall here freezes the whole application however many panes are
+ * open. 250ms is well past a slow frame and well short of anything a person
+ * would call a hang, which makes it a warning rather than a report.
+ */
+const LOOP_STALL_MS = 250;
+const LOOP_SAMPLE_MS = 500;
+/**
+ * Watch the main process for stalls.
+ *
+ * A timer that knows when it should have fired is the whole instrument: the
+ * difference between that and when it did fire is time the loop spent unable to
+ * run anything. It cannot say what blocked — only that something did, and for
+ * how long, which is the fact that was missing when a frozen window had to be
+ * explained from a screenshot.
+ */
+function watchEventLoop() {
+    let due = Date.now() + LOOP_SAMPLE_MS;
+    const timer = setInterval(() => {
+        const now = Date.now();
+        const lag = now - due;
+        due = now + LOOP_SAMPLE_MS;
+        if (lag >= LOOP_STALL_MS)
+            console.warn(`[zerog] main process blocked for ${Math.round(lag)}ms`);
+    }, LOOP_SAMPLE_MS);
+    // Diagnostics must never be the reason the process stays alive.
+    timer.unref();
+}
 function createWindow() {
     win = new BrowserWindow({
         width: 1440,
@@ -95,8 +138,32 @@ function createWindow() {
     win.webContents.on('preload-error', (_event, path, error) => {
         console.error('[zerog] preload-error', path, error);
     });
-    win.webContents.on('console-message', (_event, _level, message) => {
-        console.log('[renderer]', message);
+    // The renderer's console, copied into this one — which is the only way a
+    // warning from the workspace reaches a log at all.
+    //
+    // Read from the event object rather than from the positional arguments that
+    // used to carry it. Electron still passes those, and says so on every start:
+    // "'console-message' arguments are deprecated and will be removed". When they
+    // go, a handler reading them would keep being called and print nothing, so the
+    // renderer would fall silent without anything appearing to break — the exact
+    // failure this logging exists to rule out.
+    win.webContents.on('console-message', (details) => {
+        console.log('[renderer]', details.message);
+    });
+    // The two ends of the symptom this instrumentation exists for. `unresponsive`
+    // is the window the desktop has started greying out; `render-process-gone` is
+    // the renderer having actually died, which is a different failure that looks
+    // similar from the outside. Only recorded here: what to *do* about either —
+    // offer a reload, reattach the panes — is a decision about the interface, not
+    // about diagnostics.
+    win.on('unresponsive', () => {
+        console.warn('[zerog] window unresponsive');
+    });
+    win.on('responsive', () => {
+        console.warn('[zerog] window responsive again');
+    });
+    win.webContents.on('render-process-gone', (_event, details) => {
+        console.error('[zerog] render-process-gone', details);
     });
     const devUrl = process.env.VITE_DEV_SERVER_URL;
     if (devUrl) {
@@ -400,6 +467,7 @@ app.whenReady().then(() => {
     // Keep the normal window chrome, but let the ZeroG UI occupy the full
     // client area instead of showing Electron's default File/Edit/etc. menu.
     Menu.setApplicationMenu(null);
+    watchEventLoop();
     createWindow();
     app.on('activate', () => {
         if (!BrowserWindow.getAllWindows().length)