[MaheshtheDev]

On every client start the plugin overwrote the whole org's filter prompt (PATCH /v3/settings with shouldLLMFilter/filterPrompt), even in v5 mode. That write was its last legacy call on the hosted API. It also replaced the organization context for every namespace in the org, not just OpenCode's. The v5 migration README said the call "does not replace organization context". It does: v5 GET /organization returns that same organization_settings.filterPrompt column as organizationalContext.

This PR removes the write, plus the filterPrompt config option that only fed it. Extraction guidance already travels with every save as entityContext (AGENT_ENTITY_CONTEXT on v1 and v2 capture, compaction, and the memory tool), which is how every other plugin does it. Users with filterPrompt in their config are unaffected; the key is ignored.

Also:

• v5 mode no longer creates the bundled legacy SDK client.
• status only falls back to /v3/session in legacy mode.
• The README paragraph is updated.
• The version is bumped to 2.1.1, so merging publishes.

Verified. Typecheck, all 33 tests, and build pass. I ran SupermemoryClient against a local server that records requests, calling search, profile, add, list and delete:

Mode	Routes hit
v5 (this PR)	/ns/{ns}/search, /profile, /document, /list/documents, DELETE /ns/{ns}/memories (no settings call)
v5 (main)	same, plus PATCH /v3/settings
legacy (this PR)	/v4/search, /v4/profile, /v3/documents, /v3/documents/list, /v4/memories (no settings call)

[capy-ai]

Approving at 99912e6 on Mahesh's request ("skip and merge it"), with the Capy review waived for this PR only. I verified it: typecheck passes, 33/33 tests pass, and nothing in src still references the removed filterPrompt/settings.update. The version goes to 2.1.1, so the merge publishes.