Sync generated docs

[dcg-generated-docs]

Generated docs are out of sync with main.

This PR was created automatically after a push to main at d72a334.

[github-actions]

📚 Docs Preview: https://pr-3534.datamodel-code-generator.pages.dev

[codspeed-hq]

Merging this PR will improve performance by 13.29%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 11 improved benchmarks
⏩ 98 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	WallTime	test_perf_complex_refs	1.6 s	1.4 s	+14.5%
⚡	WallTime	test_perf_deep_nested	4.1 s	3.6 s	+14.11%
⚡	WallTime	test_perf_multiple_files_input	2.9 s	2.5 s	+14.04%
⚡	WallTime	test_perf_graphql_style_pydantic_v2	648 ms	569.3 ms	+13.82%
⚡	WallTime	test_perf_duplicate_names	851 ms	750.1 ms	+13.45%
⚡	WallTime	test_perf_kubernetes_style_pydantic_v2	2.1 s	1.9 s	+13.39%
⚡	WallTime	test_perf_all_options_enabled	4.3 s	3.8 s	+13.35%
⚡	WallTime	test_perf_aws_style_openapi_pydantic_v2	1.6 s	1.4 s	+12.91%
⚡	WallTime	test_perf_openapi_large	2.4 s	2.1 s	+12.67%
⚡	WallTime	test_perf_stripe_style_pydantic_v2	1.6 s	1.5 s	+12.28%
⚡	WallTime	test_perf_large_models_pydantic_v2	2.9 s	2.6 s	+11.72%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing docs/generated-docs-sync (a3fc339) with main (0f09aee)²}

Footnotes

1. 98 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (b126855) during the generation of this report, so 0f09aee was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0f09aee) to head (a3fc339).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #3534   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          158       158           
  Lines        34254     34256    +2     
  Branches      4001      4001           
=========================================
+ Hits         34254     34256    +2     

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[github-actions]

Breaking Change Analysis

Result: No breaking changes detected

Reasoning: The PR diff only touches two auto-generated documentation files: docs/llms-full.txt and docs/llms.txt. The changes are purely additive — they add new "Focused Topics" documentation index pages (Model Customization, Template Customization, Typing Customization, OpenAPI) that link to existing CLI reference sections. The deleted-lines file is empty (no removed lines). There are no changes to source code, CLI options, the Python API, generated code output, Jinja2 templates, default values/behavior, Python version support, or error handling. Therefore this PR contains no breaking changes.

---

This analysis was performed by Claude Code Action

[github-actions]

🎉 Released in 0.67.0

This PR is now available in the latest release. See the release notes for details.