Shipping the Work

Please write a conventional commit message for these changes.
Format: <type>(<scope>): <subject>

Types: feat, fix, refactor, docs, test, chore
Keep subject under 72 characters.
Include a body that explains the "why" behind the changes.

fix: updates

feat(auth): add JWT refresh token rotation

Implements automatic token rotation to improve security.
Refresh tokens now expire after 7 days and are rotated
on each use. Adds middleware to handle token validation
and renewal transparently.

Closes #123

"Based on our conversation, generate a commit message
that summarizes what we implemented and why."

"Run 'git diff main' and summarize all changes on this
branch into a comprehensive commit message."

"Run 'git diff main...HEAD' to see all changes on this branch.
Then write a commit message that covers everything, not just
what we discussed in this session."

"Please write a pull request description with:

## Summary
Brief overview of what this PR does

## Changes
Detailed list of changes made

## Testing
How this was tested

## Screenshots (if applicable)
Any visual changes

## Checklist
- [ ] Tests pass
- [ ] Documentation updated
- [ ] No breaking changes (or documented)

"Based on our complete conversation and the git diff,
please write a comprehensive PR description following
the template above. Focus on the 'why' and 'what',
not just the 'how'."

"Use the gh CLI to:
1. Create a new PR from this branch
2. Use the PR description we just wrote
3. Add labels: 'enhancement', 'needs-review'
4. Request review from @teammate
5. Link to issue #123"

gh pr create \
  --title "feat(auth): add JWT refresh token rotation" \
  --body "$(cat pr-description.md)" \
  --label enhancement,needs-review \
  --reviewer teammate \
  --web

# AI helps generate
git commit -m "feat(auth): add JWT refresh token rotation

Implements automatic token rotation for improved security.
[full description]"

# AI helps create PR
gh pr create --web

# Human reviews and merges
# (Keep final merge control)