miniz-integration

# miniz Integration ## Overview Use this skill to integrate miniz by separating format choice, memory budget, streaming strategy, and integrity checks. Compression bugs on MCUs usually come from buffer ownership, incomplete streams, or confusing raw DEFLATE, zlib, gzip, and ZIP containers. ## When To Use Use this skill when: - The user wants miniz for firmware assets, logs, configuration packages, OTA payloads, filesystems, or embedded resources. - The issue involves inflate errors, truncated output, high RAM use, ZIP archive handling, CRC mismatch, or streaming decompression. - The project has constrained RAM/flash, external storage, OTA downloads, or filesystem integration. Do not use this skill for very small streaming compression windows. Use `heatshrink-integration` when heatshrink is already selected for tiny MCU buffers. ## First Questions Ask for: - Data format: raw DEFLATE, zlib, gzip-like stream, or ZIP archive. - Compression/decompression direction, max input size, max output size, and RAM budget. - Storage/transport path, chunk size, and whether streaming is required. - Integrity requirement: CRC, hash, signature, or container metadata. - Current error code, input sample, and expected decompressed length. ## Integration Checklist 1. Pick the exact format. Do not mix raw DEFLATE streams, zlib headers, gzip files, and ZIP archives. 1. Budget memory before coding. Estimate output buffer, dictionary/window needs, file metadata, and stack usage. 1. P...