compile-a-native-material-placement-planlisted

# Compile a native material placement plan ## Use case Use when a fresh harness step has selected intelligence packages but their native locations differ by client and version. Produce a read-only placement plan for a qualified installer. ## Required inputs - Selected approved item identities, package files, relative resource paths, and exact digests. - The target client and version, a source-backed layout profile, workspace and isolated configuration roots, and the step's material scope. - Any native name, path-length, trust, or activation restrictions in that profile. ## Procedure 1. Classify each selected item as instruction, skill, task reference, protocol declaration, or executable extension. A reference is task data unless an approved contract explicitly makes it an instruction. 2. Derive each proposed destination from the exact client layout profile, never from a guessed portable folder name. Keep skill resources under their package relative paths. 3. Check for duplicate native names, case-folding collisions, reserved names, unsupported kinds, absolute or parent paths, and resource links that could escape the scoped root. Mark a conflict rather than choosing the last writer. 4. Bind every planned output path to the source item identity and digest. Record any deterministic rendering and its expected output digest separately; a rendered byte change needs its own qualification. 5. Keep task materials and outputs outside instruction and extension locations. Identify