Plumbs the platform v3 `delete_linked` flag through the hosted MemoryClient in
both SDKs. When true, DELETE /v1/memories/{id}/ also removes the older memories
the target superseded (the linked_memory_ids chain) — the delete-side counterpart
of `latest_only`, so a superseded memory doesn't resurface after the current one
is deleted.
- Python: MemoryClient.delete / AsyncMemoryClient.delete gain `delete_linked: bool = False`
forwarded as a query param (omitted when False — default byte-identical).
- TypeScript: client.delete accepts `{ deleteLinked?: boolean }`, serialized to
`delete_linked` via the existing camelToSnakeKeys path (matches latestOnly).
- Unit tests for both: default omits the param; opt-in forwards it.
Client-side passthrough only; no changes to the OSS memory engine.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chaithanyak42