prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  resolve-dynamic-import
   +--_expected
   |   +--amd
   |   +--cjs
   |   +--es
   |   `--system
   `--nested
  ```
  
  Convert this description:
  
  search is a core directory that features 2 subdirectories: async and sync.
  In the root directory, 'async' encapsulates 2 contained folders: client, server.
  At level 2, in directory path 'async > client', 'client' includes 1 subfolders: use.
  In nested path 'async / client / use', The 'use' collection has yet to be populated.
  In nested path 'async / server', 'server' has 2 directory entries: await, use.
  At level 3, in directory path 'async > server > await', 'await' awaits content.
  At level 3, in directory path 'async → server → use', Inside 'use', you'll find it has nothing inside.
  In the root directory, 'sync' bundles 2 directory entries: client, server.
  In nested path 'sync / client', 'client' encompasses 3 directory entries: access, has, spread.
  In nested path 'sync / client / access', Inside 'access', you'll find it is a vacant space.
  At level 3, in directory path 'sync > client > has', Inside 'has', you'll find it holds no subdirectories at the moment.
  In nested path 'sync → client → spread', The 'spread' collection is empty.
  At level 2, in directory path 'sync → server', 'server' hosts 3 directory entries: access, has, spread.
  In nested path 'sync > server > access', 'access' is devoid of content.
  At level 3, in directory path 'sync > server > has', Inside 'has', you'll find it is barren.
  At level 3, in directory path 'sync / server / spread', 'spread' awaits content.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "search\n +--async\n |   +--client\n |   |   `--use\n |   `--server\n |       +--await\n |       `--use\n `--sync\n     +--client\n     |   +--access\n     |   +--has\n     |   `--spread\n     `--server\n         +--access\n         +--has\n         `--spread", "description": "search is a core directory that features 2 subdirectories: async and sync.\nIn the root directory, 'async' encapsulates 2 contained folders: client, server.\nAt level 2, in directory path 'async > client', 'client' includes 1 subfolders: use.\nIn nested path 'async / client / use', The 'use' collection has yet to be populated.\nIn nested path 'async / server', 'server' has 2 directory entries: await, use.\nAt level 3, in directory path 'async > server > await', 'await' awaits content.\nAt level 3, in directory path 'async \u2192 server \u2192 use', Inside 'use', you'll find it has nothing inside.\nIn the root directory, 'sync' bundles 2 directory entries: client, server.\nIn nested path 'sync / client', 'client' encompasses 3 directory entries: access, has, spread.\nIn nested path 'sync / client / access', Inside 'access', you'll find it is a vacant space.\nAt level 3, in directory path 'sync > client > has', Inside 'has', you'll find it holds no subdirectories at the moment.\nIn nested path 'sync \u2192 client \u2192 spread', The 'spread' collection is empty.\nAt level 2, in directory path 'sync \u2192 server', 'server' hosts 3 directory entries: access, has, spread.\nIn nested path 'sync > server > access', 'access' is devoid of content.\nAt level 3, in directory path 'sync > server > has', Inside 'has', you'll find it is barren.\nAt level 3, in directory path 'sync / server / spread', 'spread' awaits content.\nBack to the top level.\n"}