prompt: Your task is to convert the following English description into an ASCII tree format.
  
  app is a head directory that incorporates 4 subdirectories. Notable ones include mixed-fetch-strategies, ppr-disabled, ppr-disabled-with-loading-boundary among others.
  
  Let me break down the arrangement for you:
  
  At the top level, 'mixed-fetch-strategies' encompasses 1 subfolders: has-loading-boundary.
  At level 2, in directory path 'mixed-fetch-strategies / has-loading-boundary', 'has-loading-boundary' hosts 1 directories: a.
  Within directory hierarchy 'mixed-fetch-strategies > has-loading-boundary > a', 'a' stores 1 nested folders: b.
  Within directory hierarchy 'mixed-fetch-strategies / has-loading-boundary / a / b', 'b' maintains 1 child directories: shared-layout.
  Within directory hierarchy 'mixed-fetch-strategies > has-loading-boundary > a > b > shared-layout', 'shared-layout' has 2 child directories: ppr-disabled, ppr-enabled.
  In nested path 'mixed-fetch-strategies / has-loading-boundary / a / b / shared-layout / ppr-disabled', The 'ppr-disabled' section lacks any subdirectories.
  At level 6, in directory path 'mixed-fetch-strategies → has-loading-boundary → a → b → shared-layout → ppr-enabled', 'ppr-enabled' has been left empty.
  In the root directory, 'ppr-disabled' is barren.
  At the top level, 'ppr-disabled-with-loading-boundary' features 1 nested folders: child.
  At level 2, in directory path 'ppr-disabled-with-loading-boundary > child', 'child' sits empty.
  Back to the top level.
  At the main level, 'ppr-enabled' stores 1 subdirectory elements: [dynamic-param].
  Within directory hierarchy 'ppr-enabled / [dynamic-param]', '[dynamic-param]' is devoid of content.
  Back to the top level.
  
  
  Format your response in this style:
  ```
  custom_resolve_dir
   +--testproj
   |   `--__snapshots__
   `--testproj2
       `--__snapshots__
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "app\n +--mixed-fetch-strategies\n |   `--has-loading-boundary\n |       `--a\n |           `--b\n |               `--shared-layout\n |                   +--ppr-disabled\n |                   `--ppr-enabled\n +--ppr-disabled\n +--ppr-disabled-with-loading-boundary\n |   `--child\n `--ppr-enabled\n     `--[dynamic-param]", "description": "app is a head directory that incorporates 4 subdirectories. Notable ones include mixed-fetch-strategies, ppr-disabled, ppr-disabled-with-loading-boundary among others.\n\nLet me break down the arrangement for you:\n\nAt the top level, 'mixed-fetch-strategies' encompasses 1 subfolders: has-loading-boundary.\nAt level 2, in directory path 'mixed-fetch-strategies / has-loading-boundary', 'has-loading-boundary' hosts 1 directories: a.\nWithin directory hierarchy 'mixed-fetch-strategies > has-loading-boundary > a', 'a' stores 1 nested folders: b.\nWithin directory hierarchy 'mixed-fetch-strategies / has-loading-boundary / a / b', 'b' maintains 1 child directories: shared-layout.\nWithin directory hierarchy 'mixed-fetch-strategies > has-loading-boundary > a > b > shared-layout', 'shared-layout' has 2 child directories: ppr-disabled, ppr-enabled.\nIn nested path 'mixed-fetch-strategies / has-loading-boundary / a / b / shared-layout / ppr-disabled', The 'ppr-disabled' section lacks any subdirectories.\nAt level 6, in directory path 'mixed-fetch-strategies \u2192 has-loading-boundary \u2192 a \u2192 b \u2192 shared-layout \u2192 ppr-enabled', 'ppr-enabled' has been left empty.\nIn the root directory, 'ppr-disabled' is barren.\nAt the top level, 'ppr-disabled-with-loading-boundary' features 1 nested folders: child.\nAt level 2, in directory path 'ppr-disabled-with-loading-boundary > child', 'child' sits empty.\nBack to the top level.\nAt the main level, 'ppr-enabled' stores 1 subdirectory elements: [dynamic-param].\nWithin directory hierarchy 'ppr-enabled / [dynamic-param]', '[dynamic-param]' is devoid of content.\nBack to the top level.\n"}