feat: dual-track registration with early claim + rollback support

[jlin53882]

Summary

Dual-track registration system for memory-lancedb-pro:

• Before init (Phase 2): claim api in both (WeakSet) and (Map)
• On init failure: explicit rollback, enabling retry with same API object
• resetRegistration(): now clears both WeakSet and Map

This enables test inspection of registered APIs and provides explicit rollback semantics on init failure.

Changes

• : +30/-6 lines (single file)

Dependencies

Based on master after PR #522 merge.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 013c1785b3

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Roll back WeakSet claim when init fails

If _initPluginState(api) throws, the catch block only removes api from _registeredApisMap, but the earlier _registeredApis.add(api) is never undone. Because register() gates on _registeredApis.has(api), a later retry with the same API object is skipped permanently, so initialization cannot recover after a transient startup failure. Add _registeredApis.delete(api) in this failure path (or delay the WeakSet add until after successful init) to preserve retry behavior.

Useful? React with 👍 / 👎.

[jlin53882]

Why This PR Matters

The Problem

After PR #522, places only after successful . This means:

• On init failure: the WeakSet has zero record that a registration was ever attempted — no trace, no debug trail
• Retry logic has no foundation: a subsequent call with the same API has no way to know "this was already tried and failed"
• Tests cannot assert: there is no way to verify "was this API object already considered for registration?" — WeakSet only tells you "is currently registered", not "was attempted"

The Dual-Track Solution

Track	Data Structure	Purpose
		Phase 2 singleton guard — GC-safe, prevents double-init
		Explicit claim/rollback — inspectable, supports retry logic

Registration flow now:

Concrete Benefits

1. Testability — lets tests assert "this API was attempted" even after a failed init
2. Debuggability — explicit claim/rollback creates a traceable audit trail
3. Retry safety — provides the ground truth for "should this API be retried?"
4. Future extensibility — the Map can carry metadata (timestamp, retry count, error reason) that a WeakSet structurally cannot