prompt: Your task is to convert the following English description into an ASCII tree format.
  
  test is a top-level directory that assembles 5 subdirectories. Notable ones include fixtures, hoistedNodeLinker, install among others.
  
  Let me break down the composition for you:
  
  In the root directory, 'fixtures' houses 5 different contained folders.
  In nested path 'fixtures / lockfile-v5', The 'lockfile-v5' section is vacant.
  In nested path 'fixtures / patch-pkg', 'patch-pkg' remains unused.
  In nested path 'fixtures > symlink-workspace', 'symlink-workspace' possesses 2 contained folders: app1, app2.
  At level 3, in directory path 'fixtures / symlink-workspace / app1', 'app1' keeps 1 contained folders: packages.
  At level 4, in directory path 'fixtures → symlink-workspace → app1 → packages', 'packages' organizes 1 directory entries: public.
  At level 5, in directory path 'fixtures → symlink-workspace → app1 → packages → public', 'public' possesses 2 subfolders: bar, foo.
  At level 6, in directory path 'fixtures / symlink-workspace / app1 / packages / public / bar', The 'bar' repository has been left empty.
  Within directory hierarchy 'fixtures → symlink-workspace → app1 → packages → public → foo', 'foo' is vacant.
  Within directory hierarchy 'fixtures → symlink-workspace → app2', 'app2' bundles 1 directory entries: packages.
  Within directory hierarchy 'fixtures / symlink-workspace / app2 / packages', 'packages' holds no subdirectories at the moment.
  In nested path 'fixtures > tar-pkg-with-peers', Inside 'tar-pkg-with-peers', you'll find it appears to be unused.
  At level 2, in directory path 'fixtures > tooling-that-needs-node-path', 'tooling-that-needs-node-path' is unpopulated.
  Back to the top level.
  At the main level, The 'hoistedNodeLinker' collection stands empty.
  At the top level, 'install' sits empty.
  At the top level, Inside 'registry-mirror', you'll find it is an empty container.
  In the root directory, Inside 'utils', you'll find it is currently empty.
  
  
  Format your response in this style:
  ```
  ide
   +--visualstudio
   |   `--tasks
   |       `--internal
   `--xcode
       `--tasks
           `--internal
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "test\n +--fixtures\n |   +--lockfile-v5\n |   +--patch-pkg\n |   +--symlink-workspace\n |   |   +--app1\n |   |   |   `--packages\n |   |   |       `--public\n |   |   |           +--bar\n |   |   |           `--foo\n |   |   `--app2\n |   |       `--packages\n |   +--tar-pkg-with-peers\n |   `--tooling-that-needs-node-path\n +--hoistedNodeLinker\n +--install\n +--registry-mirror\n `--utils", "description": "test is a top-level directory that assembles 5 subdirectories. Notable ones include fixtures, hoistedNodeLinker, install among others.\n\nLet me break down the composition for you:\n\nIn the root directory, 'fixtures' houses 5 different contained folders.\nIn nested path 'fixtures / lockfile-v5', The 'lockfile-v5' section is vacant.\nIn nested path 'fixtures / patch-pkg', 'patch-pkg' remains unused.\nIn nested path 'fixtures > symlink-workspace', 'symlink-workspace' possesses 2 contained folders: app1, app2.\nAt level 3, in directory path 'fixtures / symlink-workspace / app1', 'app1' keeps 1 contained folders: packages.\nAt level 4, in directory path 'fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages', 'packages' organizes 1 directory entries: public.\nAt level 5, in directory path 'fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages \u2192 public', 'public' possesses 2 subfolders: bar, foo.\nAt level 6, in directory path 'fixtures / symlink-workspace / app1 / packages / public / bar', The 'bar' repository has been left empty.\nWithin directory hierarchy 'fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages \u2192 public \u2192 foo', 'foo' is vacant.\nWithin directory hierarchy 'fixtures \u2192 symlink-workspace \u2192 app2', 'app2' bundles 1 directory entries: packages.\nWithin directory hierarchy 'fixtures / symlink-workspace / app2 / packages', 'packages' holds no subdirectories at the moment.\nIn nested path 'fixtures > tar-pkg-with-peers', Inside 'tar-pkg-with-peers', you'll find it appears to be unused.\nAt level 2, in directory path 'fixtures > tooling-that-needs-node-path', 'tooling-that-needs-node-path' is unpopulated.\nBack to the top level.\nAt the main level, The 'hoistedNodeLinker' collection stands empty.\nAt the top level, 'install' sits empty.\nAt the top level, Inside 'registry-mirror', you'll find it is an empty container.\nIn the root directory, Inside 'utils', you'll find it is currently empty.\n"}