@withone/cli 1.54.1 → 1.55.0

package/dist/{chunk-XN4ZWMLX.js → chunk-FS4HAKZ6.js}

@@ -523,7 +523,9 @@ async function writePageToMemory(profile, records, opts = {}) {
   const searchablePaths = getSearchablePaths(profile);
   const declaresIdentityKeys = (profile.identityKeys?.length ?? 0) > 0;
   const enrichTimestampField = profile.enrich?.timestampField ?? "_enriched_at";
-  for (const record of records) {
+  for (const rawRecord of records) {
+    const derived = deriveFields(rawRecord, profile.derive);
+    const record = Object.keys(derived).length > 0 ? { ...rawRecord, ...derived } : rawRecord;
     report.attempted++;
     const externalId = getByDotPath(record, profile.idField);
     if (externalId === void 0 || externalId === null || externalId === "") {
@@ -608,6 +610,24 @@ function identityValuesFor(prefix, raw, opts = {}) {
   const v = s.toLowerCase().trim();
   return v ? [v] : [];
 }
+function deriveFields(record, derive) {
+  const out = {};
+  if (!derive) return out;
+  for (const [field, spec] of Object.entries(derive)) {
+    const { path: path5, extract } = typeof spec === "string" ? { path: spec, extract: void 0 } : spec;
+    if (!path5) continue;
+    const values = resolveIdentityPath(record, path5).filter((v) => v !== null && v !== void 0 && typeof v !== "object");
+    if (values.length === 0) continue;
+    if (extract === "email") {
+      const emails = values.flatMap((v) => identityValuesFor("email", v));
+      if (emails.length === 0) continue;
+      out[field] = emails[0];
+      continue;
+    }
+    out[field] = values[0];
+  }
+  return out;
+}
 function tokenizeIdentityPath(path5) {
   const tokens = [];
   const re = /([^.[\]]+)|\[([^\]]*)\]/g;

package/dist/index.js

@@ -66,7 +66,7 @@ import {
   writeDraftProfile,
   writePageToMemory,
   writeProfile
-} from "./chunk-XN4ZWMLX.js";
+} from "./chunk-FS4HAKZ6.js";
 import {
   getByDotPath
 } from "./chunk-44CV5IMX.js";
@@ -5888,6 +5888,21 @@ async function enrichPhase(api, db, config2, model, idField, connectionKey, plat
   const duration = elapsed < 1e3 ? `${elapsed}ms` : elapsed < 6e4 ? `${(elapsed / 1e3).toFixed(1)}s` : `${Math.floor(elapsed / 6e4)}m ${Math.floor(elapsed % 6e4 / 1e3)}s`;
   return { enriched, skipped, rateLimited, total, duration };
 }
+async function enrichOneForPreview(api, profile, record, connectionKey) {
+  const config2 = profile.enrich;
+  if (!config2) return null;
+  try {
+    const detailAction = (await resolveActionDetails(api, config2.actionId)).details;
+    const detail = await enrichSingleRow(api, detailAction, config2, record, connectionKey, profile.platform);
+    if (!detail) return null;
+    let enrichedData = detail;
+    if (config2.fields && config2.fields.length > 0) enrichedData = pickFields(enrichedData, config2.fields);
+    if (config2.exclude && config2.exclude.length > 0) stripExcludedFields(enrichedData, config2.exclude);
+    return config2.merge !== false ? deepMerge(record, enrichedData) : { ...enrichedData, [profile.idField]: record[profile.idField] };
+  } catch {
+    return null;
+  }
+}
 async function enrichSingleRow(api, detailAction, config2, row, connectionKey, platform) {
   const pathVars = interpolateParams(config2.pathVars, row);
   const queryParams = interpolateParams(config2.queryParams, row);
@@ -6879,7 +6894,14 @@ async function testSyncProfile(api, profile) {
   }));
   report.sample = first;
   report.samples = records.slice(0, SEARCHABLE_SAMPLE_SIZE);
-  report.identityKeysPreview = buildIdentityKeysPreview(report.samples, profile);
+  if (profile.enrich && (profile.identityKeys?.length ?? 0) > 0 && report.samples.length > 0) {
+    const merged = await enrichOneForPreview(api, profile, report.samples[0], connectionKey);
+    if (merged) {
+      const preview = buildIdentityKeysPreview([merged], profile);
+      if (preview) report.identityKeysPreview = { ...preview, previewedAfterEnrich: true };
+    }
+  }
+  report.identityKeysPreview ??= buildIdentityKeysPreview(report.samples, profile);
   report.ok = checks.every((c) => c.ok);
   return report;
 }
@@ -8379,7 +8401,7 @@ async function maybeAutoMigrateLegacy(platform, models) {
       `  detected legacy .one/sync/data/${platform}.db (${dbSize}) \u2014 auto-migrating into memory before sync.
 `
     );
-    const { memMigrateCommand: memMigrateCommand3 } = await import("./migrate-UGDDHWGY.js");
+    const { memMigrateCommand: memMigrateCommand3 } = await import("./migrate-37A463L6.js");
     await memMigrateCommand3({ platform, yes: true });
     return;
   }
@@ -8388,7 +8410,7 @@ async function maybeAutoMigrateLegacy(platform, models) {
     initialValue: true
   });
   if (p7.isCancel(shouldMigrate) || !shouldMigrate) return;
-  const { memMigrateCommand: memMigrateCommand2 } = await import("./migrate-UGDDHWGY.js");
+  const { memMigrateCommand: memMigrateCommand2 } = await import("./migrate-37A463L6.js");
   await memMigrateCommand2({ platform, yes: true });
 }
 async function syncSuggestSearchableCommand(platformModel, options = {}) {
@@ -10859,6 +10881,30 @@ Enrichment runs after list sync completes (Phase 2), not inline. It's inherently
 
 **Limitation:** Each profile supports one enrich action. If you need multiple enrichments (e.g. both summary and transcript from Fathom), create a second profile/model for the second enrichment.
 
+## Derived fields (\`derive\`)
+
+Add flat, queryable top-level fields computed from paths already in the record \u2014 no shell, no \`jq\`:
+
+\`\`\`json
+{
+  "derive": {
+    "from_email": {
+      "path": "messages[0].payload.headers[name=From].value",
+      "extract": "email"
+    },
+    "company": "organization.name"
+  }
+}
+\`\`\`
+
+- Paths use the same resolver as \`identityKeys\`, so \`[]\` wildcards, \`[0]\` indexes and \`[name=From]\` filters all work
+- \`extract: "email"\` pulls the address out of a display-name header (\`"Jane <jane@acme.com>"\` \u2192 \`jane@acme.com\`), lowercased
+- A path resolving to nothing **omits** the field rather than writing null, so \`--where\` filters behave
+- A path resolving to several values takes the first \u2014 it's a flat field by definition, and the path syntax lets you be specific
+- Applied on both sync phases, so an enriching profile gets the same field whether the record came from the list or the detail pass
+
+**Prefer \`derive\` over \`transform\` for extracting a field.** \`transform\` spawns \`sh -c\`, so it needs \`jq\` (or whatever you invoke) on PATH and does nothing on Windows. \`derive\` is pure and works everywhere \u2014 which is why the built-in \`gmail/gmailThreads\` profile uses it for \`from_email\`. Reach for \`transform\` when you need real computation, not field extraction.
+
 ## Record Transform
 
 Pipe records through any shell command or flow between fetch and store. The command receives a JSON array on stdin and must return a JSON array on stdout.
@@ -10933,7 +10979,9 @@ Two ways to tag a record with a cross-platform identifier (e.g. email), dependin
 ]}
 \`\`\`
 
-Each \`path\` supports \`[]\` wildcards (one key per element) and a \`[name=From]\` equality filter (e.g. Gmail \`messages[].payload.headers[name=From].value\`). \`email\`-prefixed values are email-extracted, so display-name headers (\`"Jane <jane@acme.com>"\`) and comma-lists normalize cleanly. Values are lowercased/trimmed/deduped. \`sync test\` previews how many identity keys each record resolves.
+Each \`path\` supports \`[]\` wildcards (one key per element) and a \`[name=From]\` equality filter (e.g. Gmail \`messages[].payload.headers[name=From].value\`). \`email\`-prefixed values are email-extracted, so display-name headers (\`"Jane <jane@acme.com>"\`) and comma-lists normalize cleanly. Values are lowercased/trimmed/deduped.
+
+\`sync test\` previews how many identity keys each record resolves. For an **enriching** profile the participant paths live in the detail payload, so \`sync test\` spends one detail call on the first sample and previews against the merged shape \u2014 you see the keys a real sync would write, not zero plus a promise. If that call can't be made (rate limit, permissions), it falls back to the list-shape preview and says the keys resolve after enrichment.
 
 The built-in \`gmail/gmailThreads\` profile collects From/To/**Cc/Bcc**. Gmail only returns a \`Bcc\` header on messages the authenticated user sent \u2014 it is stripped for recipients \u2014 so Bcc keys appear on your own sent threads and nowhere else.
 

package/dist/{migrate-UGDDHWGY.js → migrate-37A463L6.js}

@@ -3,7 +3,7 @@ import {
   dotPathToJsonbExpr,
   memMigrateCommand,
   reviveStringifiedJson
-} from "./chunk-XN4ZWMLX.js";
+} from "./chunk-FS4HAKZ6.js";
 import "./chunk-44CV5IMX.js";
 import "./chunk-GNSR3NYN.js";
 import "./chunk-DDCDPVJH.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withone/cli",
-  "version": "1.54.1",
+  "version": "1.55.0",
   "description": "CLI for managing One",
   "type": "module",
   "files": [

package/profiles/gmail/gmailThreads.json

@@ -21,6 +21,12 @@
     { "prefix": "email", "path": "messages[].payload.headers[name=Cc].value" },
     { "prefix": "email", "path": "messages[].payload.headers[name=Bcc].value" }
   ],
+  "derive": {
+    "from_email": {
+      "path": "messages[0].payload.headers[name=From].value",
+      "extract": "email"
+    }
+  },
   "enrich": {
     "actionId": "conn_mod_def::GJ3ok0Eq0R8::AAzgZVLqTg2iBuITKpJLZg",
     "pathVars": { "userId": "me", "id": "{id}" },

package/skills/one/SKILL.md

@@ -311,6 +311,8 @@ Without declared paths, the default walker concatenates every string in the reco
 
 **Connections are late-bound** — profiles use `"connection": { "platform": "<name>" }`, not literal `connectionKey` strings. The key is resolved at sync time, so `one add <platform>` (re-auth) doesn't break the profile. For multi-account platforms, add `"tag": "<connection-tag>"` to disambiguate, and create the tagged connection with `one add <platform> --tag <name>`. Don't hardcode connection keys in profiles.
 
+**Extracting a flat field? Use `derive`, not `transform`.** `derive` computes top-level fields from paths already in the record (`"derive": { "from_email": { "path": "messages[0].payload.headers[name=From].value", "extract": "email" } }`), using the same path syntax as `identityKeys`. `transform` spawns `sh -c`, so it needs `jq` on PATH and silently does nothing on Windows — never put one in a profile you intend to share. A path that resolves to nothing omits the field rather than writing null.
+
 **Installed profiles do not auto-update.** `sync run` reads only `.one/sync/profiles/<platform>_<model>.json` and never merges the shipped built-in, so a profile created before a capability shipped silently lacks it — a pre-#167 gmail profile writes zero identity keys, forever, with no change in record counts. `sync run` warns when the built-in declares `identityKeys` / `identityKey` / `enrich` / `dateFilter` / `memory` that your copy lacks (agent mode: a `profileDrift` array). Fix with `one sync init <platform> <model>`, which patches rather than overwrites.
 
 **Cross-platform identity on a profile.** Two separate fields, and picking the wrong one silently mangles data: