prompt: Your task is to convert the following English description into an ASCII tree format.
  
  gradle is a master directory that incorporates 2 subdirectories: launcher and tooling.
  At the main level, 'launcher' groups 5 numerous folders.
  Within directory hierarchy 'launcher > bootstrap', The 'bootstrap' directory hasn't been filled with any content.
  At level 2, in directory path 'launcher / cli', 'cli' includes 1 contained folders: converter.
  In nested path 'launcher / cli / converter', 'converter' is a vacant space.
  Within directory hierarchy 'launcher > continuous', Inside 'continuous', you'll find it has been left empty.
  In nested path 'launcher / daemon', 'daemon' bundles 3 contained folders: protocol, registry, server.
  In nested path 'launcher → daemon → protocol', 'protocol' appears to be unused.
  Within directory hierarchy 'launcher > daemon > registry', The 'registry' repository contains no subdirectories.
  In nested path 'launcher > daemon > server', 'server' organizes 4 a few subdirectories.
  Within directory hierarchy 'launcher → daemon → server → exec', The 'exec' section is empty.
  Within directory hierarchy 'launcher / daemon / server / expiry', 'expiry' is an empty container.
  At level 4, in directory path 'launcher > daemon > server > health', 'health' encompasses 1 child directories: gc.
  Within directory hierarchy 'launcher → daemon → server → health → gc', The 'gc' section is devoid of content.
  In nested path 'launcher → daemon → server → scaninfo', The 'scaninfo' data structure lacks any subdirectories.
  At level 2, in directory path 'launcher → exec', Inside 'exec', you'll find it awaits content.
  In the root directory, 'tooling' houses 1 directory entries: internal.
  Within directory hierarchy 'tooling / internal', 'internal' maintains 1 subdirectory elements: provider.
  At level 3, in directory path 'tooling > internal > provider', 'provider' comprises 3 directory entries: action, connection, continuous.
  At level 4, in directory path 'tooling → internal → provider → action', The 'action' storage space is barren.
  At level 4, in directory path 'tooling / internal / provider / connection', Inside 'connection', you'll find it has been left empty.
  In nested path 'tooling / internal / provider / continuous', Inside 'continuous', you'll find it is a vacant space.
  
  
  Format your response in this style:
  ```
  params-hooks-compat
   +--app
   |   `--app
   |       `--[slug]
   +--pages
   |   `--pages
   `--shared
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "gradle\n +--launcher\n |   +--bootstrap\n |   +--cli\n |   |   `--converter\n |   +--continuous\n |   +--daemon\n |   |   +--protocol\n |   |   +--registry\n |   |   `--server\n |   |       +--exec\n |   |       +--expiry\n |   |       +--health\n |   |       |   `--gc\n |   |       `--scaninfo\n |   `--exec\n `--tooling\n     `--internal\n         `--provider\n             +--action\n             +--connection\n             `--continuous", "description": "gradle is a master directory that incorporates 2 subdirectories: launcher and tooling.\nAt the main level, 'launcher' groups 5 numerous folders.\nWithin directory hierarchy 'launcher > bootstrap', The 'bootstrap' directory hasn't been filled with any content.\nAt level 2, in directory path 'launcher / cli', 'cli' includes 1 contained folders: converter.\nIn nested path 'launcher / cli / converter', 'converter' is a vacant space.\nWithin directory hierarchy 'launcher > continuous', Inside 'continuous', you'll find it has been left empty.\nIn nested path 'launcher / daemon', 'daemon' bundles 3 contained folders: protocol, registry, server.\nIn nested path 'launcher \u2192 daemon \u2192 protocol', 'protocol' appears to be unused.\nWithin directory hierarchy 'launcher > daemon > registry', The 'registry' repository contains no subdirectories.\nIn nested path 'launcher > daemon > server', 'server' organizes 4 a few subdirectories.\nWithin directory hierarchy 'launcher \u2192 daemon \u2192 server \u2192 exec', The 'exec' section is empty.\nWithin directory hierarchy 'launcher / daemon / server / expiry', 'expiry' is an empty container.\nAt level 4, in directory path 'launcher > daemon > server > health', 'health' encompasses 1 child directories: gc.\nWithin directory hierarchy 'launcher \u2192 daemon \u2192 server \u2192 health \u2192 gc', The 'gc' section is devoid of content.\nIn nested path 'launcher \u2192 daemon \u2192 server \u2192 scaninfo', The 'scaninfo' data structure lacks any subdirectories.\nAt level 2, in directory path 'launcher \u2192 exec', Inside 'exec', you'll find it awaits content.\nIn the root directory, 'tooling' houses 1 directory entries: internal.\nWithin directory hierarchy 'tooling / internal', 'internal' maintains 1 subdirectory elements: provider.\nAt level 3, in directory path 'tooling > internal > provider', 'provider' comprises 3 directory entries: action, connection, continuous.\nAt level 4, in directory path 'tooling \u2192 internal \u2192 provider \u2192 action', The 'action' storage space is barren.\nAt level 4, in directory path 'tooling / internal / provider / connection', Inside 'connection', you'll find it has been left empty.\nIn nested path 'tooling / internal / provider / continuous', Inside 'continuous', you'll find it is a vacant space.\n"}