release: #3133 closed as shipped, but v2.2.2 was never tagged or published (npm still 2.2.1)

#3133 ("release: ecc-universal 2.2.2") was closed on 2026-09-19, but as of right now the release itself doesn't exist anywhere users can reach:

• tags end at v2.2.1 (2026-09-08) — no v2.2.2 tag
• no GitHub release after v2.2.1
• npm view ecc-universal version reports 2.2.1

So everything merged since 9/8 — the GateGuard/register fixes in #3167 (1a8beb71), the parallel-batch warning #3164 (db61d1c7), the export-server containment #3206 (8d597276), the worktree/instinct-registry work (#2009, bc519e5b8e), the hooks-metadata rework (1ac0790) — is unreachable for anyone on the npm/marketplace install path.

Concrete user reports hitting exactly this gap:

• #3203: npx [email protected] setup 404s, 2.2.1 reproduces the error
• #2984: tools/list does not accept parameters. (JSON-RPC -32602) against the published tarball
• #3127: published 2.2.1 has no main/exports, so OpenCode silently skips the plugin
• #3101: the export-server fix postdates the v2.2.1 tag, so scanners keep flagging it

Ask: cut v2.2.2 (tag + release + npm publish), or re-open #3133 so the drift is tracked until it actually ships. Happy to sanity-check the published tarball once it lands.