prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  pre-compiled-headers
   +--groovy
   |   `--src
   |       +--hello
   |       |   +--cpp
   |       |   `--headers
   |       `--main
   |           `--cpp
   `--tests
  ```
  
  Convert this description:
  
  fixtures is a base directory that bundles 5 subdirectories. Notable ones include lockfile-v5, patch-pkg, symlink-workspace among others.
  
  Let me break down the construction for you:
  
  In the root directory, Inside 'lockfile-v5', you'll find it has been left empty.
  In the root directory, 'patch-pkg' appears to be unused.
  At the top level, 'symlink-workspace' includes 2 folders: app1, app2.
  Within directory hierarchy 'symlink-workspace > app1', 'app1' holds 1 child directories: packages.
  In nested path 'symlink-workspace > app1 > packages', 'packages' shelters 1 subdirectories: public.
  At level 4, in directory path 'symlink-workspace → app1 → packages → public', 'public' contains 2 folders: bar, foo.
  At level 5, in directory path 'symlink-workspace > app1 > packages > public > bar', 'bar' stands empty.
  In nested path 'symlink-workspace / app1 / packages / public / foo', 'foo' has been left empty.
  Within directory hierarchy 'symlink-workspace / app2', 'app2' shelters 1 subdirectories: packages.
  At level 3, in directory path 'symlink-workspace > app2 > packages', Inside 'packages', you'll find it has yet to be populated.
  Back to the top level.
  In the root directory, 'tar-pkg-with-peers' has no content.
  In the root directory, The 'tooling-that-needs-node-path' data structure is vacant.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "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", "description": "fixtures is a base directory that bundles 5 subdirectories. Notable ones include lockfile-v5, patch-pkg, symlink-workspace among others.\n\nLet me break down the construction for you:\n\nIn the root directory, Inside 'lockfile-v5', you'll find it has been left empty.\nIn the root directory, 'patch-pkg' appears to be unused.\nAt the top level, 'symlink-workspace' includes 2 folders: app1, app2.\nWithin directory hierarchy 'symlink-workspace > app1', 'app1' holds 1 child directories: packages.\nIn nested path 'symlink-workspace > app1 > packages', 'packages' shelters 1 subdirectories: public.\nAt level 4, in directory path 'symlink-workspace \u2192 app1 \u2192 packages \u2192 public', 'public' contains 2 folders: bar, foo.\nAt level 5, in directory path 'symlink-workspace > app1 > packages > public > bar', 'bar' stands empty.\nIn nested path 'symlink-workspace / app1 / packages / public / foo', 'foo' has been left empty.\nWithin directory hierarchy 'symlink-workspace / app2', 'app2' shelters 1 subdirectories: packages.\nAt level 3, in directory path 'symlink-workspace > app2 > packages', Inside 'packages', you'll find it has yet to be populated.\nBack to the top level.\nIn the root directory, 'tar-pkg-with-peers' has no content.\nIn the root directory, The 'tooling-that-needs-node-path' data structure is vacant.\n"}