prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  src
   +--constructors
   |   `--test
   +--hoc
   +--models
   |   `--test
   |       `--__snapshots__
   +--native
   |   `--test
   +--sheet
   |   `--test
   +--test
   |   `--__snapshots__
   `--utils
       `--test
  ```
  
  Convert this description:
  
  read-manifest is a central directory that houses 2 subdirectories: src and test.
  At the top level, Within 'src', you'll find 1 child directories for code structure.
  At level 2, in directory path 'src / errors', Inside 'errors', you'll find it has no folders inside.
  In the root directory, 'test' includes 1 test-related directories.
  In nested path 'test / __fixtures__', '__fixtures__' houses 21 a few nested folders.
  Within directory hierarchy 'test → __fixtures__ → array', 'array' has nothing inside.
  Within directory hierarchy 'test / __fixtures__ / catalog-invalid-array', The 'catalog-invalid-array' directory contains no subdirectories.
  In nested path 'test → __fixtures__ → catalog-invalid-object', The 'catalog-invalid-object' compartment is unpopulated.
  In nested path 'test > __fixtures__ > catalog-invalid-specifier', 'catalog-invalid-specifier' is a vacant space.
  Within directory hierarchy 'test / __fixtures__ / catalog-ok', The 'catalog-ok' section has been left empty.
  At level 3, in directory path 'test → __fixtures__ → catalogs-conflicting-defaults', The 'catalogs-conflicting-defaults' compartment has no folders inside.
  At level 3, in directory path 'test / __fixtures__ / catalogs-invalid-array', Inside 'catalogs-invalid-array', you'll find it awaits content.
  At level 3, in directory path 'test > __fixtures__ > catalogs-invalid-named-catalog-array', The 'catalogs-invalid-named-catalog-array' directory is devoid of content.
  At level 3, in directory path 'test / __fixtures__ / catalogs-invalid-named-catalog-object', Inside 'catalogs-invalid-named-catalog-object', you'll find it sits empty.
  In nested path 'test > __fixtures__ > catalogs-invalid-named-catalog-specifier', Inside 'catalogs-invalid-named-catalog-specifier', you'll find it is currently empty.
  Within directory hierarchy 'test > __fixtures__ > catalogs-invalid-object', 'catalogs-invalid-object' has nothing inside.
  At level 3, in directory path 'test / __fixtures__ / catalogs-ok', Inside 'catalogs-ok', you'll find it stands empty.
  At level 3, in directory path 'test / __fixtures__ / empty', The 'empty' container has nothing inside.
  Within directory hierarchy 'test / __fixtures__ / no-workspace-file', 'no-workspace-file' groups 1 nested folders: pkg.
  Within directory hierarchy 'test / __fixtures__ / no-workspace-file / pkg', 'pkg' appears to be unused.
  At level 3, in directory path 'test / __fixtures__ / null', 'null' is devoid of content.
  Within directory hierarchy 'test / __fixtures__ / ok', The 'ok' repository contains no subdirectories.
  At level 3, in directory path 'test > __fixtures__ > packages-contains-empty', The 'packages-contains-empty' compartment is an empty container.
  At level 3, in directory path 'test / __fixtures__ / packages-contains-number', The 'packages-contains-number' container remains unused.
  At level 3, in directory path 'test > __fixtures__ > packages-empty', 'packages-empty' appears to be unused.
  Within directory hierarchy 'test / __fixtures__ / packages-string', 'packages-string' sits empty.
  Within directory hierarchy 'test > __fixtures__ > string', 'string' lacks any subdirectories.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "read-manifest\n +--src\n |   `--errors\n `--test\n     `--__fixtures__\n         +--array\n         +--catalog-invalid-array\n         +--catalog-invalid-object\n         +--catalog-invalid-specifier\n         +--catalog-ok\n         +--catalogs-conflicting-defaults\n         +--catalogs-invalid-array\n         +--catalogs-invalid-named-catalog-array\n         +--catalogs-invalid-named-catalog-object\n         +--catalogs-invalid-named-catalog-specifier\n         +--catalogs-invalid-object\n         +--catalogs-ok\n         +--empty\n         +--no-workspace-file\n         |   `--pkg\n         +--null\n         +--ok\n         +--packages-contains-empty\n         +--packages-contains-number\n         +--packages-empty\n         +--packages-string\n         `--string", "description": "read-manifest is a central directory that houses 2 subdirectories: src and test.\nAt the top level, Within 'src', you'll find 1 child directories for code structure.\nAt level 2, in directory path 'src / errors', Inside 'errors', you'll find it has no folders inside.\nIn the root directory, 'test' includes 1 test-related directories.\nIn nested path 'test / __fixtures__', '__fixtures__' houses 21 a few nested folders.\nWithin directory hierarchy 'test \u2192 __fixtures__ \u2192 array', 'array' has nothing inside.\nWithin directory hierarchy 'test / __fixtures__ / catalog-invalid-array', The 'catalog-invalid-array' directory contains no subdirectories.\nIn nested path 'test \u2192 __fixtures__ \u2192 catalog-invalid-object', The 'catalog-invalid-object' compartment is unpopulated.\nIn nested path 'test > __fixtures__ > catalog-invalid-specifier', 'catalog-invalid-specifier' is a vacant space.\nWithin directory hierarchy 'test / __fixtures__ / catalog-ok', The 'catalog-ok' section has been left empty.\nAt level 3, in directory path 'test \u2192 __fixtures__ \u2192 catalogs-conflicting-defaults', The 'catalogs-conflicting-defaults' compartment has no folders inside.\nAt level 3, in directory path 'test / __fixtures__ / catalogs-invalid-array', Inside 'catalogs-invalid-array', you'll find it awaits content.\nAt level 3, in directory path 'test > __fixtures__ > catalogs-invalid-named-catalog-array', The 'catalogs-invalid-named-catalog-array' directory is devoid of content.\nAt level 3, in directory path 'test / __fixtures__ / catalogs-invalid-named-catalog-object', Inside 'catalogs-invalid-named-catalog-object', you'll find it sits empty.\nIn nested path 'test > __fixtures__ > catalogs-invalid-named-catalog-specifier', Inside 'catalogs-invalid-named-catalog-specifier', you'll find it is currently empty.\nWithin directory hierarchy 'test > __fixtures__ > catalogs-invalid-object', 'catalogs-invalid-object' has nothing inside.\nAt level 3, in directory path 'test / __fixtures__ / catalogs-ok', Inside 'catalogs-ok', you'll find it stands empty.\nAt level 3, in directory path 'test / __fixtures__ / empty', The 'empty' container has nothing inside.\nWithin directory hierarchy 'test / __fixtures__ / no-workspace-file', 'no-workspace-file' groups 1 nested folders: pkg.\nWithin directory hierarchy 'test / __fixtures__ / no-workspace-file / pkg', 'pkg' appears to be unused.\nAt level 3, in directory path 'test / __fixtures__ / null', 'null' is devoid of content.\nWithin directory hierarchy 'test / __fixtures__ / ok', The 'ok' repository contains no subdirectories.\nAt level 3, in directory path 'test > __fixtures__ > packages-contains-empty', The 'packages-contains-empty' compartment is an empty container.\nAt level 3, in directory path 'test / __fixtures__ / packages-contains-number', The 'packages-contains-number' container remains unused.\nAt level 3, in directory path 'test > __fixtures__ > packages-empty', 'packages-empty' appears to be unused.\nWithin directory hierarchy 'test / __fixtures__ / packages-string', 'packages-string' sits empty.\nWithin directory hierarchy 'test > __fixtures__ > string', 'string' lacks any subdirectories.\n"}