grey-haven-pr-template

# Grey Haven Pull Request Template

Create comprehensive, informative pull request descriptions that help reviewers understand the changes, context, and testing approach.

## PR Structure (Standard Template)

Every pull request should follow this structure:

```markdown
## Summary
[Concise 2-4 sentence description of changes]

## Motivation
[Why these changes are needed - business value, user impact, problem solved]

## Implementation Details
[Technical approach, key decisions, trade-offs considered]

## Testing
[Test strategy: unit/integration/e2e/benchmark, manual testing steps]

## Checklist
- [ ] Code follows Grey Haven style guidelines (90 char TS, 130 char Python)
- [ ] Type hints added (Python) or types maintained (TypeScript)
- [ ] Tests added/updated (unit, integration, e2e, benchmark)
- [ ] Database migrations tested (up and down)
- [ ] Multi-tenant isolation verified (tenant_id/RLS)
- [ ] Pre-commit hooks passing
- [ ] Documentation updated
- [ ] No breaking changes (or documented with migration guide)
```

## Section Guidelines

### Summary
**Purpose**: Provide a brief, clear overview of what changed.

**Guidelines**:
- 2-4 sentences maximum
- Focus on **what** changed from user/system perspective
- Reference Linear issues: `GREY-123`
- Mention multi-tenant or RLS changes
- Use present tense

**Example**:
```markdown
## Summary

This PR adds magic link authentication using better-auth with email verification.
Users can now sign in via emailed links instead of passwords. Addresses Linear
issue GREY-234 and integrates with multi-tenant RLS policies.
```

### Motivation
**Purpose**: Explain **why** these changes are necessary.

**Guidelines**:
- Describe the problem being solved
- Explain business value or user impact
- Reference Linear issues: `GREY-123`
- Include context not obvious from code
- Mention technical debt or performance concerns

**Example**:
```markdown
## Motivation

Users reported frustration with password-based auth (GREY-234). Analytics s