reuse-scriptslisted

# Engine scripts The installed `playcanvas` package ships production scripts under `scripts/esm/**`. Discover the current set rather than maintaining a stale list: ```sh rg 'static scriptName =' node_modules/playcanvas/scripts/esm \ | sed "s|.*/scripts/esm/||; s|:.*static scriptName = ['\"]| -> |; s|['\"].*||" \ | sort ``` Read the selected file for its named export, `@attribute` properties, and defaults. Not every module is a `Script`; the parsers below `scripts/esm/parsers` are plain classes registered with a resource handler instead. Only import from `scripts/esm/**`. Legacy sibling directories depend on the global Engine namespace. After selecting a script, use `find-examples` to locate its matching versioned Engine example. Use a relevant shipped script as the default implementation. If it cannot own the whole feature, preserve its input signs, angular damping, bounds, and lifecycle invariants in the custom portion instead of replacing them from memory. ## Reproduce the reference integration Treat the selected script source and its closest official example as complementary references: 1. Read the source for exports, properties, defaults, fallbacks, required components, and lifecycle. 2. Read the example for assets, entity references, mesh requirements, layer ordering, scene settings, and render-pipeline setup. 3. Reproduce the smallest working baseline before customizing it. Preserve defaults that are not deliberately changed, and tune one property gr