LinX consumes xpod through the npm package in desktop runtime caches, not through LINX_XPOD_ROOT. The legacy CSS child config now gets copied into a stable runtime config directory whenever package component context is available, while preserving package-relative Components.js bases and rewriting package asset paths to absolute package-root paths. This prevents Application Support paths, runtime cwd differences, and bare component parameter keys from breaking local SP startup.

Constraint: LinX desktop validates the packaged xpod path and may install under directories containing spaces.

Constraint: Components.js parameter aliases must come from generated component context, not hand-written source config aliases.

Rejected: Keep using source-mode E2E as release evidence | it does not exercise npm package layout or runtime cache paths.

Rejected: Hand edit dist/components | generated metadata must come from build:components.

Confidence: high

Scope-risk: moderate

Directive: Do not change config/*.json to generated compact parameter aliases; runtime normalization derives them from dist/components/context.jsonld.

Tested: bun test tests/runtime/css-process.test.ts tests/runtime/bootstrap.test.ts

Tested: bun run build:ts

Tested: bun run build:components

Tested: bun run build:ui