push

## Branch handling If on main, checkout a new branch first. If on a non-main branch where the existing PR is already merged, the uncommitted changes are likely unrelated to that branch. In this case: 1. Checkout main and pull 2. Create a new branch with a name describing the uncommitted changes 3. Continue with the commit and PR workflow below ## Commit and PR workflow Commit the changes. Use gh cli to check if a PR exists for this branch. If no PR exists, create one with an appropriate title and description. If a PR exists, query its current title and description and update them if the new changes warrant it. Push the changes. When writing or updating a PR title and description, always base them on the **full diff against `main`** (`git diff main...HEAD`), not just the most recent commits. The title and description should accurately summarize the entire set of changes in the PR. ### Release note labels When creating or updating a PR in this repo, make sure it has a changelog label so GitHub Releases can categorize it correctly. Prefer one of: - `enhancement` - `bug` - `documentation` If the correct label is unclear, prefer `enhancement`. If the PR should be excluded from release notes, use `skip-changelog`. Use `skip-changelog` for PRs focused only on developer tooling changes, such as agent skills, workflow plumbing, local tooling, or similar maintenance that should not appear in user-facing release notes. ### PR body formatting When the PR body contains Mark...