Update file structure displays to use Files component

[devin-ai-integration]

Update file structure displays to use Files component

Summary

Converted all file structure displays throughout the documentation from bash code blocks with tree characters (├─, └─) to the new interactive Files component introduced in PR #1870.

Changes:

• Updated 37 documentation files across all product sections (Docs, SDKs, API Definitions, CLI Reference)
• Replaced bash code blocks containing file trees with <Files>, <Folder>, and <File> components
• Moved inline comments from code blocks to adjacent descriptive text (e.g., bullet points or notes)
• Used defaultOpen property on root folders and immediate children for better visibility
• Preserved all file/folder information and hierarchy

Files affected:

• 3 project structure pages (Docs, SDKs, API Definitions)
• 9 SDK quickstart guides (TypeScript, Python, Java, Go, Ruby, C#, Swift, PHP, Postman)
• 3 SDK snippet files (OpenAPI, Fern Definition, AsyncAPI)
• 8 API definition overview pages (AsyncAPI, OpenAPI, OpenRPC, gRPC, Fern Definition)
• 6 Fern Definition feature pages (auth, packages, dependencies, etc.)
• 5 docs configuration pages (versions, products, changelogs, quickstart, reusable markdown)
• 3 custom component pages (CSS/JS, markdown, API/webhook references)

Review & Testing Checklist for Human

• Visual rendering verification: Check that Files components render correctly on the preview deployment - especially verify that folders expand/collapse properly and the hierarchy is clear
• Content accuracy: Spot-check a few converted files to ensure no information was lost during conversion, particularly where inline comments were moved to adjacent text
• Consistency check: Verify that the conversion pattern is consistent across different file types (some files have "Key files:" sections, others have "Note:" sections - confirm this makes sense contextually)
• Edge cases: Check the 4 files that still contain └─ characters (pr-preview.mdx, preview-changes-locally.mdx, publishing-your-docs.mdx, commands.mdx) - these should only be CLI output formatting, not file trees that need conversion
• Empty folders: Verify that empty folders (represented as <Folder name="xyz" />) render correctly in the UI

Recommended test plan:

1. Deploy to preview environment and navigate through different documentation sections
2. Verify Files components are interactive (folders can expand/collapse)
3. Check that the visual hierarchy matches the original bash tree structures
4. Confirm that explanatory text (bullet points, notes) added alongside Files components is helpful and not redundant

Notes

• fern check passed with 0 errors (only warnings which are unrelated to these changes)
• All remaining grep matches for tree characters (├─, └─) are in CLI output examples, not file structures
• Session: https://app.devin.ai/sessions/63466d8cdc50455f820ebb8cacf9fd3b
• Requested by: Devin Logan (@devalog)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

⚠️ [vale] _{reported by reviewdog 🐶}
[FernStyles.Current] Avoid time-relative terms like 'latest' that become outdated

[github-actions]

🌿 Preview your docs: https://fern-preview-809e952a-d3b8-4582-9d68-68825e041cfd.docs.buildwithfern.com/learn