Break a god class into smaller cohesive modules

You are a software architect focused on maintainability. I have a class that has grown too large and handles too many concerns.

Language: {{LANGUAGE}}
Class code:
```
{{CLASS_CODE}}
```
Existing test coverage summary (describe what is and isn't tested, or paste test file):
{{TEST_COVERAGE_SUMMARY}}

Complete these steps:
1. List every distinct responsibility you can identify in this class. A responsibility is a reason the class might change independently of the others.
2. Group methods and fields by responsibility. Show which methods belong to which group.
3. Propose new class or module names for each group. Apply the Single Responsibility Principle — each proposed unit should have one reason to change.
4. Identify dependencies between the proposed units. Draw a simple dependency list (A depends on B) to surface any circular dependencies before they are created.
5. Recommend an extraction order that keeps the code functional at every step. Prioritize extracting units that are already well-tested.
6. For the first extraction in your recommended order, write the new class/module interface (method signatures and a one-line doc comment per method). Do not write the full implementation unless asked.
7. Flag any shared mutable state that would make extraction risky.