You are preparing media from an owner-supplied game media pack. Follow the owner’s requested destination, format and scope.

1. Extract Part 1 and Part 2 into the same new folder, preserving the games/ subfolders. Part 1 contains Valorant and Rainbow Six Siege. Part 2 contains Apex Legends, Wardogs and Rob Run. The five allowed game IDs are valorant, r6, apex, wardogs and rob_run. If only one part is supplied, work only with files actually present and state which part is missing. Keep the supplied originals intact. Read manifest.json and features.json first, then FEATURES.md and COMPATIBILITY.csv when needed.
2. The root documentation is shared between the two parts. Treat manifest.json as the authority for actual included files, dimensions, durations, hashes and edit timestamps. Match each game by its game ID. Use only relative paths inside the extracted folder. A path convention in features.json is not proof that an asset exists.
3. When listed in the manifest and present, use games/{id}/showcase_16x9.mp4 for landscape work, games/{id}/teaser_9x16.mp4 for portrait work, and games/{id}/thumbnail.png for the thumbnail. Do not substitute another game’s files. If an asset is missing, report that specific gap and continue with the available authorized assets.
4. Preserve the supplied framing, gameplay, actual visual overlays and privacy masks. Valorant has a 40-second landscape showcase and a 24.7-second portrait teaser. Its portrait layout stacks a full-width overview above a focused gameplay panel. Preserve both panels; do not crop the full-width overview away or obscure player overlays. The landscape Visuals menu section is at 8.7-11.1 seconds; control labels show appearance only. Use the manifest’s edit details rather than guessing source timestamps. Do not add fake gameplay, fabricated controls or invented demonstrations. Keep an AI-edited thumbnail separate from evidence of actual gameplay or product capability.
5. Separate catalog claims from reviewed visual observations. A menu label shows a control; a visible overlay shows its appearance. Neither a menu label nor a successful shot independently proves aimbot effectiveness, silent aim, recoil removal, stream protection or detection safety. Only describe observations that remain visible in the delivered edit.
6. Do not invent features, prices, license durations, compatibility, stock, support promises or detection claims. Unknown or null values remain unknown. Treat every status label as a dated, unverified listing, never a guarantee. Do not advertise Rob Run controls in disabled_options as active or activate them.
7. Before publishing commercial claims, obtain the owner’s current prices, license terms, availability and requirements and update the working copy accordingly. Do not silently reuse snapshot pricing as current pricing. Keep missing product details unfilled until the owner provides them.
8. Public video masters are silent. Add no external artist music, links or unrelated material. Add the owner’s brand, contact details or properly licensed music only when the owner requests and supplies the necessary material or permission. Do not restore removed seller branding, private identifiers or account information.
9. Write new edits and captions into a new output folder. Use concise game-specific copy grounded in the permitted evidence. Inspect the result for correct game matching, readable framing, retained masks, unsupported claims and accidental identifiers.
10. Return the prepared files and a short list of any missing data. Do not automatically post, publish, message, upload or schedule anything without the owner’s instruction.

Owner’s requested task: [insert the desired edit, channel, duration, caption style and output format here].

Photo library use: Read manifest.json, PHOTO_INDEX.csv, PHOTO_GUIDE.md and COVERAGE_REPORT.md. Each game has photos[] with origin and category labels. Use only current manifest paths in games/{id}/photos/. Preserve supplied text, UI toggle states, gameplay overlays and privacy masks. Website menus, website gameplay, website artwork, recorded menus and new gameplay captures are labeled separately. Use website menu references for current published UI appearance; recorded references may show older software versions. Artwork and presentation thumbnails are not evidence of actual gameplay. Do not invent features or recreate UI labels. Return requested assets in a new output folder.
