@withbuddi/buddi 0.1.0-pre.36 → 0.1.0-pre.38

package/node_modules/imapflow/dist/cjs/commands/store.js

@@ -31,8 +31,11 @@ async function store(connection, range, flags, options) {
     else if (options.silent) {
         operation = `${operation}.SILENT`;
     }
+    // Normalized once: the raw value is also compared below, and a mixed-case 'SET' must not
+    // take the set branch here and the add branch there.
+    const operationName = (options.operation || '').toLowerCase();
     // Prefix determines the operation: none = set (replace), + = add, - = remove
-    switch ((options.operation || '').toLowerCase()) {
+    switch (operationName) {
         case 'set':
             break;
         case 'remove':
@@ -43,20 +46,42 @@ async function store(connection, range, flags, options) {
             operation = `+${operation}`;
             break;
     }
-    // Validate each flag: format it (normalize backslash prefix for system flags),
-    // then check if the mailbox's permanentFlags allow it. Removal is always allowed
+    // Only an explicitly empty array asks for every flag to be cleared. A missing value is not
+    // that request, and neither is a 'set' whose flags all get dropped below: either would
+    // compile to "FLAGS ()" and wipe the message instead of storing what was asked for. The
+    // line is drawn at destroying flags, not at fidelity, so a set that keeps some of the
+    // requested flags still runs, as the documented contract for those methods says.
+    const clearAll = operationName === 'set' && Array.isArray(flags) && !flags.length;
+    // permanentFlags lists the IMAP keywords the mailbox accepts and says nothing about Gmail
+    // labels, so it is not consulted for X-GM-LABELS - the same reason an unrelated mailbox's
+    // flags are not consulted for APPEND (issue #415).
+    const flagSource = options.useLabels ? false : mailbox;
+    // Validate each flag: format it (normalize backslash prefix for system flags, reject the
+    // server-owned \Recent), then check that the mailbox allows it. Removal is always allowed
     // since it doesn't require the flag to be in permanentFlags.
+    const dropped = [];
     flags = (Array.isArray(flags) ? flags : [].concat(flags || []))
         .map(flag => {
         let formatted = (0, tools_js_1.formatFlag)(flag);
-        if (!(0, tools_js_1.canUseFlag)(mailbox, formatted) && options.operation !== 'remove') {
+        if (!formatted || (!(0, tools_js_1.canUseFlag)(flagSource, formatted) && operationName !== 'remove')) {
+            dropped.push(flag);
             return false;
         }
         return formatted;
     })
         .filter((flag) => !!flag);
-    // Allow empty flags only for 'set' operation (which clears all flags)
-    if (!flags.length && options.operation !== 'set') {
+    // The caller is told nothing by the boolean this returns, so leave a trail for the flags
+    // that never reached the server.
+    if (dropped.length) {
+        connection.log.warn({
+            msg: 'Dropped flags the mailbox does not accept',
+            cid: connection.id,
+            path: mailbox.path,
+            operation,
+            dropped
+        });
+    }
+    if (!flags.length && !clearAll) {
         return false;
     }
     let attributes = [

package/node_modules/imapflow/dist/cjs/imap-flow.d.ts

@@ -356,7 +356,7 @@ export declare class ImapFlow extends EventEmitter {
      * Sets flags for a message or message range
      *
      * @param range Range to filter the messages
-     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored
+     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored. An empty array clears every flag, but a non-empty array with nothing usable in it is refused rather than clearing the message
      * @param options Store options
      * @returns Did the operation succeed or not
      *

package/node_modules/imapflow/dist/cjs/imap-flow.js

@@ -2631,7 +2631,7 @@ class ImapFlow extends node_events_1.EventEmitter {
      * Sets flags for a message or message range
      *
      * @param range Range to filter the messages
-     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored
+     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored. An empty array clears every flag, but a non-empty array with nothing usable in it is refused rather than clearing the message
      * @param options Store options
      * @returns Did the operation succeed or not
      *

package/node_modules/imapflow/dist/cjs/package-info.d.ts

@@ -1,3 +1,3 @@
 export declare const name = "imapflow";
-export declare const version = "2.2.1";
+export declare const version = "2.2.4";
 export declare const homepage = "https://imapflow.com/";

package/node_modules/imapflow/dist/cjs/package-info.js

@@ -3,5 +3,5 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.homepage = exports.version = exports.name = void 0;
 exports.name = "imapflow";
-exports.version = "2.2.1";
+exports.version = "2.2.4";
 exports.homepage = "https://imapflow.com/";

package/node_modules/imapflow/dist/cjs/search-compiler.js

@@ -3,6 +3,8 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.searchCompiler = void 0;
 const tools_js_1 = require("./tools.js");
+// Matches any character outside the ASCII range
+const UNICODE_PATTERN = /[^\x00-\x7F]/;
 /**
  * Sets a boolean flag in the IMAP search attributes.
  * Automatically handles UN- prefixing for falsy values.
@@ -38,6 +40,17 @@ let setBoolOpt = (attributes, term, value) => {
  * @returns The joined sequence set string
  */
 let toSequenceValue = (value) => [].concat(value).join(',');
+/**
+ * Builds the token for a search value. A quoted string may only carry 7-bit
+ * characters (RFC 3501 section 9), so a non-ASCII value is sent as a literal;
+ * strict servers reply BAD to UTF-8 inside a quoted string. A literal can not
+ * carry NUL either (CHAR8 is %x01-ff), so such a value stays an ATOM and the
+ * compiler rejects it.
+ *
+ * @param value - The search value
+ * @returns An ATOM token (quoted by the compiler when needed), or a LITERAL token
+ */
+let toSearchValue = (value) => UNICODE_PATTERN.test(value) && !value.includes('\0') ? { type: 'LITERAL', value: Buffer.from(value) } : { type: 'ATOM', value };
 /**
  * Adds a search option with its value(s) to the attributes array.
  * Handles NOT operations and array values.
@@ -54,10 +67,10 @@ let setOpt = (attributes, term, value) => {
     attributes.push({ type: 'ATOM', value: term.toUpperCase() });
     // Handle array values (e.g. HEADER name/value pairs)
     if (Array.isArray(value)) {
-        value.forEach(entry => attributes.push({ type: 'ATOM', value: (entry || '').toString() }));
+        value.forEach(entry => attributes.push(toSearchValue((entry || '').toString())));
     }
     else {
-        attributes.push({ type: 'ATOM', value: value.toString() });
+        attributes.push(toSearchValue(value.toString()));
     }
 };
 /**
@@ -89,8 +102,6 @@ let processDateField = (attributes, term, value) => {
     }
     setOpt(attributes, term, formatted);
 };
-// Pre-compiled regex for better performance
-const UNICODE_PATTERN = /[^\x00-\x7F]/;
 /**
  * Throws a coded search compilation error.
  *
@@ -103,20 +114,13 @@ let fail = (code, message) => {
     throw error;
 };
 /**
- * Checks if a string contains Unicode characters.
- * Used to determine if CHARSET UTF-8 needs to be specified.
+ * Checks whether any search value was compiled into a literal, which only
+ * happens for non-ASCII values and means CHARSET UTF-8 needs to be specified.
  *
- * @param str - String to check
- * @returns True if string contains non-ASCII characters
+ * @param attributes - Compiled search attributes
+ * @returns True if a LITERAL token is present
  */
-let isUnicodeString = (str) => {
-    if (!str || typeof str !== 'string') {
-        return false;
-    }
-    // Regex test is ~3-5x faster than Buffer.byteLength
-    // Matches any character outside ASCII range (0x00-0x7F)
-    return UNICODE_PATTERN.test(str);
-};
+let hasLiteral = (attributes) => attributes.some(attr => (Array.isArray(attr) ? hasLiteral(attr) : attr.type === 'LITERAL'));
 /**
  * Compiles a JavaScript object query into IMAP search command attributes.
  * Supports standard IMAP search criteria and extensions like OBJECTID and Gmail extensions.
@@ -145,8 +149,6 @@ let isUnicodeString = (str) => {
  */
 const searchCompiler = (connection, query) => {
     const attributes = [];
-    // Track if we need to specify UTF-8 charset
-    let hasUnicode = false;
     /**
      * Recursively walks through the query object and builds IMAP attributes.
      * @param params - Query parameters to process
@@ -236,9 +238,6 @@ const searchCompiler = (connection, query) => {
                 case 'SUBJECT':
                 case 'TEXT':
                 case 'TO':
-                    if (isUnicodeString(params[term])) {
-                        hasUnicode = true;
-                    }
                     if (params[term]) {
                         setOpt(attributes, term, params[term]);
                     }
@@ -286,9 +285,6 @@ const searchCompiler = (connection, query) => {
                 case 'GMRAW':
                 case 'GMAILRAW': // alias for GMRAW
                     if (connection.capabilities.has('X-GM-EXT-1')) {
-                        if (isUnicodeString(params[term])) {
-                            hasUnicode = true;
-                        }
                         setOpt(attributes, 'X-GM-RAW', params[term]);
                     }
                     else {
@@ -329,9 +325,6 @@ const searchCompiler = (connection, query) => {
                         fail('MissingServerExtension', 'Server does not support X-GM-EXT-1 extension required for label search');
                     }
                     let rawQuery = rawParts.join(' ');
-                    if (isUnicodeString(rawQuery)) {
-                        hasUnicode = true;
-                    }
                     setOpt(attributes, 'X-GM-RAW', rawQuery);
                     break;
                 }
@@ -391,9 +384,6 @@ const searchCompiler = (connection, query) => {
                             if (typeof value !== 'string') {
                                 return;
                             }
-                            if (isUnicodeString(value)) {
-                                hasUnicode = true;
-                            }
                             setOpt(attributes, term, [header.toUpperCase().trim(), value]);
                         });
                     }
@@ -473,7 +463,7 @@ const searchCompiler = (connection, query) => {
     walk(query);
     // If we encountered Unicode strings and UTF-8 is not already accepted,
     // prepend CHARSET UTF-8 to the search command
-    if (hasUnicode && !connection.enabled.has('UTF8=ACCEPT')) {
+    if (!connection.enabled.has('UTF8=ACCEPT') && hasLiteral(attributes)) {
         attributes.unshift({ type: 'ATOM', value: 'UTF-8' });
         attributes.unshift({ type: 'ATOM', value: 'CHARSET' });
     }

package/node_modules/imapflow/dist/esm/commands/append.js

@@ -34,10 +34,34 @@ export default async function append(connection, destination, content, flags, id
     let selected = getSelectedMailbox(connection);
     // The selected mailbox when appending to it, false otherwise
     const targetMailbox = selected && comparePaths(connection, selected.path, destination) ? selected : false;
-    // Validate and format flags. Only flags allowed by the mailbox's permanentFlags are included.
+    // Flags are only filtered when a read-write selection of the destination itself says what it
+    // accepts: the permanentFlags of an unrelated mailbox say nothing about the destination, and a
+    // read-only selection reports an empty PERMANENTFLAGS list (Dovecot does), which canUseFlag()
+    // reads as deny-all. Otherwise they go to the server unfiltered and it decides (RFC 9051).
+    const flagSource = targetMailbox && !targetMailbox.readOnly ? targetMailbox : false;
+    const dropped = [];
     flags = (Array.isArray(flags) ? flags : [].concat(flags || []))
-        .map(flag => flag && formatFlag(flag.toString()))
-        .filter((flag) => !!flag && canUseFlag(connection.mailbox, flag));
+        .map(flag => {
+        const formatted = flag && formatFlag(flag.toString());
+        if (!formatted || !canUseFlag(flagSource, formatted)) {
+            if (flag) {
+                dropped.push(flag.toString());
+            }
+            return false;
+        }
+        return formatted;
+    })
+        .filter((flag) => !!flag);
+    // The stored message simply ends up without them, and the caller is told nothing, so leave
+    // a trail for the flags that never reached the server.
+    if (dropped.length) {
+        connection.log.warn({
+            msg: 'Dropped flags the mailbox does not accept',
+            cid: connection.id,
+            path: destination,
+            dropped
+        });
+    }
     // APPEND command format: APPEND <mailbox> [<flags>] [<date-time>] <literal>
     let attributes = [{ type: 'ATOM', value: encodePath(connection, destination) }];
     // Internal date: the date the server should record for this message.

package/node_modules/imapflow/dist/esm/commands/store.js

@@ -28,8 +28,11 @@ export default async function store(connection, range, flags, options) {
     else if (options.silent) {
         operation = `${operation}.SILENT`;
     }
+    // Normalized once: the raw value is also compared below, and a mixed-case 'SET' must not
+    // take the set branch here and the add branch there.
+    const operationName = (options.operation || '').toLowerCase();
     // Prefix determines the operation: none = set (replace), + = add, - = remove
-    switch ((options.operation || '').toLowerCase()) {
+    switch (operationName) {
         case 'set':
             break;
         case 'remove':
@@ -40,20 +43,42 @@ export default async function store(connection, range, flags, options) {
             operation = `+${operation}`;
             break;
     }
-    // Validate each flag: format it (normalize backslash prefix for system flags),
-    // then check if the mailbox's permanentFlags allow it. Removal is always allowed
+    // Only an explicitly empty array asks for every flag to be cleared. A missing value is not
+    // that request, and neither is a 'set' whose flags all get dropped below: either would
+    // compile to "FLAGS ()" and wipe the message instead of storing what was asked for. The
+    // line is drawn at destroying flags, not at fidelity, so a set that keeps some of the
+    // requested flags still runs, as the documented contract for those methods says.
+    const clearAll = operationName === 'set' && Array.isArray(flags) && !flags.length;
+    // permanentFlags lists the IMAP keywords the mailbox accepts and says nothing about Gmail
+    // labels, so it is not consulted for X-GM-LABELS - the same reason an unrelated mailbox's
+    // flags are not consulted for APPEND (issue #415).
+    const flagSource = options.useLabels ? false : mailbox;
+    // Validate each flag: format it (normalize backslash prefix for system flags, reject the
+    // server-owned \Recent), then check that the mailbox allows it. Removal is always allowed
     // since it doesn't require the flag to be in permanentFlags.
+    const dropped = [];
     flags = (Array.isArray(flags) ? flags : [].concat(flags || []))
         .map(flag => {
         let formatted = formatFlag(flag);
-        if (!canUseFlag(mailbox, formatted) && options.operation !== 'remove') {
+        if (!formatted || (!canUseFlag(flagSource, formatted) && operationName !== 'remove')) {
+            dropped.push(flag);
             return false;
         }
         return formatted;
     })
         .filter((flag) => !!flag);
-    // Allow empty flags only for 'set' operation (which clears all flags)
-    if (!flags.length && options.operation !== 'set') {
+    // The caller is told nothing by the boolean this returns, so leave a trail for the flags
+    // that never reached the server.
+    if (dropped.length) {
+        connection.log.warn({
+            msg: 'Dropped flags the mailbox does not accept',
+            cid: connection.id,
+            path: mailbox.path,
+            operation,
+            dropped
+        });
+    }
+    if (!flags.length && !clearAll) {
         return false;
     }
     let attributes = [

package/node_modules/imapflow/dist/esm/imap-flow.d.ts

@@ -356,7 +356,7 @@ export declare class ImapFlow extends EventEmitter {
      * Sets flags for a message or message range
      *
      * @param range Range to filter the messages
-     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored
+     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored. An empty array clears every flag, but a non-empty array with nothing usable in it is refused rather than clearing the message
      * @param options Store options
      * @returns Did the operation succeed or not
      *

package/node_modules/imapflow/dist/esm/imap-flow.js

@@ -2590,7 +2590,7 @@ export class ImapFlow extends EventEmitter {
      * Sets flags for a message or message range
      *
      * @param range Range to filter the messages
-     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored
+     * @param flags Array of flags to set. Only flags that are permitted to set are used, other flags are ignored. An empty array clears every flag, but a non-empty array with nothing usable in it is refused rather than clearing the message
      * @param options Store options
      * @returns Did the operation succeed or not
      *

package/node_modules/imapflow/dist/esm/package-info.d.ts

@@ -1,3 +1,3 @@
 export declare const name = "imapflow";
-export declare const version = "2.2.1";
+export declare const version = "2.2.4";
 export declare const homepage = "https://imapflow.com/";

package/node_modules/imapflow/dist/esm/package-info.js

@@ -1,4 +1,4 @@
 // Generated by scripts/build.js from package.json. Do not edit by hand.
 export const name = "imapflow";
-export const version = "2.2.1";
+export const version = "2.2.4";
 export const homepage = "https://imapflow.com/";

package/node_modules/imapflow/dist/esm/search-compiler.js

@@ -1,5 +1,7 @@
 /* eslint no-control-regex:0 */
 import { formatDate, formatFlag, toValidDate, isRev2Active } from './tools.js';
+// Matches any character outside the ASCII range
+const UNICODE_PATTERN = /[^\x00-\x7F]/;
 /**
  * Sets a boolean flag in the IMAP search attributes.
  * Automatically handles UN- prefixing for falsy values.
@@ -35,6 +37,17 @@ let setBoolOpt = (attributes, term, value) => {
  * @returns The joined sequence set string
  */
 let toSequenceValue = (value) => [].concat(value).join(',');
+/**
+ * Builds the token for a search value. A quoted string may only carry 7-bit
+ * characters (RFC 3501 section 9), so a non-ASCII value is sent as a literal;
+ * strict servers reply BAD to UTF-8 inside a quoted string. A literal can not
+ * carry NUL either (CHAR8 is %x01-ff), so such a value stays an ATOM and the
+ * compiler rejects it.
+ *
+ * @param value - The search value
+ * @returns An ATOM token (quoted by the compiler when needed), or a LITERAL token
+ */
+let toSearchValue = (value) => UNICODE_PATTERN.test(value) && !value.includes('\0') ? { type: 'LITERAL', value: Buffer.from(value) } : { type: 'ATOM', value };
 /**
  * Adds a search option with its value(s) to the attributes array.
  * Handles NOT operations and array values.
@@ -51,10 +64,10 @@ let setOpt = (attributes, term, value) => {
     attributes.push({ type: 'ATOM', value: term.toUpperCase() });
     // Handle array values (e.g. HEADER name/value pairs)
     if (Array.isArray(value)) {
-        value.forEach(entry => attributes.push({ type: 'ATOM', value: (entry || '').toString() }));
+        value.forEach(entry => attributes.push(toSearchValue((entry || '').toString())));
     }
     else {
-        attributes.push({ type: 'ATOM', value: value.toString() });
+        attributes.push(toSearchValue(value.toString()));
     }
 };
 /**
@@ -86,8 +99,6 @@ let processDateField = (attributes, term, value) => {
     }
     setOpt(attributes, term, formatted);
 };
-// Pre-compiled regex for better performance
-const UNICODE_PATTERN = /[^\x00-\x7F]/;
 /**
  * Throws a coded search compilation error.
  *
@@ -100,20 +111,13 @@ let fail = (code, message) => {
     throw error;
 };
 /**
- * Checks if a string contains Unicode characters.
- * Used to determine if CHARSET UTF-8 needs to be specified.
+ * Checks whether any search value was compiled into a literal, which only
+ * happens for non-ASCII values and means CHARSET UTF-8 needs to be specified.
  *
- * @param str - String to check
- * @returns True if string contains non-ASCII characters
+ * @param attributes - Compiled search attributes
+ * @returns True if a LITERAL token is present
  */
-let isUnicodeString = (str) => {
-    if (!str || typeof str !== 'string') {
-        return false;
-    }
-    // Regex test is ~3-5x faster than Buffer.byteLength
-    // Matches any character outside ASCII range (0x00-0x7F)
-    return UNICODE_PATTERN.test(str);
-};
+let hasLiteral = (attributes) => attributes.some(attr => (Array.isArray(attr) ? hasLiteral(attr) : attr.type === 'LITERAL'));
 /**
  * Compiles a JavaScript object query into IMAP search command attributes.
  * Supports standard IMAP search criteria and extensions like OBJECTID and Gmail extensions.
@@ -142,8 +146,6 @@ let isUnicodeString = (str) => {
  */
 export const searchCompiler = (connection, query) => {
     const attributes = [];
-    // Track if we need to specify UTF-8 charset
-    let hasUnicode = false;
     /**
      * Recursively walks through the query object and builds IMAP attributes.
      * @param params - Query parameters to process
@@ -233,9 +235,6 @@ export const searchCompiler = (connection, query) => {
                 case 'SUBJECT':
                 case 'TEXT':
                 case 'TO':
-                    if (isUnicodeString(params[term])) {
-                        hasUnicode = true;
-                    }
                     if (params[term]) {
                         setOpt(attributes, term, params[term]);
                     }
@@ -283,9 +282,6 @@ export const searchCompiler = (connection, query) => {
                 case 'GMRAW':
                 case 'GMAILRAW': // alias for GMRAW
                     if (connection.capabilities.has('X-GM-EXT-1')) {
-                        if (isUnicodeString(params[term])) {
-                            hasUnicode = true;
-                        }
                         setOpt(attributes, 'X-GM-RAW', params[term]);
                     }
                     else {
@@ -326,9 +322,6 @@ export const searchCompiler = (connection, query) => {
                         fail('MissingServerExtension', 'Server does not support X-GM-EXT-1 extension required for label search');
                     }
                     let rawQuery = rawParts.join(' ');
-                    if (isUnicodeString(rawQuery)) {
-                        hasUnicode = true;
-                    }
                     setOpt(attributes, 'X-GM-RAW', rawQuery);
                     break;
                 }
@@ -388,9 +381,6 @@ export const searchCompiler = (connection, query) => {
                             if (typeof value !== 'string') {
                                 return;
                             }
-                            if (isUnicodeString(value)) {
-                                hasUnicode = true;
-                            }
                             setOpt(attributes, term, [header.toUpperCase().trim(), value]);
                         });
                     }
@@ -470,7 +460,7 @@ export const searchCompiler = (connection, query) => {
     walk(query);
     // If we encountered Unicode strings and UTF-8 is not already accepted,
     // prepend CHARSET UTF-8 to the search command
-    if (hasUnicode && !connection.enabled.has('UTF8=ACCEPT')) {
+    if (!connection.enabled.has('UTF8=ACCEPT') && hasLiteral(attributes)) {
         attributes.unshift({ type: 'ATOM', value: 'UTF-8' });
         attributes.unshift({ type: 'ATOM', value: 'CHARSET' });
     }

package/node_modules/imapflow/package.json

@@ -1,6 +1,6 @@
 {
     "name": "imapflow",
-    "version": "2.2.1",
+    "version": "2.2.4",
     "description": "IMAP Client for Node",
     "type": "module",
     "main": "./dist/cjs/imap-flow.js",
@@ -70,7 +70,7 @@
     "devDependencies": {
         "@types/node": "20.19.43",
         "c8": "12.0.0",
-        "eslint": "10.11.0",
+        "eslint": "10.12.0",
         "eslint-config-prettier": "10.1.8",
         "globals": "17.13.0",
         "prettier": "3.9.9",
@@ -78,7 +78,7 @@
         "types-node-legacy": "npm:@types/node@20.0.0",
         "typescript": "6.0.3",
         "typescript-eslint": "8.71.0",
-        "wrangler": "4.145.0"
+        "wrangler": "4.147.0"
     },
     "dependencies": {
         "@zone-eu/mailsplit": "5.4.19",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withbuddi/buddi",
-  "version": "0.1.0-pre.36",
+  "version": "0.1.0-pre.38",
   "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- Two scripts for working on buddi: `pnpm test:db` runs the suites against a throwaway Postgres in Docker (migrated first, removed afterwards, never the dev database), and `pnpm release pre.N` cuts a release: stamps new API routes, dates the changelog, refreshes the API and CLI pages, commits, tags and pushes.\n- Plugins can sign in to a CalDAV or WebDAV account without holding its password (host API 1.26): the password is an owner secret bound to the plugin and the account's host, and buddi itself adds the sign-in to the plugin's requests, for the calendar verbs only, with small bodies, capped answers and at most 120 requests a minute. Settings → Secrets shows such a password under its plugin, as \"A plugin’s sign-in\".\n- A plugin page's table can show a row's own colour as a dot before a cell (`swatch`, host API 1.26): Settings → Calendar draws each account calendar's colour beside its name.\n- Plugins can keep small images they fetched, like an outlet's logo (host API 1.27, `assets`): buddi re-draws them as 64 and 128 px PNGs (SVG refused), serves them only to the signed-in dashboard, keeps at most 20 MB per plugin, and removes them with the plugin. The install card says \"keeps small images it fetched, like logos\".\n- Plugin pages can show logos on a list row (up to three overlapping, then \"Reuters and 3 more\", a letter when there is none) and on a widget's rows at medium size and on the lock screen, always from buddi and never from the outlet (host API 1.27).\n- A plugin page can link out to an article: the link opens in a new tab, with no referrer, and an outside-link mark (`href`, host API 1.27). The dashboard still loads nothing from outside buddi.\n- A mission can read a plugin's material before it runs (`context`, host API 1.27), so an edition is written in one model call; it can send a longer report (`reportMax`, up to 6,000 characters, split at paragraphs on Telegram); and its report can carry a dashboard link (\"Open edition\") and a voice note, which Telegram sends before the text and the chat plays above it.\n- Plugins can name plugins they work better with (`optional`, host API 1.27) and ask whether one is there (`ctx.buddi.plugins.has`), so a setting can say \"Needs Speech\" instead of failing.\n- A `news` page icon, a folded newspaper, for plugin pages (host API 1.27).\n- Plugin pages can draw a feed of stories as the News kit does (`stories`, host API 1.27): cards with their outlets' logos, quiet marks (Opinion, EN · FR, \"Told you · this morning\"), a ⋯ of ways out that leave \"Hidden · Undo\" in the card's place, groups with See all, and a sheet per story with its sources linked out and how it moved. Also: buttons in a page's head, topic chips with an add chip, a tab kept in a page parameter, a quiet one-line notice ending with a link, an intro read from the page's data, and list rows with a logo, a small tag, a status line and a ⋯ menu.\n- Widget lists can ask for five rows at medium and let a headline take two lines (`max`, `wrap`, host API 1.27), and draw a row's logo at small size too (a letter tile when the outlet has none); a widget set to several topics names itself after them (\"Top stories · AI, US politics\").\n\n### Changed\n\n- The catalogue update sheet shows where in the persona a change sits: each change comes with two lines of muted context and its line number, and the unchanged lines between changes fold into a \"⋯ 12 lines\" row. `buddi agents update` prints the same. `POST /api/catalogue/:name/update/plan` returns `personaDiff` as unified hunks (`@@ -a,b +c,d @@` and context lines).\n\n### Fixed\n\n- `buddi dashboard --unlock` no longer lands back on the lock screen when an older dashboard tab is open in the same browser: that tab's idle lock is refused for a session someone used more recently, and a tab only tells the others it locked once the server agrees.\n- A plugin's settings link without a tab (`#/settings/p.news`) opens the plugin's first settings tab instead of an empty page.\n- The npm release now ships the macOS computer helper behind \"Use my apps\" (a universal arm64 + x86_64 binary, signed ad hoc, built by a macOS job in the release workflow); before, a Mac installed from npm had none and Settings said \"Computer helper unavailable … ENOENT\".\n- Settings → Computer & browser no longer shows a red error when the computer helper is missing: the \"Use my apps\" choice carries one line saying so and how to fix it, and Check again answers instead of failing. `buddi doctor` prints a \"computer helper\" row on macOS (present, and its version).\n- Settings no longer asks to update the browser extension just because buddi's version differs from it (\"buddi is 0.1.0-pre.35; the extension is 0.1.0\"): it asks only when the extension is older than the minimum this buddi needs, which the store's current build meets.\n- A tool name in a catalogue listing's owner-facing text (pitch, description, about, what changed, examples, mission names, skill descriptions), such as \"(artifacts.write)\", is rewritten in words from the tool's description, or dropped, wherever buddi shows it.\n- A scheduled mission run now tells the agent its mission's own report cap (`reportMax`, such as 4,000 characters) instead of always 1,500, and that Telegram splits a message past 4,000 characters at paragraphs; a morning edition had dropped stories to fit the wrong limit.\n- A plugin request that carries an owner secret can no longer be steered to another server: caller-set `Host`, forwarding and `Proxy-Authorization` headers are dropped, and TLS always names the URL's own host. The sign-in budget (120 a minute) is now shared by every run of a plugin instead of reset per run, a refused or pending sign-in no longer uses it up, and a response cap that is not a whole number (`NaN`) falls back to the default instead of lifting the cap.\n- A plugin's logo can no longer exhaust buddi's memory: images are capped at a megapixel (2048 on a side) before any pixel buffer is made, a PNG with a second header or data that inflates past its own size is refused (also inside an ICO), a GIF frame must fit its canvas, and decoding runs one at a time in a worker thread with a memory limit and a five-second deadline.\n- A mission's material (`context`) now reaches its run between unique data markers, with the reminder that it is data after it; when the material cannot be read, the run gets a fixed sentence and at most 200 characters of the plugin's error, inside the same markers, instead of the whole error. A mission report's voice note is refused when the run has no conversation to prove it was made there.\n- A catalogue update now brings missions the agent already has the package's new material and report length (`context`, `reportMax`): the update sheet and the approval name each one (\"Morning edition: new settings — …\"), and approving changes just those two settings, never the mission's prompt, hour or switch. Before, installed missions kept their old settings for good.\n- The idle lock lands on time again: the page's claim says how long it saw no use, and the server allows for its own record trailing the use by up to 40 seconds, instead of refusing ordinary idle locks and leaving the lock to land at twice the delay.\n- Logos on the lock screen's widget rows draw instead of falling back to a letter: plugin assets are answered while locked."
+    "notes": "- Development: the web test suite runs in a fifth of the time (nwsapi pinned to 2.2.28; its older versions recursed on every menu open under jsdom), which also unsticks the release gate.\n- Cloudflare setup: after the token is checked, type just the name and pick the domain from your Cloudflare zones; the full hostname is still accepted when the token lists none.\n- Cloudflare setup: the Done line says Cloudflare needs a minute or two before the first sign-in works, and to reload if its page can’t find the application.\n- Trusted access: the Cloudflare \"Open Cloudflare\" button opens the token form pre-filled with the four permissions buddi needs (Cloudflare template URL); the owner names and creates the token, then pastes it.\n\n### Added\n\n- Sign in from your own domain through Cloudflare: Settings → System → Sign in from elsewhere → Cloudflare Access walks you through a Cloudflare Tunnel with Cloudflare Access in front (install cloudflared, create the tunnel, point a hostname at the port the panel prints, add an Access application for your email, paste the team domain and AUD tag), with Test my setup and a status line. buddi verifies Access's signed JWT itself on every request — signature against your team's keys, issuer, audience, expiry, your email — never trusts a plain header, and gives the same remote session as Tailscale (12 hours idle, CSRF, approvals, the lock screen). cloudflared points at a separate loopback port that is always treated as a visit from elsewhere, and failed sign-ins there — a stale cookie, or an Access assertion that doesn't verify, counted per visitor address — are counted apart from this computer's and your tailnet's. `buddi doctor` has a `cloudflare access` row.\n- `buddi doctor browser` and `GET /api/browser/telemetry`: the last week's browser stops by cause, cards and routes, so flakiness can be seen to fall; `buddi doctor` has a browser line too.\n- Missions can browse while you are away, in buddi's own browser only (never your Chrome or apps), when their catalogue package says `\"browser\": \"own\"`; the install card says so. When a mission meets a sign-in, a human check, an uncertain click or its budget, it waits for you with the same card, sent to Telegram with its buttons and held on Home and Needs you; your answer carries the run on where it stopped (an answer given the moment the card arrives counts too; Take over makes the run wait until you give the page back, then it carries on), and with no answer within an hour (`missionWaitMinutes` in the browser settings) it stops and tells you in one line. Browser telemetry rows mark mission runs.\n- A colleague an agent asks for help may use the browser too, but only when you are in the asking conversation and a page is already open there; a mission's colleague never does.\n- Plugins can provide the apps route (host API 1.29: `routes` in the manifest, with health and look/do handlers, plus `reach` for the owner's list of apps, take-over without a remote hand, and native typing for `secret.type`). Tools may stop a run on a result that needs the owner (`waitsForOwner` as a function), declare their own budget (`ownBudget`), and put one card in front of the owner (`ctx.ask`).\n- Cloudflare Access can set itself up: Set it up for me (or `buddi access cloudflare setup --host <hostname>`) takes one Cloudflare API token, kept as an owner secret, and makes the tunnel, its route to this computer, the DNS record and the Access application with an Allow policy for your email, fills in the settings, shows the one `sudo cloudflared service install …` line to run (buddi never runs sudo), waits for the tunnel to connect and tests it. Running it again reuses what it made, by the ids it recorded; something of buddi's name it didn't make stops the run with Use it anyway (`--adopt`) instead of being taken silently; one setup or removal runs at a time, and a setup for another hostname waits until what buddi made for the first is removed; a missing token permission is named; Remove what buddi made (or `buddi access cloudflare remove`) deletes only the objects buddi recorded making. The install line only ever holds a well-formed connector token.\n\n### Changed\n\n- The Cloudflare Access form says what is missing in a plain line until you try to turn it on, and its row no longer says Needs setup while it is off.\n- Tailscale sign-in is now one row of Settings → System → Sign in from elsewhere, beside Cloudflare Access; the panel, its `tailscale serve` line and how it checks you are unchanged, and existing Tailscale sessions carry over. `GET/PUT /api/tailscale` stay for one release as aliases of `/api/access/tailscale`.\n- The browser picks where to look for you instead of asking you to pick a mode: buddi's own browser for every page, in the background (headless, seen on the Canvas); your Chrome for sites that need your sign-in, in background tabs, when you allow it and it is connected; your apps only for app jobs. When a route is not there it falls back without stopping, and the chat says one line when the page was not in buddi's own browser (\"I used your Chrome because Amazon needs your sign-in.\"). A login wall in buddi's browser moves to your Chrome when it can, unless the conversation, the agent or your default keeps it in buddi's browser (then the card offers Use my Chrome instead), and the site is remembered.\n- Settings → Computer & browser is now **Where agents may look**: one row per route instead of mode radios — buddi's own browser (always on; ready, Install · 150 MB, the Linux sandbox command to copy, installing), your Chrome (a switch once paired, connected or Chrome closed, Add to Chrome, the pairing code read from the extension in that browser so it pairs by itself, Pair again when Chrome forgot the pairing, Forget this Chrome; the sites that need your sign-in, yours and the ones buddi added itself, outlined dashed, each removable), your apps only when a plugin provides them (its health and fix, a switch, Settings › to the plugin's own page), a warning with Resume while a Stop holds, and Advanced: the first choice for every agent, the agents with their own rule, the sites that need your sign-in, how long Stop lasts, pages open at once, and showing buddi's browser as a window. No lock while a page is open. Your old choice is carried over: Your browser keeps your Chrome on; Use my apps keeps your apps on (and your Chrome when it is paired). A conversation can be pinned to a route (Use my Chrome under the composer, once your Chrome is paired), an agent too (its page → Tools → Where it may look, written as `browser:` in its agent.md), and Settings keeps a default.\n- Browser stops: you are asked on four occasions only, with one card in the chat, the corner chat and Telegram (one photo, then buttons): \"I’m not sure that went through. Look?\" (Carry on · Look), \"Keep going?\" (Stop here · Keep going), \"Amazon needs your sign-in\" (Save a login for next time · Use my Chrome · Take over) and \"This page asks for a human\" (Skip this site · Take over), each with one line of why; while a Stop holds, \"Browsing is paused since 10:12\" (Keep paused · Resume). A slow page, a stale target, a redirect or a closed tab is retried inside the tool, and every action returns the page as it is after it, so agents no longer \"observe again\" or wait for a paused page.\n- Budgets are 200 actions and an hour per task, renewed by any message or card tap of yours in that conversation, and browser steps no longer use up the agent's turns. Several agents can look at once: three own-browser pages by default (a fourth waits its turn; a page waiting on a card for you doesn't count), several Chrome tabs with one agent per site at a time, one page in your hands and one app job at a time.\n- Stop agents' browsing now expires after an hour (a setting; or until you say), and while it holds an agent shows one card with Resume instead of telling you to visit Settings. A Stop left from before is lifted an hour after it was pressed.\n\n…"
   },
   "files": [
     "packages",