@withbuddi/buddi 0.1.0-pre.52 → 0.1.0-pre.53

package/node_modules/process-warning/.github/workflows/lock-threads.yml

@@ -16,4 +16,4 @@ jobs:
     permissions:
       issues: write
       pull-requests: write
-    uses: fastify/workflows/.github/workflows/lock-threads.yml@2073dc8e1f9e172bf42daa3843c9dbd31af1e8cb # v6.0.0
+    uses: fastify/workflows/.github/workflows/lock-threads.yml@ef591e2186785d5ab36b9fe6a79c7ce2f1d94e57 # v7.0.0

package/node_modules/process-warning/.github/workflows/release.yml

@@ -0,0 +1,24 @@
+name: Release the package
+
+on:
+  workflow_dispatch:
+    inputs:
+      semver:
+        description: 'Release bump type'
+        required: true
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+
+permissions: {}
+
+jobs:
+  release:
+    permissions:
+      id-token: write # required for npm provenance via OIDC
+      contents: write # required to push the release commit and the tag
+    uses: fastify/workflows/.github/workflows/reusable-release.yml@b1a11bce713bc857e52b2231fec3c89071ad3135
+    with:
+      semver: ${{ inputs.semver }}

package/node_modules/process-warning/README.md

@@ -4,18 +4,18 @@
 [![NPM version](https://img.shields.io/npm/v/process-warning.svg?style=flat)](https://www.npmjs.com/package/process-warning)
 [![neostandard javascript style](https://img.shields.io/badge/code_style-neostandard-brightgreen?style=flat)](https://github.com/neostandard/neostandard)
 
-A small utility for generating consistent [warning objects](https://nodejs.org/api/process.html#event-warning) across your codebase.
+A small utility for generating consistent [warning objects](https://nodejs.org/api/process.html#event-warning) across a codebase.
 It also exposes a utility for emitting those warnings, guaranteeing that they are issued only once (unless configured otherwise).
 
-_This module is used by the [Fastify](https://fastify.dev) framework and it was called `fastify-warning` prior to version 1.0.0._
+_This module is used by the [Fastify](https://fastify.dev) framework, and it was called `fastify-warning` prior to version 1.0.0._
 
-### Install
+## Install
 
 ```
 npm i process-warning
 ```
 
-### Usage
+## Usage
 
 The module exports two builder functions for creating warnings.
 
@@ -34,35 +34,34 @@ const warning = createWarning({
 const emitted = warning('world')
 ```
 
-#### Methods
+### Methods
 
-##### `createWarning({ name, code, message[, unlimited] })`
+#### `createWarning({name, code, message[, unlimited]})`
 
-- `name` (`string`, required) - The error name, you can access it later with
-`error.name`. For consistency, we recommend prefixing module error names
-with `{YourModule}Warning`
-- `code` (`string`, required) - The warning code, you can access it later with
-`error.code`. For consistency, we recommend prefixing plugin error codes with
-`{ThreeLetterModuleName}_`, e.g. `FST_`. NOTE: codes should be all uppercase.
-- `message` (`string`, required) - The warning message. You can also use
-interpolated strings for formatting the message.
+- `name` (`string`, required) - The error name, accessible through
+`error.name`. For consistency, prefix module error names with
+`{ModuleName}Warning`.
+- `code` (`string`, required) - The warning code, accessible through
+`error.code`. For consistency, prefix plugin error codes with
+`{ThreeLetterModuleName}_`, e.g. `FST_`. Note: Codes should be all uppercase.
+- `message` (`string`, required) - The warning message. Interpolated strings
+can also be used to format the message.
 - `options` (`object`, optional) - Optional options with the following
 properties:
   + `unlimited` (`boolean`, optional) - Should the warning be emitted more than
   once? Defaults to `false`.
 
-
-##### `createDeprecation({code, message[, options]})`
+#### `createDeprecation({ code, message[, options] })`
 
 This is a wrapper for `createWarning`. It is equivalent to invoking
-`createWarning` with the `name` parameter set to "DeprecationWarning".
+`createWarning` with the `name` parameter set to `"DeprecationWarning"`.
 
 Deprecation warnings have extended support for the Node.js CLI options:
 `--throw-deprecation`, `--no-deprecation`, and `--trace-deprecation`.
 
-##### `warning([, a [, b [, c]]])`
+#### `warning([, a [, b [, c]]])`
 
-The returned `warning` function can used for emitting warnings.
+The returned `warning` function can be used to emit warnings.
 A warning is guaranteed to be emitted at least once.
 
 - `[, a [, b [, c]]]` (`any`, optional) - Parameters for string interpolation.
@@ -73,14 +72,16 @@ const FST_ERROR_CODE = createWarning({ name: 'MyAppWarning', code: 'FST_ERROR_CO
 FST_ERROR_CODE()
 ```
 
-How to use an interpolated string:
+Using an interpolated string:
+
 ```js
 const { createWarning } = require('process-warning')
 const FST_ERROR_CODE = createWarning({ name: 'MyAppWarning', code: 'FST_ERROR_CODE', message: 'Hello %s'})
 FST_ERROR_CODE('world')
 ```
 
-The `warning` object has methods and properties for managing the warning's state. Useful for testing.
+The `warning` object has methods and properties for managing the warning's state. These are useful for testing.
+
 ```js
 const { createWarning } = require('process-warning')
 const FST_ERROR_CODE = createWarning({ name: 'MyAppWarning', code: 'FST_ERROR_CODE', message: 'Hello %s'})
@@ -90,20 +91,21 @@ console.log(FST_ERROR_CODE.emitted) // true
 
 const FST_ERROR_CODE_2 = createWarning('MyAppWarning', 'FST_ERROR_CODE_2', 'Hello %s')
 FST_ERROR_CODE_2.emitted = true
-FST_ERROR_CODE_2('world') // will not be emitted because it is not unlimited
+FST_ERROR_CODE_2('world') // Will not be emitted because it is not unlimited
 ```
 
-How to use an unlimited warning:
+Using an unlimited warning:
+
 ```js
 const { createWarning } = require('process-warning')
 const FST_ERROR_CODE = createWarning({ name: 'MyAppWarning', code: 'FST_ERROR_CODE', message: 'Hello %s', unlimited: true })
-FST_ERROR_CODE('world') // will be emitted
-FST_ERROR_CODE('world') // will be emitted again
+FST_ERROR_CODE('world') // Will be emitted
+FST_ERROR_CODE('world') // Will be emitted again
 ```
 
 #### `spyWarning(warning)`
 
-Spy the created warning function for testing purpose.
+Spy on the created warning function for testing purposes.
 
 ```js
 const { test } = require('node:test')
@@ -113,45 +115,43 @@ const FST_ERROR_CODE = createWarning({ name: 'MyAppWarning', code: 'FST_ERROR_CO
 test('spy warning', t => {
   const spyData = spyWarning(FST_ERROR_CODE)
 
-  // call after spy
+  // Call after spying
   const emitted = FST_ERROR_CODE('world')
   t.assert.strictEqual(emitted, true)
 
-  // restore the warning function
-  // it must be called when you do not need to spy anymore
-  // otherwise, the calls data will accumulates.
+  // Restore the warning function
+  // This must be called when spying is no longer required
+  // Otherwise, the call data will accumulate
   t.after(() => spyData.restore())
 
   t.assert.strictEqual(FST_ERROR_CODE.emitted, true)
-  // calls return the arguments and result.
-  // result indicate whether warning is emitted through process.emitWarning
+  // `calls` contains the arguments and results
+  // `result` indicates whether the warning was emitted through `process.emitWarning`
   console.log(spyData.calls) // [{ arguments: ['world'], result: true }]
   t.assert.deepStrictEqual(spyData.calls[0].arguments, ['world'])
-  t.assert.strictEqual(spyData.calls[0].result,  true)
-  // number of times called the function
+  t.assert.strictEqual(spyData.calls[0].result, true)
+  // Number of times the function was called
   console.log(spyData.callCount()) // 1
-  t.assert.strictEqual(spyData.callCount(),  1)
+  t.assert.strictEqual(spyData.callCount(), 1)
 
-  // reset the spy stat and warning state
+  // Reset the spy statistics and warning state
   spyData.reset()
   t.assert.strictEqual(FST_ERROR_CODE.emitted, false)
   t.assert.deepStrictEqual(spyData.calls, [])
-  t.assert.strictEqual(spyData.callCount(),  0)
+  t.assert.strictEqual(spyData.callCount(), 0)
 })
 ```
 
-#### Suppressing warnings
-
-It is possible to suppress warnings by utilizing one of node's built-in warning suppression mechanisms.
+### Suppressing warnings
 
-Warnings can be suppressed:
+Warnings can be suppressed by using one of Node.js's built-in warning suppression mechanisms:
 
-- by setting the `NODE_NO_WARNINGS` environment variable to `1`
-- by passing the `--no-warnings` flag to the node process
-- by setting '--no-warnings' in the `NODE_OPTIONS` environment variable
+- Setting the `NODE_NO_WARNINGS` environment variable to `1`
+- Passing the `--no-warnings` flag to the Node.js process
+- Setting `--no-warnings` in the `NODE_OPTIONS` environment variable
 
-For more information see [node's documentation](https://nodejs.org/api/cli.html).
+For more information, see the [Node.js documentation](https://nodejs.org/api/cli.html).
 
 ## License
 
-Licensed under [MIT](./LICENSE).
+Licensed under [MIT](./LICENSE).

package/node_modules/process-warning/package.json

@@ -1,6 +1,6 @@
 {
   "name": "process-warning",
-  "version": "5.1.0",
+  "version": "5.1.1",
   "description": "A small utility for creating warnings and emitting them.",
   "main": "index.js",
   "type": "commonjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withbuddi/buddi",
-  "version": "0.1.0-pre.52",
+  "version": "0.1.0-pre.53",
   "type": "module",
   "description": "Your personal agents, on your computer",
   "repository": {
@@ -17,7 +17,7 @@
     "buddi": "packages/install/dist/launcher.js"
   },
   "buddi": {
-    "notes": "### Added\n\n- Secrets in the sign-in flow, in place: an agent on a sign-in form with nothing saved for the site calls `secret.request` and a card in the chat asks for the fields it saw (username, password), with the site as a chip. Save and fill saves them for that site and fills the form at once, one approval for the set; Save only saves and hands you the page; I'll sign in myself hands it over; More options opens a sheet beside the page with a code field and more fields. The agent hears only the names saved and whether the form was filled. The thread says \"Filled username and password on wikipedia.org\", and Keys and secrets links each saved secret back to its conversation. On Telegram the card says to open the dashboard, with Decline. `POST /api/secrets` saves a set for one site in one call; `POST /api/secrets/request/decline`.\n- Capture on the Page tab's window bar: a full-resolution PNG of the page as it is now (password fields masked), whoever holds it, saved to Files under the page's title and the time, with Open in Files. `POST /api/browser/capture`.\n- A page in your Chrome is live on the Canvas: the extension paints the agent's background tab (focus emulated, so a hidden tab paints) two frames a second while the agent works, and Take over is the remote hand there as in buddi's own browser, from your phone or any other device: the picture at the link's quality (sharp, normal, fast), clicks, wheel, keys, paste, copy (never a password field) and the window's back, forward, reload and address. **Bring the tab to the front** is the secondary action in the bar for when you are at the computer (`POST /api/browser/front`), and Capture works there too. Chrome's \"buddi started debugging this browser\" bar shows while a page is open; it goes when the page closes or you close the tab. Frames cross the extension socket as binary messages.\n- One extension, several buddis: the popup lists every buddi this Chrome works for, each with its name (from its handshake: `buddi`, `buddi-dev`), address, colour, state and a switch, plus **Add a buddi** and **Remove** per row. Each buddi has its own socket, pairing code and tab groups, named after it in its colour, and a tab belongs to exactly one of them. An existing pairing becomes the first buddi, switched on. A buddi that answers and turns this browser away (paired with another copy of the extension) says so instead of *did not answer*, and is not retried until you press Try again; a token it no longer takes is dropped for a fresh code; retries back off to 30 seconds and the popup no longer flickers; a buddi from before this release connects and says *older buddi: live view off*. Settings → Browser & apps says *paired with this buddi and 1 other* instead of asking to re-point the extension, and *off in Chrome* for a buddi switched off there.\n\n### Changed\n\n- A `secret.fill` for a site with nothing saved now tells the agent to ask with the sign-in card (`secret.request`) instead of asking you in chat where the password is; a set of secrets saved together asks once for the set the first time an agent fills it there, not once per field.\n- The Canvas no longer takes the screen from a live page. While an agent has a page open in the conversation the Page tab stays in front: results open behind it with a quiet dot that clears when you open them, and only the agent's own `canvas.show` brings something forward (on a phone the sheet behaves as before). Only results with a view open a tab at all (tables, lists, charts, stories, documents, diffs, pictures, audio, previews, terminal output, a structured result with real content); a browser step, a `secret.*` fill or list, a `mission.*` report and `owner.notify` stay in their chat row, which still opens them on the canvas. When you start a new turn, the previous turn's tabs fold into the **N more** menu unless you opened them yourself.\n- The live picture of a page you hold gets sharp on a link that keeps up: after a few seconds of frames going out promptly it grows to the page's own size (up to 1440×900) at JPEG quality 70, and steps back down on lag, waiting longer each time before trying again. The window bar says *sharp* or *fast*.\n\n### Fixed\n\n- Save and fill no longer types a password into the wrong element: fields are filled by their label on the latest page (Wikipedia's login redraws after the first fill and its refs land on the Appearance radios), a ref that names a radio, checkbox or button is refused before anything is entered, and the agent is told to observe once and fill again by label before asking you; afterwards it presses the form's sign-in button itself.\n- A login wall in buddi's browser now raises the sign-in card (the fields in the card, Save and fill, with Use my Chrome beside it when that route exists) instead of the old card whose \"Save a login for next time\" sent you to Settings; a code page's card opens the sign-in card in place. A tool call the turn never ran because it stopped on a card first reads \"not run\" instead of failed.\n- Give it back starts a turn only when an agent was waiting on the page (its card was answered with Take over, the take-over interrupted it, or it tried to act while you held the page). A page taken from an idle conversation is given back with the \"Gave the page back\" stamp and no model call.\n- Take over and Give it back no longer flash or take the page back by themselves: the Page tab ignores a status still in flight for a page it just gave back or stopped, keeps its buttons asleep until the status after the action has arrived, and keeps showing the last picture the hand drew instead of an empty frame.\n- Scrolling a page you hold no longer shakes: the wheel goes to the host once per animation frame with its deltas summed, frames are drawn in the order they came (an older one finishing its decode late is dropped), a frame that only scrolls back against your gesture waits until the gesture ends, and the dashboard no longer scrolls under the picture.\n- Cmd/Ctrl+C and Cmd/Ctrl+V work on a page you hold. Copy puts the host page's selection (or the focused field's, never a password field's) on your own clipboard instead of the headless browser's; paste fires again on macOS Chrome, where the shortcut's keydown was being cancelled before the browser could paste.\n- A question can always be answered from the chat: it now stands above any approval waiting there instead of behind it, and an approval decided elsewhere, expired, or an owner secret's use that went through (`secret.fill`) leaves the dock instead of hiding the question and the composer behind a card that drew nothing."
+    "notes": "### Added\n\n- Linux installs with one command and nothing from the host: `curl -fsSL https://withbuddi.com/install.sh | sh` (or `wget -qO-`) downloads `buddi-<version>-linux-<x64|arm64>.tar.gz` from the GitHub release (the Node buddi.app pins with npm beside it, the npm release, its embedded Postgres), checks its sha256, and installs it under `~/.local/share/buddi` with `buddi` in `~/.local/bin`, no sudo: a systemd user unit, lingering turned on when the system allows it (else the one sudo line), the dashboard link at the end. Running it again upgrades with a backup first and goes back if the new release does not start; updates from the dashboard or `buddi upgrade` go into `releases/` as in buddi.app; `buddi uninstall` removes the runtime, the releases, the command and the lingering too, keeping the last backup and its passphrase. An npm install in the same folder moves over with its data. The release workflow builds, smoke-installs and attaches both tarballs.\n- A desktop app for Linux, `buddi-desktop` (a .deb and an AppImage per architecture on the GitHub release; Tauri on WebKitGTK): the dashboard in its own window and a tray icon whose menu is buddi.app's (Open buddi, New Conversation, Settings…, Update to / Check for Updates…, Restart, Stop/Start, Lock, Start at Login, Advanced ▸ Open in Browser, Show Logs, Restart with the Previous Version…, Help, About, Uninstall buddi…, Quit), with New Conversation, Check for Updates and Lock on the launcher's right-click too, around the buddi `install.sh` installed, starting in the tray at login. It signs in with `buddi`'s link, shows \"Starting buddi…\" while the gateway restarts and comes back on the same page, gets a fresh link when the session expired, and shows the install line when `buddi` is missing. The microphone, notifications and the app's own calls are for the dashboard's exact origin only (another local port, such as a preview, opens in the browser); links leave for the browser on a click, http(s) only and rate-limited; downloads go to ~/Downloads. `install.sh` adds buddi to the app grid (the desktop app when it is installed, else the dashboard in the browser) and, with the desktop app installed, to autostart; `buddi uninstall` removes both.\n- `buddi doctor` says which Node runs buddi and which npm plugin installs use: the bundled runtime (buddi.app, the Linux install) or the machine's own.\n\n### Fixed\n\n- Settings → System and the owner menu say \"this computer\" instead of \"this Mac\" when buddi runs on Linux: \"Remove buddi from this computer?\", and the passphrase leaves \"buddi’s secret store\" rather than \"this Mac’s keychain\"."
   },
   "files": [
     "packages",