v0.5.2-preview.1

• @assetlib/cli 0.3.0, unchanged from 0.5.1-preview.1 and attached to this release again. @assetlib/sdk-core changes only its version and README.

• @assetlib/sdk-expo: on iOS and Android, client.resolveAnimation(ref) under the default disk cache policy always returned source: 'poster', so verified Lottie animations never reached the app's player. The native storage adapter accepted only PNG and WebP, so caching the verified JSON threw after a successful download, and it never looked for a cached animation. It now stores application/json as <sha256>.json in the same namespaced cache directory and reads it back. Each JSON entry is capped at 512 KiB (LOTTIE_LIMITS.bytes) and counts toward the same 50 MiB / 100 entry eviction budget as images. Other MIME types are still rejected, and raster storage, .webp compatibility and legacy namespace migration are unchanged. The core still rehashes and revalidates cached JSON on every read. The memory and none policies and Expo web were not affected.

• Limits: the SDK includes no Lottie player; the app supplies one. A cache write that fails after a verified download still returns the poster, just as a failed image cache write returns the bundled image. Native SVG and PDF delivery are still not implemented. The fix is covered by Node unit tests that run the real adapter source against a simulated Expo filesystem; it has not been run on an iOS or Android device or simulator.

Attached: @assetlib/sdk-core and @assetlib/sdk-expo 0.5.2-preview.1, @assetlib/cli 0.3.0 (unchanged from v0.5.1-preview.1 apart from its README URL), and SHA256SUMS covering those three. Not on npm.