No. The per-item _imagify_data postmeta is not part of the whitelist. The render reads only safe summary counters from the option family, and per-item data stays scoped to the underlying tool where it belongs in normal use.

Yes. Paid plans expand the monthly quota but stores configuration in the same option family. Any flag you whitelist renders the same way as the free flags, through the standard template binding on the card render. There is no separate code path for the paid tier on the binding side.

Generally no. Per-row data is operational detail that most teams prefer to keep off the share image. The whitelist defaults to summary counters and toggle flags. Per-row dumps can be added on internal-only variants but are not in the default binding by design.

Each recap captures the state at publication time through the whitelisted flags. Historical recap posts keep the values current at save, so the audit trail of changes stays intact across the back catalog of recap posts published on the site over time.

Yes for live binding. If the plugin is deactivated the binding falls back to a manual value entered on the recap post and the auto-state badges go quiet by design. Reactivating restores the live binding on the next save without any code change.

Yes. The sweep type drives the variant selection. bulk run, WebP rollout, level change each use a dedicated layout that highlights the relevant badge set as the headline state of the recap and downplays unrelated badges accordingly through the variant configuration.

Yes. The library savings field is opt-in per variant. Some teams prefer to keep the percentage off the share image and reserve it for the body of the post, which is supported through a simple toggle on the variant configuration without code changes.

Yes. Each tool stores configuration in its own option family. SleekPixel binds to whichever option family is active for the recap post type, and multi-tool variants are supported as a separate template family for joint recap posts that touch both layers.