@paigy/harness 0.3.7 → 0.3.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +3 -1
  2. package/dist/cli.js +142 -346
  3. package/dist/main.js +221 -454
  4. package/package.json +13 -12
package/README.md CHANGED
@@ -236,7 +236,9 @@ which still belongs to paigy-listen).
236
236
  ## The window is not distributable (yet)
237
237
 
238
238
  npm is the ONLY shipping channel: `@paigy/harness` installs the CLI and the whole
239
- bridge, and updates with `npm i -g @paigy/harness@latest`. The Electron window runs
239
+ bridge. The host service updates itself once no session is running (`src/update.ts`), and
240
+ re-running `curl -fsSL https://paigy.ai/install | sh` updates it on demand and restarts it —
241
+ a bare `npm i -g` leaves the running host on the old code. The Electron window runs
240
242
  from source (`electron .`) — there is no packaging, no Developer ID signing or
241
243
  notarization, and therefore no auto-update (macOS auto-update requires the signing).
242
244
  A downloaded unsigned app would hit Gatekeeper's "damaged" dialog, which is worse