Skip to content

fix: Codex CONFIRM resubmission and Motion data relocation (0.1.111) - #122

Merged
brunoazoulay merged 3 commits into
mainfrom
fix/motion-scope-codex-confirm
Oct 29, 2026
Merged

brunoazoulay merged 3 commits into
mainfrom
fix/motion-scope-codex-confirm

Conversation

@brunoazoulay

Copy link
Copy Markdown
Collaborator

Summary

  • fix(confirm): Codex CONFIRM — resubmitted armed code returns "armed" (not a false "unknown"), receipt-only code returns "already-consumed", whole-message markdown/quote-wrapped CONFIRM xxxx accepted, single-line escaped ack.
  • fix(motion): Motion data relocated under ~/.fuse-harness/video-motion/; Motion guards key on video-motion so harness commands on cache/sessions are no longer blocked; race-safe rename(2) migration of the old layout, old fragments stay blocklisted.
  • chore: bump version and CHANGELOG to 0.1.111.

Test plan

  • bunx tsc --noEmit clean
  • HOME=$(mktemp -d) bun test — 3374 pass, 0 fail
  • CI green

Breaking changes

None — the old Motion layout is migrated automatically on first resolve.

- A resubmitted, already-armed code now returns "armed" instead of a false "unknown".
- A receipt-only code returns "already-consumed".
- A whole-message markdown/quote-wrapped `CONFIRM xxxx` is accepted.
- The ack reads "accepté — relance maintenant exactement : <cmd> (valide 5 min)",
  with control characters escaped onto a single line.
- Approvals, state, critic flags, banned.txt and signing keys now live
  under ~/.fuse-harness/video-motion/.
- Motion guards key on video-motion instead of the whole ~/.fuse-harness/
  directory, so harness commands on cache/sessions are no longer blocked.
- The old layout is migrated on first resolve with rename(2), never deleted
  or overwritten; old fragments stay blocklisted; in-flight approvals are
  re-verified once after the move (fail-closed).
@brunoazoulay
brunoazoulay merged commit 89e5a26 into main Oct 29, 2026
1 check passed
@brunoazoulay
brunoazoulay deleted the fix/motion-scope-codex-confirm branch October 29, 2026 23:24
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.

1 participant