Sync Granola notes from opted-in personal folders
Superseded by the stacked implementation: #30814 → #30815 → #30816 → #30817.
Context
This follows #30803 and #30806. Members who connect Granola need to opt individual folders into sharing future meeting notes as Twenty Call Recordings. The existing workspace connection can keep syncing meetings in parallel.
Changes
- Reconcile one folder-filtered Granola webhook per opted-in personal connection. Route deliveries through the existing workspace claim, verify the signature, and use the current member key.
- Verify the note was created after opt-in and is still in a selected folder or subtree. Recheck the member connection and selection before writing. Disconnect, clearing the selection, and uninstall retire routing claims and remove the remote endpoint when its key still has access.
- Use the existing deterministic Call Recording ID. Add one nullable, read-only app field to track the source revision of personal imports. A conditional update rejects stale personal writes, and a workspace write clears the revision so later personal deliveries leave the workspace copy alone. Existing Granola recordings have a null revision and retain workspace ownership.
Build and rollout
This PR is the live delivery path. Scheduled catch-up and the Folders tab will land together in the release PR after this merges. The current app version has no member-facing folder picker. The first scheduled run will reconcile every saved personal selection, including choices made during development or through the settings API before the release, so those members do not have to save again. There is no app version bump here. The new field is additive and needs no data backfill. The current workspace webhook URL, registration keys, and scope-selection behavior are preserved.
Verification
- Granola lint, typecheck, unit tests, and Twenty CLI app build
- Deploy and run the suite against an isolated local Twenty server. Coverage includes matching nested folder scope, opt-in timestamps, disconnect during a delivery, stale keys after reconnect, and competing workspace and personal writes.