ppt-page-assets

To fix outdated PPT assets on a single page, you target the specific page_id or slot_id to update asset plans and regenerate image search results. This localized repair approach preserves the rest of the deck and avoids redundant computation.

Page-level PPT asset repair requires task-pack.json, asset-plan.json, and storyboard.json, along with a specified page_id or slot_id. These inputs enable targeted asset updates and local image regeneration within the deck directory.

Yes, you can replace a hero image or background on one slide by targeting its slot_id. This updates the image_selection.json and generates new local images while keeping all other slides in the presentation completely unchanged.

The best way to update image search results for a specific PPT slot is using a targeted asset repair workflow. It regenerates image_search_results.json and updates image_selection.json for the designated slot_id without touching other deck assets.

Yes, the PPT asset repair workflow updates asset-plan.json, image_search_results.json, and image_selection.json within the deck directory. It modifies these records to reflect the newly replaced assets for the targeted page or slot.

You should use targeted slide asset management when a specific page has clarity issues, semantic mismatches, or needs a quick cover image replacement. It performs minimal scope repairs to fix individual slots without reprocessing the entire storyboard.