fix(sync): surface built-in profile drift so identity keys reach existing users (v1.54.0)

[siddharth-bhansali]

Addresses the remaining gaps on #129 and #130 · INT-4395

Why these two issues are still open

The core ask of both landed in 1acbc48 (#167) and the profiles are correct. But sync run resolves profiles with readProfile() alone (sync/index.ts:706, :795, :919) — it never merges or diffs against the shipped built-in.

So every user who had already run sync init before #167 kept their older profile and writes zero identity keys — silently, forever. Record counts are identical whether the feature is active or not, so there is no signal at all. isBuiltinNewerThanInstalled exists in the codebase but is wired only into mem migrate.

That is why I left #129/#130 open rather than closing them on the #167 merge.

Changes

1. Detect and surface profile drift. findMissingBuiltinCapabilities() compares the installed profile against the shipped built-in across a curated set of additive fields: identityKeys, identityKey, enrich, dateFilter, memory.

A direct field comparison rather than the existing mtime approach — file mtimes are not meaningful for an npm-installed package, where every file is stamped at install time. The list is curated on purpose: a profile is user-editable, and fields someone may have deliberately removed (transform, exclude, onChange, …) must never nag. These five only ever add behaviour.

sync run warns per model and points at one sync init <platform> <model> (which patches, preserving edits). --agent output carries a profileDrift array with model, missingFields, and the fix command, since an agent cannot see a console warning.

2. hasIdentityKey read only the singular key. sync/index.ts:144 was !!(p as any).identityKey, so sync profiles --agent reported hasIdentityKey: false for gmail / google-calendar / fathom — precisely the three profiles the plural form was added for. Now checks both, plus a distinct hasIdentityKeys so the two concepts stay separable. Same fix for the human-mode [identity] tag.

3. Bcc participants (#129). The issue's Problem section names From/To/Bcc; the profile declared only From/To/Cc. Added. Note Gmail strips Bcc for recipients, so these resolve only on threads the authenticated user sent — documented rather than silently partial.

Deliberately not in this PR

• [Sync] Built-in gmail/threads profile: identity keys for all participants #129 proposed item 3 (move the from_email extraction into the built-in profile) — that changes the record shape for existing users, so it wants its own change with a migration note rather than riding along here.
• [Sync] Built-in gmail/threads profile: identity keys for all participants #129 acceptance 4 (sync test previewing resolved identity keys for enrich-deferred profiles) — sync test never enriches its samples, so the preview correctly reports 0 with an explanatory note. Making it meaningful means having sync test perform a detail call, which is a real design decision, not a fix.

Both are worth keeping the issues open for if you want them; happy to split them out.

Tests

8 new tests in profile-drift.test.ts covering the drift detector (reports a genuinely-missing capability against the real gmail built-in, stays quiet when present, never reports user-editable fields, handles missing built-in / missing installed / explicitly-empty-value) and the Bcc addition. The pre-existing identity-keys.test.ts suites still pass unchanged — 43/43 together.

Verification notes

• npx tsc --noEmit passes.
• I did not run the full npm test suite: on Windows it reads and writes the developer's real ~/.one (tests sandbox process.env.HOME, which os.homedir() ignores on win32).
• Version bumped 1.52.1 → 1.54.0. package-lock.json version fields hand-edited rather than regenerated, since npm install on Node 24 drops the pg optional dependency from the lockfile.
• Stacks with fix(sync): never destroy a healthy database on a driver fault (v1.52.3) #179 (INT-4393) and feat(sync): re-enrich stale detail content — --re-enrich + enrich.invalidateOn (v1.53.0) #180 (INT-4394); all three branch from main and touch sync/index.ts in different places. Whichever merges later will need its version bump rebased.

🤖 Generated with Claude Code

---

Also in this PR (unrelated housekeeping)

Removes test/all-emails.json, a committed API-response capture that nothing in the codebase references — it landed by accident in f4f8ea4 alongside an unrelated README change. Adds .gitignore rules so local captures cannot be committed the same way again. Full suite passes with it gone.

Also merges main (this branch predated CI landing, so it had no checks at all).

[linear]

INT-4395