| 1 | <!-- Thanks for the PR! English or 中文 are both fine. Short is good. --> |
| 2 | |
| 3 | ## What and why |
| 4 | |
| 5 | <!-- What does this change, and why? A few sentences is enough. --> |
| 6 | |
| 7 | ## Issue |
| 8 | |
| 9 | <!-- CI needs one line here. Replace N with a number: |
| 10 | - Closes #N this PR finishes the issue (Fixes / Resolves also work) |
| 11 | - Refs #N related or partial work; the issue stays open |
| 12 | - No-Issue: <one-line reason> for typos, chores, dependency bumps |
| 13 | Only write a closing word when you mean it. GitHub closes the issue even in |
| 14 | "this does not close ..." and CI rejects that wording. |
| 15 | Put issue numbers here rather than in `feat:` commit messages: CI requires a |
| 16 | `feat:` commit that mentions #N to also add #N to CHANGELOG.md. --> |
| 17 | |
| 18 | ## How I tested it |
| 19 | |
| 20 | <!-- Commands you ran and what they showed. Test what you changed, for example |
| 21 | `scripts/dev-test.sh tui <filter>`; CI runs the full suite for you. |
| 22 | For visible UI changes, add a screenshot or recording. --> |
| 23 | |
| 24 | ## Checklist |
| 25 | |
| 26 | - [ ] One focused change, rebased on current `main` |
| 27 | - [ ] `cargo fmt --all` passes, and tests cover new or changed behavior |
| 28 | - [ ] If this adds or changes a user-facing feature, I updated its docs and its row in `docs/features.toml` (`cargo test -p codewhale-tui --test feature_registry` checks it) |
| 29 |