prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  plumbing
   +--cache
   +--color
   +--filemode
   +--format
   |   +--config
   |   +--diff
   |   +--gitignore
   |   +--idxfile
   |   +--index
   |   +--objfile
   |   +--packfile
   |   `--pktline
   +--hash
   +--object
   +--protocol
   |   `--packp
   |       +--capability
   |       `--sideband
   +--revlist
   +--storer
  ```
  
  Convert this description:
  
  fixtures is a head directory that houses 4 subdirectories. Notable ones include many-pkgs, many-pkgs-2, many-pkgs-with-different-manifest-types among others.
  
  Let me break down the arrangement for you:
  
  At the top level, 'many-pkgs' houses 2 folders: components, libs.
  Within directory hierarchy 'many-pkgs → components', Within 'components', you'll find 2 nested folders for code structure.
  At level 3, in directory path 'many-pkgs / components / component-1', 'component-1' is unpopulated.
  At level 3, in directory path 'many-pkgs / components / component-2', 'component-2' has no content.
  In nested path 'many-pkgs > libs', 'libs' carries 1 subfolders: foo.
  At level 3, in directory path 'many-pkgs > libs > foo', The 'foo' container is blank.
  Back to the top level.
  In the root directory, 'many-pkgs-2' possesses 2 child directories: components, libs.
  In nested path 'many-pkgs-2 / components', Within 'components', you'll find 2 subdirectories for code structure.
  Within directory hierarchy 'many-pkgs-2 → components → component-1', The 'component-1' directory is an empty container.
  In nested path 'many-pkgs-2 / components / component-2', The 'component-2' collection stands empty.
  Within directory hierarchy 'many-pkgs-2 > libs', 'libs' encapsulates 1 subdirectory elements: foo.
  Within directory hierarchy 'many-pkgs-2 / libs / foo', Inside 'foo', you'll find it appears to be unused.
  Back to the top level.
  At the main level, 'many-pkgs-with-different-manifest-types' hosts 2 nested folders: components, libs.
  In nested path 'many-pkgs-with-different-manifest-types → components', 'components' carries 2 subdirectories that organize the source code.
  At level 3, in directory path 'many-pkgs-with-different-manifest-types / components / component-1', 'component-1' contains nothing at present.
  At level 3, in directory path 'many-pkgs-with-different-manifest-types > components > component-2', The 'component-2' compartment has nothing inside.
  Within directory hierarchy 'many-pkgs-with-different-manifest-types → libs', 'libs' stores 1 directory entries: foo.
  In nested path 'many-pkgs-with-different-manifest-types / libs / foo', Inside 'foo', you'll find it appears to be unused.
  At the top level, 'one-pkg' includes 1 subdirectory elements: foo.
  In nested path 'one-pkg → foo', The 'foo' compartment remains unused.
  
  
  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 houses 4 subdirectories. Notable ones include many-pkgs, many-pkgs-2, many-pkgs-with-different-manifest-types among others.\n\nLet me break down the arrangement for you:\n\nAt the top level, 'many-pkgs' houses 2 folders: components, libs.\nWithin directory hierarchy 'many-pkgs \u2192 components', Within 'components', you'll find 2 nested folders for code structure.\nAt level 3, in directory path 'many-pkgs / components / component-1', 'component-1' is unpopulated.\nAt level 3, in directory path 'many-pkgs / components / component-2', 'component-2' has no content.\nIn nested path 'many-pkgs > libs', 'libs' carries 1 subfolders: foo.\nAt level 3, in directory path 'many-pkgs > libs > foo', The 'foo' container is blank.\nBack to the top level.\nIn the root directory, 'many-pkgs-2' possesses 2 child directories: components, libs.\nIn nested path 'many-pkgs-2 / components', Within 'components', you'll find 2 subdirectories for code structure.\nWithin directory hierarchy 'many-pkgs-2 \u2192 components \u2192 component-1', The 'component-1' directory is an empty container.\nIn nested path 'many-pkgs-2 / components / component-2', The 'component-2' collection stands empty.\nWithin directory hierarchy 'many-pkgs-2 > libs', 'libs' encapsulates 1 subdirectory elements: foo.\nWithin directory hierarchy 'many-pkgs-2 / libs / foo', Inside 'foo', you'll find it appears to be unused.\nBack to the top level.\nAt the main level, 'many-pkgs-with-different-manifest-types' hosts 2 nested folders: components, libs.\nIn nested path 'many-pkgs-with-different-manifest-types \u2192 components', 'components' carries 2 subdirectories that organize the source code.\nAt level 3, in directory path 'many-pkgs-with-different-manifest-types / components / component-1', 'component-1' contains nothing at present.\nAt level 3, in directory path 'many-pkgs-with-different-manifest-types > components > component-2', The 'component-2' compartment has nothing inside.\nWithin directory hierarchy 'many-pkgs-with-different-manifest-types \u2192 libs', 'libs' stores 1 directory entries: foo.\nIn nested path 'many-pkgs-with-different-manifest-types / libs / foo', Inside 'foo', you'll find it appears to be unused.\nAt the top level, 'one-pkg' includes 1 subdirectory elements: foo.\nIn nested path 'one-pkg \u2192 foo', The 'foo' compartment remains unused.\n"}