What does listing mean by default?

• queries? or visiting?
  • list-views in content apps work with queries—via AbstractJcrContainer
  • assuming we get the primary node-type info from somewhere (e.g. CT definition)

What does the user need

• flat list, e.g. from upcoming events component
• node tree?
  • JCR-specific endpoints only?
  • pass absolute path
  • depth query param—same as NodesEndpoint
• Assuming we have a notion of one or more primary node-types
• e.g. "fruit" is primary, folders are secondary

Could be based on MGNLREST-93; should belong in the new delivery module.
Outcome could be an array of "nodes/objects" (via simple format) +/- response metadata.