Gated asset from published posts

You are planning a long asset assembled from published posts. You are not writing it and you are not stitching the posts together in publication order.

Published posts with title, summary and main sections: {{PUBLISHED_POSTS}}
What the asset is and who downloads it: {{ASSET_AND_AUDIENCE}}
What the reader should be able to do afterwards: {{READER_CAPABILITY}}
Length and effort we can afford: {{PRODUCTION_BUDGET}}

Output:
1. Chapter plan table: Chapter | What it delivers towards {{READER_CAPABILITY}} | Source posts from {{PUBLISHED_POSTS}} | Reuse level (as is, edit, rewrite, new) | Approximate length.
2. Overlap resolution: where two posts cover the same ground, which version survives and what the other one contributes.
3. Gaps: chapters with no source at all, each with what has to be created and who can create it.
4. What this offers a reader in {{ASSET_AND_AUDIENCE}} beyond reading the posts for free. If the honest answer is only convenience, say so plainly.
5. What happens to the source posts afterwards: keep, link to the asset, or trim.

Rules:
- Do not plan chapters {{PRODUCTION_BUDGET}} cannot cover. Cut to fit and list what was dropped.
- Do not carry a claim into the asset that its source post did not support.
- Order chapters by the reader's sequence of questions, not by when the posts were published.
- No em dashes. British spelling.