Refactoring: Consolidate general filesystem information

[amotl]

Problem

docs/getting-started/file-format-routing.md possibly included a bunch of generative text, which impacted the reading flow negatively.

Solution

I've extracted the key ingredients and added them back to the docs/supported-sources/filesystem.md file instead.

[coderabbitai]

Walkthrough

The change consolidates file-format routing guidance in the filesystem documentation, adds decoder and integrity notes, updates Sphinx cross-references and Handbook navigation, and redirects an inline source comment to the new documentation location.

Changes

File-format routing documentation

Layer / File(s)	Summary
Filesystem routing and format notes docs/supported-sources/filesystem.md	Adds format-to-library routing, iterabledata usage guidance, decoding semantics, type normalization rules, integrity behavior, and supporting references.
Navigation and cross-reference updates docs/index.md, docs/supported-sources/*.md, src/dlt_filesystem/source/format/iterable_codec.py	Updates routing links to Sphinx references, refines XML reader-hint guidance, removes the old Handbook entry, and points the inline comment to the filesystem guide.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• panodata/omniload#196: Introduces related MessagePack/CBOR support and routing documentation.
• panodata/omniload#225: Updates related filesystem and supported-source documentation.

Suggested reviewers: hampsterx

Poem

I’m a rabbit with docs in my paws,
Routing now follows clearer laws.
Formats hop, decoders align,
Cross-references neatly entwine.
The filesystem guide stands tall—
One bright path to explain them all.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title matches the main change: consolidating filesystem documentation into the supported-sources docs.
Description check	✅ Passed	The description is directly related to moving file-format routing content into the filesystem docs.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor-docs-file-format-routing

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[read-the-docs-community]

Documentation build overview

📚 omniload | 🛠️ Build #33621639 | 📁 Comparing 4c39231 against latest (8d7317c)

  🔍 Preview build  

6 files changed · ± 5 modified · - 1 deleted

± Modified

• supported-sources/cbor.html
• supported-sources/filesystem.html
• supported-sources/msgpack.html
• supported-sources/xml.html
• supported-sources/yaml.html

- Deleted

• getting-started/file-format-routing.html

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 55.23%. Comparing base (8d7317c) to head (4c39231).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #230   +/-   ##
=======================================
  Coverage   55.23%   55.23%           
=======================================
  Files         210      210           
  Lines        9796     9796           
=======================================
  Hits         5411     5411           
  Misses       4385     4385           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.