Skip to content

fix(core): expose previous accepted move path - #1075

Merged
phernandez merged 1 commit into
mainfrom
codex/1072-previous-move-path
Jul 16, 2026
Merged

fix(core): expose previous accepted move path#1075
phernandez merged 1 commit into
mainfrom
codex/1072-previous-move-path

Conversation

@phernandez

Copy link
Copy Markdown
Member

Why

Accepted note moves capture the authoritative previous file path inside the move transaction, but exposed it only when materialized-file cleanup was needed. Never-materialized moves therefore forced Cloud activity publishing into a racy pre-read.

What changed

  • carry previous_file_path on accepted materialization results independently from cleanup work
  • set it from the transaction-local source path for moves only
  • preserve the field through queue-neutral requests and serialized worker payloads
  • keep create and update results unchanged
  • cover materialized and never-materialized moves plus create/update absence

Verification

  • just fast-check
  • just fast-test — 135 passed, 1 skipped
  • focused runtime, payload, mutation, enqueue, and response tests — 46 passed

Closes #1072.

Cloud follow-up: basicmachines-co/basic-memory-cloud#1506.

Signed-off-by: phernandez <paul@basicmachines.co>
@phernandez
phernandez merged commit c616148 into main Jul 16, 2026
23 checks passed
@phernandez
phernandez deleted the codex/1072-previous-move-path branch July 16, 2026 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose transaction-local previous path in accepted move results

1 participant