docs: add doctest Examples for correlation, Munich, tails, adjustments, workflow, and utils

[EKtheSage]

Summary

• Add Examples sections with .. testsetup::, .. testcode::, and .. testoutput:: Sphinx doctest directives to 14 files across the codebase
• Each example demonstrates meaningful parameter effects using cl.load_sample() data and reproducible round() output
• Covers: BerquistSherman, BootstrapODPSample, ParallelogramOLF, TrendAdjustment, DevelopmentCorrelation, ValuationCorrelation, ConstantDevelopment, MunichChainladder, CaseOutstanding, BondyTail, ClarkTail, TailCurve, GridSearch, VotingChainladder, and utility functions

Files changed

Module	File
adjustments	berqsherm.py, bootstrap.py, parallelogram.py, trend.py
core	correlation.py
development	constant.py, munich.py, outstanding.py
tails	bondy.py, clark.py, curve.py
utils	utility_functions.py
workflow	gridsearch.py, voting.py

Test plan

• Verify Sphinx doctest build runs without errors on all modified files
• Confirm .. testoutput:: blocks match actual estimator output
• Check that import placement (import chainladder in testsetup, other imports in testcode) is consistent

---

Note

Medium Risk
Mostly documentation-only doctest additions, but it also introduces a GitHub Action that auto-merges and pushes main into docs/great-docs-prototype, which could cause unexpected branch updates or merge conflicts if misconfigured.

Overview
Adds extensive Sphinx doctest Examples blocks to a wide set of estimators/utilities (adjustments, correlation, development, tails, workflow, and utility_functions) to demonstrate parameter effects with reproducible outputs.

Introduces a new GitHub Actions workflow (sync-main-to-docs.yml) that, on every push to main, checks out docs/great-docs-prototype, merges origin/main into it, and pushes the result back to the remote branch.

^{Reviewed by Cursor Bugbot for commit ce197a6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ce197a6. Configure here.}

[cursor]

Unrelated CI workflow file included in docs PR

Low Severity

The new sync-main-to-docs.yml workflow file is not mentioned anywhere in the PR description's "Files changed" table, which exclusively lists Python source files. This workflow — which auto-merges main into docs/great-docs-prototype on every push — is unrelated to adding doctest examples and appears to have been accidentally included in this documentation-focused PR.

 

^{Reviewed by Cursor Bugbot for commit ce197a6. Configure here.}

[henrydingliu]

echoing @kennethshsu 's concerns from #786 , this is a whale of a PR.

[kennethshsu]

Hi @EKtheSage, this is a big PR too. I would encourage smaller PRs going forward. I think 2-3 methods max for the docstrings improvements.

Can you resolve the merge conflict with another commit and I will help review this?

[EKtheSage]

Closing as superseded by smaller scoped PRs for #704: #800, #801, #803, and #804 cover the adjustment family, tails, workflow, and utility work from this branch. The replacement PRs are rebased from current main, scoped by subsystem, and intentionally exclude .github/workflows/sync-main-to-docs.yml.