prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  ws
   +--__snapshots__
   `--test
       `--__snapshots__
  ```
  
  Convert this description:
  
  fixtures is a head directory that gathers 4 subdirectories. Notable ones include many-pkgs, many-pkgs-2, many-pkgs-with-different-manifest-types among others.
  
  Let me break down the hierarchy for you:
  
  At the top level, 'many-pkgs' contains 2 directory entries: components, libs.
  At level 2, in directory path 'many-pkgs → components', Within 'components', you'll find 2 subdirectories for code structure.
  At level 3, in directory path 'many-pkgs > components > component-1', 'component-1' has nothing inside.
  Within directory hierarchy 'many-pkgs / components / component-2', 'component-2' has no folders inside.
  At level 2, in directory path 'many-pkgs → libs', 'libs' groups 1 nested folders: foo.
  At level 3, in directory path 'many-pkgs > libs > foo', 'foo' is blank.
  Back to the top level.
  At the top level, 'many-pkgs-2' bundles 2 directories: components, libs.
  In nested path 'many-pkgs-2 / components', Within 'components', you'll find 2 directories for code structure.
  At level 3, in directory path 'many-pkgs-2 → components → component-1', Inside 'component-1', you'll find it is devoid of content.
  Within directory hierarchy 'many-pkgs-2 / components / component-2', Inside 'component-2', you'll find it is vacant.
  Within directory hierarchy 'many-pkgs-2 → libs', 'libs' holds 1 subdirectories: foo.
  Within directory hierarchy 'many-pkgs-2 > libs > foo', The 'foo' container remains unused.
  Back to the top level.
  At the top level, 'many-pkgs-with-different-manifest-types' retains 2 subfolders: components, libs.
  In nested path 'many-pkgs-with-different-manifest-types → components', Within 'components', you'll find 2 child directories for code structure.
  At level 3, in directory path 'many-pkgs-with-different-manifest-types → components → component-1', Inside 'component-1', you'll find it appears to be unused.
  At level 3, in directory path 'many-pkgs-with-different-manifest-types / components / component-2', The 'component-2' collection sits empty.
  In nested path 'many-pkgs-with-different-manifest-types / libs', 'libs' includes 1 directory entries: foo.
  In nested path 'many-pkgs-with-different-manifest-types → libs → foo', Inside 'foo', you'll find it is unpopulated.
  At the top level, 'one-pkg' hosts 1 subdirectories: foo.
  In nested path 'one-pkg → foo', 'foo' is an empty container.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "fixtures\n +--many-pkgs\n |   +--components\n |   |   +--component-1\n |   |   `--component-2\n |   `--libs\n |       `--foo\n +--many-pkgs-2\n |   +--components\n |   |   +--component-1\n |   |   `--component-2\n |   `--libs\n |       `--foo\n +--many-pkgs-with-different-manifest-types\n |   +--components\n |   |   +--component-1\n |   |   `--component-2\n |   `--libs\n |       `--foo\n `--one-pkg\n     `--foo", "description": "fixtures is a head directory that gathers 4 subdirectories. Notable ones include many-pkgs, many-pkgs-2, many-pkgs-with-different-manifest-types among others.\n\nLet me break down the hierarchy for you:\n\nAt the top level, 'many-pkgs' contains 2 directory entries: components, libs.\nAt level 2, in directory path 'many-pkgs \u2192 components', Within 'components', you'll find 2 subdirectories for code structure.\nAt level 3, in directory path 'many-pkgs > components > component-1', 'component-1' has nothing inside.\nWithin directory hierarchy 'many-pkgs / components / component-2', 'component-2' has no folders inside.\nAt level 2, in directory path 'many-pkgs \u2192 libs', 'libs' groups 1 nested folders: foo.\nAt level 3, in directory path 'many-pkgs > libs > foo', 'foo' is blank.\nBack to the top level.\nAt the top level, 'many-pkgs-2' bundles 2 directories: components, libs.\nIn nested path 'many-pkgs-2 / components', Within 'components', you'll find 2 directories for code structure.\nAt level 3, in directory path 'many-pkgs-2 \u2192 components \u2192 component-1', Inside 'component-1', you'll find it is devoid of content.\nWithin directory hierarchy 'many-pkgs-2 / components / component-2', Inside 'component-2', you'll find it is vacant.\nWithin directory hierarchy 'many-pkgs-2 \u2192 libs', 'libs' holds 1 subdirectories: foo.\nWithin directory hierarchy 'many-pkgs-2 > libs > foo', The 'foo' container remains unused.\nBack to the top level.\nAt the top level, 'many-pkgs-with-different-manifest-types' retains 2 subfolders: components, libs.\nIn nested path 'many-pkgs-with-different-manifest-types \u2192 components', Within 'components', you'll find 2 child directories for code structure.\nAt level 3, in directory path 'many-pkgs-with-different-manifest-types \u2192 components \u2192 component-1', Inside 'component-1', you'll find it appears to be unused.\nAt level 3, in directory path 'many-pkgs-with-different-manifest-types / components / component-2', The 'component-2' collection sits empty.\nIn nested path 'many-pkgs-with-different-manifest-types / libs', 'libs' includes 1 directory entries: foo.\nIn nested path 'many-pkgs-with-different-manifest-types \u2192 libs \u2192 foo', Inside 'foo', you'll find it is unpopulated.\nAt the top level, 'one-pkg' hosts 1 subdirectories: foo.\nIn nested path 'one-pkg \u2192 foo', 'foo' is an empty container.\n"}