task-workflowlisted

# Task Workflow Execute the standard development workflow for this task: `$ARGUMENTS` Follow these steps in order. Do NOT skip any step. ## Step 1: Create GitHub Issue ```bash gh issue create --title "<title>" --body "<description>" --label "<label>" ``` Common labels: `enhancement`, `bug`, `tests`, `documentation`, `refactor` Use the task description to write a clear issue title and body. The body should explain the context, what needs to change, and why. ## Step 2: Create Feature Branch Branch naming convention: - `feat/<slug>` for new features - `fix/<slug>` for bug fixes - `refactor/<slug>` for refactoring - `test/<slug>` for test-only changes - `docs/<slug>` for documentation ```bash git checkout -b <prefix>/<short-slug> ``` ## Step 3: Implement Changes Read existing code before modifying it. Follow patterns already established in the codebase. Key conventions: - Line length: 99 characters - Double quotes for strings - Complete type hints on all functions - Docstrings on classes and public methods - Tests use `unittest` with `unittest.mock` — never pytest - Add an entry to `CHANGELOG.md` under `## [Unreleased]` in the appropriate section (Added/Enhanced/Fixed/Documentation). Format: `- Description.` ## Step 4: Verify Run all verification commands. ALL must pass before committing. Important: The `.venv` uses a JIT-enabled CPython build with AddressSanitizer. All commands require the `ASAN_OPTIONS=detect_leaks=0 PYTHON_JIT=0` prefix. ```bash ASAN_OPTIONS=det