prompt: Your task is to convert the following English description into an ASCII tree format.
  
  config is a head directory that collects 9 subdirectories. Notable ones include config, config-writer, deps-installer among others.
  
  Let me break down the setup for you:
  
  In the root directory, 'config' stores 2 nested folders: src, test.
  In nested path 'config → src', 'src' remains unused.
  Within directory hierarchy 'config / test', 'test' organizes tests across 5 separate subfolders.
  At level 3, in directory path 'config > test > fixtures', 'fixtures' possesses 6 numerous child directories.
  In nested path 'config > test > fixtures > has-env-in-key', Inside 'has-env-in-key', you'll find it has yet to be populated.
  In nested path 'config / test / fixtures / has-number-setting', 'has-number-setting' has nothing inside.
  Within directory hierarchy 'config / test / fixtures / never-built-dependencies', The 'never-built-dependencies' data structure is blank.
  At level 4, in directory path 'config > test > fixtures > pkg-using-workspaces', 'pkg-using-workspaces' appears to be unused.
  At level 4, in directory path 'config → test → fixtures → pkg-with-valid-workspace-yaml', The 'pkg-with-valid-workspace-yaml' repository is barren.
  In nested path 'config > test > fixtures > settings-in-workspace-yaml', The 'settings-in-workspace-yaml' collection stands empty.
  In nested path 'config → test → global-bin-dir', 'global-bin-dir' contains 1 subfolders: etc.
  At level 4, in directory path 'config → test → global-bin-dir → etc', Inside 'etc', you'll find it is an empty container.
  In nested path 'config / test / global-bin-dir-windows', 'global-bin-dir-windows' encompasses 1 folders: etc.
  In nested path 'config > test > global-bin-dir-windows > etc', 'etc' lacks any subdirectories.
  Within directory hierarchy 'config / test / has-workspace-yaml', Inside 'has-workspace-yaml', you'll find it remains unused.
  At level 3, in directory path 'config / test / using-test-pattern', 'using-test-pattern' appears to be unused.
  At the main level, 'config-writer' comprises 1 folders: src.
  Within directory hierarchy 'config-writer → src', The 'src' compartment contains no subdirectories.
  Back to the top level.
  In the root directory, 'deps-installer' stores 2 subdirectories: src, test.
  At level 2, in directory path 'deps-installer / src', The 'src' collection lacks any subdirectories.
  At level 2, in directory path 'deps-installer → test', 'test' stands empty.
  At the main level, 'matcher' houses 2 subfolders: src, test.
  At level 2, in directory path 'matcher → src', Inside 'src', you'll find it has been left empty.
  In nested path 'matcher / test', 'test' contains no subdirectories.
  Back to the top level.
  At the top level, 'normalize-registries' incorporates 1 contained folders: src.
  In nested path 'normalize-registries / src', The 'src' repository contains no subdirectories.
  Back to the top level.
  At the main level, 'package-is-installable' contains 2 subfolders: src, test.
  At level 2, in directory path 'package-is-installable / src', The 'src' storage space has no content.
  Within directory hierarchy 'package-is-installable / test', 'test' has no content.
  Back to the top level.
  In the root directory, 'parse-overrides' bundles 2 nested folders: src, test.
  At level 2, in directory path 'parse-overrides / src', Inside 'src', you'll find it has no folders inside.
  Within directory hierarchy 'parse-overrides > test', The 'test' collection contains nothing at present.
  Back to the top level.
  At the top level, 'pick-registry-for-package' encapsulates 2 contained folders: src, test.
  At level 2, in directory path 'pick-registry-for-package → src', The 'src' data structure is barren.
  In nested path 'pick-registry-for-package / test', Inside 'test', you'll find it is devoid of content.
  In the root directory, 'plugin-commands-config' carries 2 subfolders: src, test.
  Within directory hierarchy 'plugin-commands-config → src', Inside 'src', you'll find it has been left empty.
  In nested path 'plugin-commands-config → test', The 'test' storage space is unpopulated.
  
  
  Format your response in this style:
  ```
  params-hooks-compat
   +--app
   |   `--app
   |       `--[slug]
   +--pages
   |   `--pages
   `--shared
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "config\n +--config\n |   +--src\n |   `--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\n +--config-writer\n |   `--src\n +--deps-installer\n |   +--src\n |   `--test\n +--matcher\n |   +--src\n |   `--test\n +--normalize-registries\n |   `--src\n +--package-is-installable\n |   +--src\n |   `--test\n +--parse-overrides\n |   +--src\n |   `--test\n +--pick-registry-for-package\n |   +--src\n |   `--test\n `--plugin-commands-config\n     +--src\n     `--test", "description": "config is a head directory that collects 9 subdirectories. Notable ones include config, config-writer, deps-installer among others.\n\nLet me break down the setup for you:\n\nIn the root directory, 'config' stores 2 nested folders: src, test.\nIn nested path 'config \u2192 src', 'src' remains unused.\nWithin directory hierarchy 'config / test', 'test' organizes tests across 5 separate subfolders.\nAt level 3, in directory path 'config > test > fixtures', 'fixtures' possesses 6 numerous child directories.\nIn nested path 'config > test > fixtures > has-env-in-key', Inside 'has-env-in-key', you'll find it has yet to be populated.\nIn nested path 'config / test / fixtures / has-number-setting', 'has-number-setting' has nothing inside.\nWithin directory hierarchy 'config / test / fixtures / never-built-dependencies', The 'never-built-dependencies' data structure is blank.\nAt level 4, in directory path 'config > test > fixtures > pkg-using-workspaces', 'pkg-using-workspaces' appears to be unused.\nAt level 4, in directory path 'config \u2192 test \u2192 fixtures \u2192 pkg-with-valid-workspace-yaml', The 'pkg-with-valid-workspace-yaml' repository is barren.\nIn nested path 'config > test > fixtures > settings-in-workspace-yaml', The 'settings-in-workspace-yaml' collection stands empty.\nIn nested path 'config \u2192 test \u2192 global-bin-dir', 'global-bin-dir' contains 1 subfolders: etc.\nAt level 4, in directory path 'config \u2192 test \u2192 global-bin-dir \u2192 etc', Inside 'etc', you'll find it is an empty container.\nIn nested path 'config / test / global-bin-dir-windows', 'global-bin-dir-windows' encompasses 1 folders: etc.\nIn nested path 'config > test > global-bin-dir-windows > etc', 'etc' lacks any subdirectories.\nWithin directory hierarchy 'config / test / has-workspace-yaml', Inside 'has-workspace-yaml', you'll find it remains unused.\nAt level 3, in directory path 'config / test / using-test-pattern', 'using-test-pattern' appears to be unused.\nAt the main level, 'config-writer' comprises 1 folders: src.\nWithin directory hierarchy 'config-writer \u2192 src', The 'src' compartment contains no subdirectories.\nBack to the top level.\nIn the root directory, 'deps-installer' stores 2 subdirectories: src, test.\nAt level 2, in directory path 'deps-installer / src', The 'src' collection lacks any subdirectories.\nAt level 2, in directory path 'deps-installer \u2192 test', 'test' stands empty.\nAt the main level, 'matcher' houses 2 subfolders: src, test.\nAt level 2, in directory path 'matcher \u2192 src', Inside 'src', you'll find it has been left empty.\nIn nested path 'matcher / test', 'test' contains no subdirectories.\nBack to the top level.\nAt the top level, 'normalize-registries' incorporates 1 contained folders: src.\nIn nested path 'normalize-registries / src', The 'src' repository contains no subdirectories.\nBack to the top level.\nAt the main level, 'package-is-installable' contains 2 subfolders: src, test.\nAt level 2, in directory path 'package-is-installable / src', The 'src' storage space has no content.\nWithin directory hierarchy 'package-is-installable / test', 'test' has no content.\nBack to the top level.\nIn the root directory, 'parse-overrides' bundles 2 nested folders: src, test.\nAt level 2, in directory path 'parse-overrides / src', Inside 'src', you'll find it has no folders inside.\nWithin directory hierarchy 'parse-overrides > test', The 'test' collection contains nothing at present.\nBack to the top level.\nAt the top level, 'pick-registry-for-package' encapsulates 2 contained folders: src, test.\nAt level 2, in directory path 'pick-registry-for-package \u2192 src', The 'src' data structure is barren.\nIn nested path 'pick-registry-for-package / test', Inside 'test', you'll find it is devoid of content.\nIn the root directory, 'plugin-commands-config' carries 2 subfolders: src, test.\nWithin directory hierarchy 'plugin-commands-config \u2192 src', Inside 'src', you'll find it has been left empty.\nIn nested path 'plugin-commands-config \u2192 test', The 'test' storage space is unpopulated.\n"}