remem-plugin-version-synclisted

# remem-plugin-version-sync Use this skill for changes that affect the shipped `remem` binary, Codex plugin runtime, or npm wrapper. The goal is to keep all release surfaces consistent and avoid a plugin that resolves a stale or incompatible runtime. ## Files Keep these synchronized when the binary version changes: - `Cargo.toml` - `Cargo.lock` - `plugins/remem/.codex-plugin/plugin.json` - `plugins/remem/runtimes/remem-releases.json` - `npm/remem/package.json` `scripts/ci/check_plugin_version_sync.py` requires the Rust package, plugin manifest, release manifest, and npm wrapper package versions to match. A binary version bump must update the npm package version even when npm wrapper behavior is unchanged. Read these before editing plugin runtime behavior: - `plugins/remem/README.md` - `plugins/remem/skills/remem/SKILL.md` - `plugins/remem/scripts/remem-runtime.js` - `plugins/remem/scripts/remem-runtime.test.js` - `npm/remem/scripts/install.js` - `npm/remem/scripts/install.test.js` ## Workflow 1. Run `git status --short` and identify whether the PR changes binary-impacting files: `src/`, `migrations/`, or `Cargo.lock`. 2. If binary-impacting files changed, bump `Cargo.toml` `package.version`. 3. Regenerate or update `Cargo.lock` so the `remem-ai` package version matches. 4. Update `plugins/remem/.codex-plugin/plugin.json` to the same version. 5. Update `plugins/remem/runtimes/remem-releases.json` so it contains exactly the same version key and a `base_url` endin