[wmeddie]

Promote prerelease v0.4.25 to stable v0.4.26, with a correction for tab drops outside the tab strip exposed by release CI. Pin source and runner images to 6312aac8fb39e69bdd213f465068ac4bb6ff0e7b, retain native build number 25, synchronize app/lockfile/MCP versions, and add notes covering changes since stable 0.4.13.

The drag handler previously read operation.position.current before dnd-kit committed the new coordinates. Coalesced pointer events could leave a stale landing marker and an out-of-strip release could reuse it. Use the move event's to/by coordinates, use native pointer-release coordinates for a final movement that has not been processed, and preserve the committed position for keyboard drops. A release outside all strips now leaves the original tab order intact.

Validation:

• Release metadata synchronized; 8 release tests passed.
• Stable plan: version 0.4.26, source v0.4.25, native build 25, runner revision 6312aac.
• Chromium/WebKit settled and immediate outside-drop regressions: 20 repeated cases passed, with a single jump to make event coalescing deterministic.
• Broader tab suite: 27 passed, 2 platform-specific skips, including keyboard moves/cancellation and native touch scrolling.
• Frontend typecheck: 0 errors/warnings; production build passed; git diff --check passed.

The source prerelease's CI, runner builds, and four-platform release builds passed. Fresh CI is required for the final release commit including the tab-drop correction.

After final CI passes, publish v0.4.26 at this release commit before merging it into main, so a main-branch prerelease cannot consume the stable version. Verify the complete stable release is public and latest, then merge this PR.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-25T09:36:58.973871Z	97cf5ff	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.