Support asset path import from js + special treatment of /public dir

Editor assessment

`feat: support asset path import from js + special treatment of /public dir` crams two behaviors together, and `special treatment` is deliberately uninformative — what treatment, and why. The plus-chained second clause reads as a grab-bag. No scope marks the asset area. No body explains the new import capability or the public-dir rules, so a two-part feature arrives with no explanation of either part. Style basics hold otherwise: imperative verb, no trailing period. Valid and partially legible, but the vague second clause and missing rationale cap it at acceptable.