open-prlisted

# Open a Pull Request ## Step 1: Pre-flight checks Before opening the PR: 1. Ensure all changes are committed 2. Ensure the branch is pushed to the remote (`git push -u origin <branch>`) 3. Run linters/formatters across the whole repo (not just changed files) and commit any fixes ## Step 2: Test coverage **This is critical.** Before opening the PR, verify: ### Existing behavior is not broken - Identify which modules/components your changes touch - Run the existing test suites for those areas - If tests fail, fix them before opening the PR — do not open a PR with known regressions ### New behavior has test coverage - Every new feature, endpoint, or behavior change needs tests - If you added a new block, add tests for that block - If you changed API behavior, add or update API tests - If you changed frontend behavior, verify it doesn't break existing flows If you cannot run the full test suite locally, note which tests you ran and which you couldn't in the test plan. ## Step 3: Create the PR using the repo template Read the canonical PR template at `.github/PULL_REQUEST_TEMPLATE.md` and use it **verbatim** as your PR body: 1. Read the template: `cat .github/PULL_REQUEST_TEMPLATE.md` 2. Preserve the exact section titles and formatting, including: - `### Why / What / How` - `### Changes 🏗️` - `### Checklist 📋` 3. Replace HTML comment prompts (`<!-- ... -->`) with actual content; do not leave them in 4. **Do not pre-check boxes** — leave all checkboxes as `-