prompt: Your task is to convert the following English description into an ASCII tree format.
  
  test is a head directory that includes 5 subdirectories. Notable ones include fixtures, global-bin-dir, global-bin-dir-windows among others.
  
  Let me break down the architecture for you:
  
  In the root directory, 'fixtures' includes 6 different directories.
  At level 2, in directory path 'fixtures → has-env-in-key', Inside 'has-env-in-key', you'll find it has no content.
  In nested path 'fixtures > has-number-setting', Inside 'has-number-setting', you'll find it is unpopulated.
  Within directory hierarchy 'fixtures > never-built-dependencies', Inside 'never-built-dependencies', you'll find it appears to be unused.
  At level 2, in directory path 'fixtures / pkg-using-workspaces', 'pkg-using-workspaces' has nothing inside.
  At level 2, in directory path 'fixtures / pkg-with-valid-workspace-yaml', 'pkg-with-valid-workspace-yaml' has yet to be populated.
  In nested path 'fixtures → settings-in-workspace-yaml', The 'settings-in-workspace-yaml' container hasn't been filled with any content.
  At the main level, 'global-bin-dir' hosts 1 child directories: etc.
  In nested path 'global-bin-dir → etc', Inside 'etc', you'll find it is empty.
  Back to the top level.
  At the main level, 'global-bin-dir-windows' includes 1 nested folders: etc.
  At level 2, in directory path 'global-bin-dir-windows / etc', Inside 'etc', you'll find it is unpopulated.
  In the root directory, 'has-workspace-yaml' has no content.
  At the main level, The 'using-test-pattern' storage space awaits content.
  
  
  Format your response in this style:
  ```
  samples
   +--basic
   |   `--_expected
   +--missing-dependency-resolution
   +--missing-entry-resolution
   +--missing-load
   +--renormalizes-external-paths
   |   `--_expected
   `--supports-hashes
       `--_expected
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "test\n +--fixtures\n |   +--has-env-in-key\n |   +--has-number-setting\n |   +--never-built-dependencies\n |   +--pkg-using-workspaces\n |   +--pkg-with-valid-workspace-yaml\n |   `--settings-in-workspace-yaml\n +--global-bin-dir\n |   `--etc\n +--global-bin-dir-windows\n |   `--etc\n +--has-workspace-yaml\n `--using-test-pattern", "description": "test is a head directory that includes 5 subdirectories. Notable ones include fixtures, global-bin-dir, global-bin-dir-windows among others.\n\nLet me break down the architecture for you:\n\nIn the root directory, 'fixtures' includes 6 different directories.\nAt level 2, in directory path 'fixtures \u2192 has-env-in-key', Inside 'has-env-in-key', you'll find it has no content.\nIn nested path 'fixtures > has-number-setting', Inside 'has-number-setting', you'll find it is unpopulated.\nWithin directory hierarchy 'fixtures > never-built-dependencies', Inside 'never-built-dependencies', you'll find it appears to be unused.\nAt level 2, in directory path 'fixtures / pkg-using-workspaces', 'pkg-using-workspaces' has nothing inside.\nAt level 2, in directory path 'fixtures / pkg-with-valid-workspace-yaml', 'pkg-with-valid-workspace-yaml' has yet to be populated.\nIn nested path 'fixtures \u2192 settings-in-workspace-yaml', The 'settings-in-workspace-yaml' container hasn't been filled with any content.\nAt the main level, 'global-bin-dir' hosts 1 child directories: etc.\nIn nested path 'global-bin-dir \u2192 etc', Inside 'etc', you'll find it is empty.\nBack to the top level.\nAt the main level, 'global-bin-dir-windows' includes 1 nested folders: etc.\nAt level 2, in directory path 'global-bin-dir-windows / etc', Inside 'etc', you'll find it is unpopulated.\nIn the root directory, 'has-workspace-yaml' has no content.\nAt the main level, The 'using-test-pattern' storage space awaits content.\n"}