Frozen Codex updates now finish on their own
- What happened. If you use AIQ Rank from both Claude Code and Codex, a Claude session running an older plugin copy could quietly stall the Codex-side updater. Updates stopped halfway — the local log kept a "preserving modified" note — and the Codex scanner stayed on an old version even though the plugin itself looked current.
- Why. The updater only replaces a local file it can vouch for: one matching the last install record, a known release, or the incoming bundle. An older plugin copy rewrote that record without the newest files' entries, so those files matched nothing and were treated as yours — left untouched, update after update.
- What's fixed. The updater now recognizes every previously released version of those files as safe to replace, so the next update completes and the scanner catches up in one run. The install record also keeps entries for files an older copy doesn't know about, so this cannot happen again.
- Nothing changes for your data. The same privacy bound as always — only aggregate counts leave your machine.