prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  samples
   +--basic
   |   `--_expected
   +--missing-dependency-resolution
   +--missing-entry-resolution
   +--missing-load
   +--renormalizes-external-paths
   |   `--_expected
   `--supports-hashes
       `--_expected
  ```
  
  Convert this description:
  
  core is a origin directory that organizes 2 subdirectories: src and test.
  In the root directory, Within 'src', you'll find 2 directory entries for code structure.
  Within directory hierarchy 'src → install', 'install' incorporates 1 subdirectory elements: checkCompatibility.
  At level 3, in directory path 'src → install → checkCompatibility', Inside 'checkCompatibility', you'll find it hasn't been filled with any content.
  Within directory hierarchy 'src > uninstall', The 'uninstall' repository stands empty.
  Back to the top level.
  At the main level, 'test' houses 5 folders for testing purposes.
  At level 2, in directory path 'test → fixtures', 'fixtures' encapsulates 5 numerous directory entries.
  At level 3, in directory path 'test > fixtures > lockfile-v5', The 'lockfile-v5' collection appears to be unused.
  Within directory hierarchy 'test / fixtures / patch-pkg', Inside 'patch-pkg', you'll find it has yet to be populated.
  At level 3, in directory path 'test → fixtures → symlink-workspace', 'symlink-workspace' stores 2 child directories: app1, app2.
  Within directory hierarchy 'test > fixtures > symlink-workspace > app1', 'app1' organizes 1 subdirectories: packages.
  In nested path 'test → fixtures → symlink-workspace → app1 → packages', 'packages' encapsulates 1 contained folders: public.
  In nested path 'test / fixtures / symlink-workspace / app1 / packages / public', 'public' features 2 directory entries: bar, foo.
  At level 7, in directory path 'test → fixtures → symlink-workspace → app1 → packages → public → bar', 'bar' has no content.
  Within directory hierarchy 'test → fixtures → symlink-workspace → app1 → packages → public → foo', The 'foo' directory remains unused.
  At level 4, in directory path 'test → fixtures → symlink-workspace → app2', 'app2' groups 1 nested folders: packages.
  At level 5, in directory path 'test / fixtures / symlink-workspace / app2 / packages', 'packages' hasn't been filled with any content.
  In nested path 'test > fixtures > tar-pkg-with-peers', The 'tar-pkg-with-peers' storage space lacks any subdirectories.
  Within directory hierarchy 'test > fixtures > tooling-that-needs-node-path', Inside 'tooling-that-needs-node-path', you'll find it awaits content.
  In nested path 'test → hoistedNodeLinker', 'hoistedNodeLinker' contains no subdirectories.
  At level 2, in directory path 'test → install', The 'install' collection is barren.
  In nested path 'test / registry-mirror', The 'registry-mirror' folder holds no subdirectories at the moment.
  Within directory hierarchy 'test → utils', Inside 'utils', you'll find it is devoid of content.
  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 origin directory that organizes 2 subdirectories: src and test.\nIn the root directory, Within 'src', you'll find 2 directory entries for code structure.\nWithin directory hierarchy 'src \u2192 install', 'install' incorporates 1 subdirectory elements: checkCompatibility.\nAt level 3, in directory path 'src \u2192 install \u2192 checkCompatibility', Inside 'checkCompatibility', you'll find it hasn't been filled with any content.\nWithin directory hierarchy 'src > uninstall', The 'uninstall' repository stands empty.\nBack to the top level.\nAt the main level, 'test' houses 5 folders for testing purposes.\nAt level 2, in directory path 'test \u2192 fixtures', 'fixtures' encapsulates 5 numerous directory entries.\nAt level 3, in directory path 'test > fixtures > lockfile-v5', The 'lockfile-v5' collection appears to be unused.\nWithin directory hierarchy 'test / fixtures / patch-pkg', Inside 'patch-pkg', you'll find it has yet to be populated.\nAt level 3, in directory path 'test \u2192 fixtures \u2192 symlink-workspace', 'symlink-workspace' stores 2 child directories: app1, app2.\nWithin directory hierarchy 'test > fixtures > symlink-workspace > app1', 'app1' organizes 1 subdirectories: packages.\nIn nested path 'test \u2192 fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages', 'packages' encapsulates 1 contained folders: public.\nIn nested path 'test / fixtures / symlink-workspace / app1 / packages / public', 'public' features 2 directory entries: bar, foo.\nAt level 7, in directory path 'test \u2192 fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages \u2192 public \u2192 bar', 'bar' has no content.\nWithin directory hierarchy 'test \u2192 fixtures \u2192 symlink-workspace \u2192 app1 \u2192 packages \u2192 public \u2192 foo', The 'foo' directory remains unused.\nAt level 4, in directory path 'test \u2192 fixtures \u2192 symlink-workspace \u2192 app2', 'app2' groups 1 nested folders: packages.\nAt level 5, in directory path 'test / fixtures / symlink-workspace / app2 / packages', 'packages' hasn't been filled with any content.\nIn nested path 'test > fixtures > tar-pkg-with-peers', The 'tar-pkg-with-peers' storage space lacks any subdirectories.\nWithin directory hierarchy 'test > fixtures > tooling-that-needs-node-path', Inside 'tooling-that-needs-node-path', you'll find it awaits content.\nIn nested path 'test \u2192 hoistedNodeLinker', 'hoistedNodeLinker' contains no subdirectories.\nAt level 2, in directory path 'test \u2192 install', The 'install' collection is barren.\nIn nested path 'test / registry-mirror', The 'registry-mirror' folder holds no subdirectories at the moment.\nWithin directory hierarchy 'test \u2192 utils', Inside 'utils', you'll find it is devoid of content.\nBack to the top level.\n"}