Marketplace storage keys can point at whole file trees, but generic writes are refused.
A marketplace file-tree key form is wired through path resolution and listing, but writes are refused and generic resolution does not accept it yet.
What's wrong with this entry?
Path resolution, key validation, child and descendant lookup, directory listing and scope enumeration in the storage key layer all check whether a marketplace key carries a relative path, and take the file-tree route if so. Writes through the tree interface are refused because trees are produced by cloning or publishing, and generic key resolution does not accept a marketplace tree yet.
a marketplace's tree is not resolved through resolveKey yet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.