prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  ws
   +--__snapshots__
   `--test
       `--__snapshots__
  ```
  
  Convert this description:
  
  core is a top-level directory that includes 2 subdirectories: src and test.
  In the root directory, Within 'src', you'll find 2 directories for code structure.
  Within directory hierarchy 'src → install', 'install' retains 1 directories: checkCompatibility.
  In nested path 'src → install → checkCompatibility', The 'checkCompatibility' compartment is a vacant space.
  At level 2, in directory path 'src > uninstall', The 'uninstall' container lacks any subdirectories.
  At the top level, 'test' houses 5 folders for testing purposes.
  In nested path 'test / fixtures', 'fixtures' features 5 multiple directories.
  In nested path 'test / fixtures / lockfile-v5', The 'lockfile-v5' storage space stands empty.
  In nested path 'test → fixtures → patch-pkg', Inside 'patch-pkg', you'll find it lacks any subdirectories.
  At level 3, in directory path 'test → fixtures → symlink-workspace', 'symlink-workspace' contains 2 contained folders: app1, app2.
  In nested path 'test > fixtures > symlink-workspace > app1', 'app1' has 1 subdirectories: packages.
  Within directory hierarchy 'test > fixtures > symlink-workspace > app1 > packages', 'packages' maintains 1 directory entries: public.
  In nested path 'test / fixtures / symlink-workspace / app1 / packages / public', 'public' groups 2 contained folders: bar, foo.
  At level 7, in directory path 'test / fixtures / symlink-workspace / app1 / packages / public / bar', 'bar' is devoid of content.
  Within directory hierarchy 'test / fixtures / symlink-workspace / app1 / packages / public / foo', 'foo' has no folders inside.
  In nested path 'test / fixtures / symlink-workspace / app2', 'app2' holds 1 directories: packages.
  In nested path 'test / fixtures / symlink-workspace / app2 / packages', Inside 'packages', you'll find it is barren.
  In nested path 'test → fixtures → tar-pkg-with-peers', 'tar-pkg-with-peers' is blank.
  At level 3, in directory path 'test → fixtures → tooling-that-needs-node-path', 'tooling-that-needs-node-path' appears to be unused.
  At level 2, in directory path 'test / hoistedNodeLinker', Inside 'hoistedNodeLinker', you'll find it lacks any subdirectories.
  In nested path 'test / install', The 'install' section sits empty.
  In nested path 'test → registry-mirror', 'registry-mirror' is currently empty.
  At level 2, in directory path 'test / utils', The 'utils' data structure appears to be unused.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "core\n +--src\n |   +--install\n |   |   `--checkCompatibility\n |   `--uninstall\n `--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": "core is a top-level directory that includes 2 subdirectories: src and test.\nIn the root directory, Within 'src', you'll find 2 directories for code structure.\nWithin directory hierarchy 'src \u2192 install', 'install' retains 1 directories: checkCompatibility.\nIn nested path 'src \u2192 install \u2192 checkCompatibility', The 'checkCompatibility' compartment is a vacant space.\nAt level 2, in directory path 'src > uninstall', The 'uninstall' container lacks any subdirectories.\nAt the top level, 'test' houses 5 folders for testing purposes.\nIn nested path 'test / fixtures', 'fixtures' features 5 multiple directories.\nIn nested path 'test / fixtures / lockfile-v5', The 'lockfile-v5' storage space stands empty.\nIn nested path 'test \u2192 fixtures \u2192 patch-pkg', Inside 'patch-pkg', you'll find it lacks any subdirectories.\nAt level 3, in directory path 'test \u2192 fixtures \u2192 symlink-workspace', 'symlink-workspace' contains 2 contained folders: app1, app2.\nIn nested path 'test > fixtures > symlink-workspace > app1', 'app1' has 1 subdirectories: packages.\nWithin directory hierarchy 'test > fixtures > symlink-workspace > app1 > packages', 'packages' maintains 1 directory entries: public.\nIn nested path 'test / fixtures / symlink-workspace / app1 / packages / public', 'public' groups 2 contained folders: bar, foo.\nAt level 7, in directory path 'test / fixtures / symlink-workspace / app1 / packages / public / bar', 'bar' is devoid of content.\nWithin directory hierarchy 'test / fixtures / symlink-workspace / app1 / packages / public / foo', 'foo' has no folders inside.\nIn nested path 'test / fixtures / symlink-workspace / app2', 'app2' holds 1 directories: packages.\nIn nested path 'test / fixtures / symlink-workspace / app2 / packages', Inside 'packages', you'll find it is barren.\nIn nested path 'test \u2192 fixtures \u2192 tar-pkg-with-peers', 'tar-pkg-with-peers' is blank.\nAt level 3, in directory path 'test \u2192 fixtures \u2192 tooling-that-needs-node-path', 'tooling-that-needs-node-path' appears to be unused.\nAt level 2, in directory path 'test / hoistedNodeLinker', Inside 'hoistedNodeLinker', you'll find it lacks any subdirectories.\nIn nested path 'test / install', The 'install' section sits empty.\nIn nested path 'test \u2192 registry-mirror', 'registry-mirror' is currently empty.\nAt level 2, in directory path 'test / utils', The 'utils' data structure appears to be unused.\nBack to the top level.\n"}