@withbuddi/buddi 0.1.0-pre.35 → 0.1.0-pre.37

package/node_modules/real-require/package.json

@@ -1,6 +1,6 @@
 {
   "name": "real-require",
-  "version": "0.2.0",
+  "version": "1.0.0",
   "description": "Keep require and import consistent after bundling or transpiling",
   "author": "Paolo Insogna <shogun@cowtech.it>",
   "homepage": "https://github.com/pinojs/real-require",
@@ -23,27 +23,16 @@
     "src"
   ],
   "scripts": {
-    "format": "prettier -w src test",
-    "lint": "eslint src test",
-    "test": "c8 --reporter=text --reporter=html tap --reporter=spec --no-coverage test/*.test.js",
-    "test:watch": "tap --watch --reporter=spec --no-browser --coverage-report=text --coverage-report=html test/*.test.js",
-    "test:ci": "c8 --reporter=text --reporter=json --check-coverage --branches 90 --functions 90 --lines 90 --statements 90 tap --no-color --no-coverage test/*.test.js",
-    "ci": "npm run lint && npm run test:ci",
-    "prepublishOnly": "npm run ci",
-    "postpublish": "git push origin && git push origin -f --tags"
+    "lint": "eslint .",
+    "lint:fix": "eslint --fix .",
+    "test": "c8 --reporter=text --reporter=html borp 'test/*.test.js'",
+    "test:ci": "c8 --reporter=text --reporter=json --check-coverage --branches 90 --functions 90 --lines 90 --statements 90 borp 'test/*.test.js'",
+    "ci": "npm run lint && npm run test:ci"
   },
   "devDependencies": {
-    "eslint": "^7.12.0",
-    "eslint-config-standard": "^16.0.3",
-    "eslint-plugin-import": "^2.25.2",
-    "eslint-plugin-node": "^11.1.0",
-    "eslint-plugin-promise": "^5.1.1",
-    "eslint-plugin-standard": "^5.0.0",
-    "c8": "^7.10.0",
-    "prettier": "^2.4.1",
-    "tap": "^16.0.0"
-  },
-  "engines": {
-    "node": ">= 12.13.0"
+    "borp": "^1.0.0",
+    "c8": "^8.0.0",
+    "eslint": "^9.39.4",
+    "neostandard": "^0.13.0"
   }
 }

package/node_modules/real-require/src/index.js

@@ -1,9 +1,9 @@
-/* eslint-disable no-new-func, camelcase */
+/* eslint-disable no-new-func */
 /* globals __non_webpack__require__ */
 
 const realImport = new Function('modulePath', 'return import(modulePath)')
 
-function realRequire(modulePath) {
+function realRequire (modulePath) {
   if (typeof __non_webpack__require__ === 'function') {
     return __non_webpack__require__(modulePath)
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withbuddi/buddi",
-  "version": "0.1.0-pre.35",
+  "version": "0.1.0-pre.37",
   "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- Agents can write documents: with the new `artifacts.write` tool an agent saves a report (Markdown) or a table (CSV, or JSON rows) into Files, credited to it and the conversation; the same title again saves a new version. The Download in Files and on the file's canvas card becomes a menu, and buddi itself converts: Markdown to PDF or Word, a table to Excel. On Telegram a written document arrives as the .md and a PDF. A shipped skill, \"writing-a-document\", says when a file beats a chat answer and how to shape it. Files search also finds the label a document was filed under.\n\n- Telegram: \"Still useful?\" for a quiet watch now has Keep and Stop buttons, alone or after the end-of-day message. Only the owner's tap counts, a second tap says what already happened, and the message is edited to show the outcome.\n\n### Fixed\n\n- \"Still useful?\" is answered once: Keep then Stop on Telegram no longer switches the watch off, an old prompt's button no longer acts on a later question or a re-enabled watch, and a Telegram tap racing the dashboard's Keep or Stop applies only one of them. A later tap says what was decided; the dashboard's Stop answers the question too (`POST /api/missions/:id/still-useful`).\n- `artifacts.write` numbers versions over the whole conversation and under a lock: a report pushed out of the newest 100 files no longer comes back as `Report.md`, and two writes at once no longer both become `(v2)`. Bytes already in Files from another conversation are reported as already there instead of \"Saved\". Host API 1.25: `files.save` takes `version` and says `existed`.\n- A JSON table for `artifacts.write` is checked while it is read: thousands of objects with distinct keys are refused at the 201st column instead of building rows × keys cells first, and a row wider than its header is refused in every shape. A written document is at most 512 KiB.\n- Converting a document can no longer freeze or exhaust the gateway: PDF, Word and Excel are made in a worker thread with a memory limit, one at a time (a second download is told to retry in a few seconds), and stopped after 15 seconds. Markdown too deep, with too many parts or with runs of `*`/`_` that would take the reader minutes is refused at once, and so is a CSV whose ragged rows would pad to millions of cells; conversions take at most 512 KiB. On Telegram such a document arrives as its .md with a note instead of a PDF.\n- A document too large to convert still downloads: \"as written\" in the Download menu is the plain download, and the export route hands the stored format back at any size. A file whose contents are gone from disk answers 410 instead of an error.\n- `buddi status` (and every other command but `serve`) no longer prints \"agents: … has its own skill … it shadows the shared one\" above its output. The line stays in the gateway's log; a command shows it on stderr with `BUDDI_DEBUG=1`."
+    "notes": "### Added\n\n- Knowing you: Settings → Profile takes your full name, pronouns and birthday (day and month, the year optional) beside what the agents call you, and every agent is told them — and that today is your birthday when it is. On the day your front desk greets you first thing in your zone with a short note from the team, on Telegram and on Home under \"Happy birthday\", with a picture from your Illustrator when the image plugin has an account (on by default; the switch is on Missions).\n- People: the people in your life are their own kind of memory — who they are to you, how to address them, birthdays and anniversaries, a few notes — read by every agent in one line each and edited in Settings → Memory → People, with Forget and Undo. An agent keeps someone at once only when you told it about them in that message; otherwise you get a card to keep or discard. The people your existing notes already name are offered once, the same way. A person with a date can remind you a week before and on the day, with an offer to find something (off until you turn it on in their sheet).\n- The front desk and the Chief of Staff's morning brief read all-day \"Happy birthday!\", \"Anniversary\" and \"Marion's birthday\" events as occasions and say them in words, never as events with a time.\n- Agents decide when there is only one option and ask with buttons when there are a few: with one calendar they may change (or one mailbox, one account) they use it and say which; with two to six they ask with choices you tap in the chat, the corner chat or Telegram, never in prose; and they state the defaults they chose, such as two hours for a dinner, on the confirmation or the approval card. A question may now offer six choices.\n\n- Plugins can sign you in to an account with OAuth, starting with Google (host API 1.28): buddi opens Google's consent, catches the answer on this computer (or takes the address you paste back when your browser is on another one), keeps the tokens in Keys and secrets, renews them itself and sends them only to Google's API for that plugin. The plugin never sees a token; a sign-in Google stops accepting is reported as such.\n- Plugin pages can draw a choice per row (a segment such as Not linked · Read · Read and change, an option greyed with why), a grouped list whose heads carry the group's own actions, a row's colour as a dot, one button that opens a short menu of actions and forms, a card that finishes by itself once what it waits for arrives, and parts shown only when the dashboard is opened on this computer or only from elsewhere (host API 1.28). Settings → Calendar is the first page to use them.\n- A plugin's calendar page can open an event in a sheet on the right — when and how long, its calendar and colour, the place as a map link, the notes, a link to it in Google Calendar or iCloud — with Move or change… and Cancel…, which open the corner chat with the request written in for you to send; and it can say how many events the week holds beside its dates (host API 1.28).\n- Skills can be bundles: upload a `.zip` holding a SKILL.md with its scripts and assets (Agents → Skills → Upload). buddi checks it before keeping anything — 20 MB and 500 files at most, no paths that climb out, no links, nothing that runs outside `scripts/` — and shows what is inside, then the row says BUNDLE and who can run its scripts, and its sheet shows the files as a tree you can read (only SKILL.md is editable; Download gives the .zip back). Nothing in a bundle runs on upload. A script runs only when an agent holding host.exec runs it, never while the bundle is untrusted, asking you every time on a card that names the script, the bundle, the arguments, the working folder and what it may touch (Allow once only); it is confined (the macOS sandbox or bubblewrap on Linux): it writes only in its own folder, reads only the bundle, that folder and the system it runs on (nothing in your home), and has no network unless the bundle's SKILL.md says `network: true`, which its card then says. A shipped example, `examples/skills/letterhead`, shows a template bundle with no scripts.\n- The chat's composer styles what you type as you type it, and what is sent is the same plain Markdown: code and fenced blocks tinted with the block's language, bold, italic, headings, links and list markers. `@` in any chat offers who you can name with their faces (Agent Father borrowed for one message, or a teammate the agent asks for you; a group's members in a group) and draws the name as a chip; `/` at the start offers /use, /new, /stop and /quiet, then commands plugins add in their manifest (`commands`); lists carry on with Enter and indent with Tab; pasted code is fenced with Undo, and a paste over 4,000 characters becomes a file at once with \"Put it in the message\". On a phone the lists sit above the keyboard.\n\n- Agents try before they decline: every agent is told to look with the browser when it has one (your own browser where you are signed in, or buddi's with a login you stored in Keys and secrets, asking you to take over at a code it cannot answer), to hand a colleague's question to that colleague and relay the answer, and only then to say exactly what it lacks with one next step. An agent without the browser says it could look if you gave it browser control.\n- Catalogue agents can be given the browser's stored logins (`secret.list`, `secret.fill`) and colleagues to hand work to: a package's `delegates` resolve at install to the agents you have, an agent added later joins the lists that name it and the front desk's, and the approval card says who may ask whom.\n\n- A first run with no key at all: the **Ollama on this computer** card shows the command that installs Ollama (Homebrew or the app on a Mac, the official script on Linux; buddi never runs it), notices when Ollama starts, fetches the model your machine's memory suits (`qwen3:1.7b` to `qwen3:14b`) with a progress bar, makes the Ollama account and puts your assistant on it, so it answers before first run ends. It says plainly that a small local model is slower and weaker than Claude or ChatGPT, offers Ollama Cloud on a machine that would be slow, and Home's tip offers a stronger brain while any agent thinks with the local model.\n- `buddi doctor` has an `ollama` row: running with its version and models and which accounts use it, or a warning when an account uses it and Ollama is stopped or the account's model is not fetched.\n\n- Widgets in the market: Browse has a **Widgets** shelf beside All · Plugins · Agents with every widget a listed plugin brings, drawn as Home draws it from the plugin's sample data, and a listing's sheet shows each widget at every size it offers; Home's Add widgets and the lock screen's Add a widget end with **Get more widgets**. A plugin declares the sample as `preview` on a widget (one body, or one per size), `buddi plugins describe` now reports each widget (id, title, sizes, settings, preview) for the market's check, and a plugin that is only a widget is welcome.\n- A news edition in chat is drawn as an edition card: its name and time, the voice note as a waveform, its first sentence, each topic with its stories (the outlet's logo, the headline with Update or Opinion, Anchor's line, the outlet linked out and \"and N more\"), and the next edition's time. The text as sent is one tap away under \"Show as text\", and is what shows when News cannot read the edition back.\n\n- `pnpm review` for working on buddi: Codex reviews everything since the last release tag (from the Unreleased lines and a standard focus list) into a file, the script prints the brief for a second review agent, and `--merge` puts both reviews into one findings file.\n\n- Each story in a news edition card has its ways out under ⋯, as on the News page: Not interested, Mute an outlet, Quiet the topic for a week, Mute the topic. The story leaves a sentence and Undo in its place.\n\n### Changed\n\n…"
   },
   "files": [
     "packages",