Let chat move a recording onto the correct meeting

[ComputelessComputer]

When overlapping calendar events start the wrong session, recordings, transcripts, and notes can land on the wrong meeting. Chat could search and edit text, but it had no way to reassign that content.

This adds a move_meeting_contents chat tool. After resolving both meeting IDs, Anarlog AI can move:

• the local recording
• transcript
• generated summaries
• notes
• action items

onto another existing meeting.

Safety limits:

• Source and target must be different existing meetings
• The target must not already have a recording or transcript
• The move is blocked while either meeting is still recording or transcribing
• If the database write fails after the audio copy, the copied file is rolled back

Usage from chat, on the meeting that has the misplaced recording:

Move this recording to the Board meeting

Or from the destination:

Move the Standup recording into this meeting

  

[netlify]

✅ Deploy Preview for anarlog canceled.

Name	Link
🔨 Latest commit	3976037
🔍 Latest deploy log	https://app.netlify.com/projects/anarlog/deploys/6a85e13884951e0008bf14e4

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3976037. Configure here.}

[cursor]

Moved audio stays marked processing

Medium Severity

catalogLocalSessionAudio always stamps the destination recording with transcript_status processing, and a successful move never marks it complete. Retention treats that flag as “still transcribing,” so a moved recording is skipped by every cleanup policy even when transcripts were moved with it.

 

^{Reviewed by Cursor Bugbot for commit 3976037. Configure here.}

[cursor]

Note move keys the wrong document id

Medium Severity

Note copy/clear updates session_documents with id equal to the session id and expectedRowsAffected: 1. Snapshots already expose rawNoteId because the canonical note is not always session.id. When that fallback applies, the note statements affect zero rows, the transaction fails, and the whole move (including the recording) is aborted.

 

^{Reviewed by Cursor Bugbot for commit 3976037. Configure here.}

[cursor]

Failed copy leaves target audio

Medium Severity

copiedAudio is set only after audioCopy returns success, and rollback runs only when that flag is true. A failed std::fs::copy can still leave a primary audio file in the target directory. The catch path then reports that nothing changed, later moves see that file as an existing recording, and the destination is stuck.

Additional Locations (1)

• crates/fs-sync-core/src/audio/mod.rs#L53-L78

 

^{Reviewed by Cursor Bugbot for commit 3976037. Configure here.}