Extract shared pagination type and refactor response types

[enko]

Summary

This PR extracts pagination metadata into a shared type and refactors response types across the codebase for better type reusability and consistency. The changes improve type safety and reduce duplication in API response definitions.

Key Changes

• New shared pagination type: Created PaginationInfo interface in packages/shared/src/pagination.ts to standardize pagination metadata across paginated API responses
• Extracted response types in auth: Added dedicated response types (UserWithPreferencesResponse, PreferencesResponse, ForgotPasswordResponse, HealthCheckResponse) in packages/shared/src/auth.ts for better API documentation and type safety
• Refactored collective types: Extracted CollectiveTypeSummary and RelationshipTypeSummary interfaces to reduce inline type definitions and improve reusability
• Refactored friend types: Extracted FriendPreview interface for use in dashboard and summary views
• Refactored circle types: Extracted CircleReorderItemSchema to avoid inline schema duplication in circle reorder requests
• Updated backend routes: Applied new response types in auth.ts and health.ts routes
• Updated frontend stores: Replaced local PaginationState interfaces with shared PaginationInfo type in collectives and encounters stores
• Updated frontend API: Extracted UpcomingDatesOptions interface for better API function documentation

Implementation Details

• All pagination-related responses now use the centralized PaginationInfo type from the shared package
• Response types are now explicitly defined and exported, making API contracts clearer
• Type summaries (e.g., CollectiveTypeSummary, RelationshipTypeSummary) follow a consistent naming pattern
• Frontend stores now import pagination type from shared package instead of defining locally, reducing duplication

https://claude.ai/code/session_01Ggmu9YzZBUq3ETBuiyXcXV

[github-actions]

🔍 Automated Code Review

Commit	26bdaee
Reviewed	2026-03-09T00:00:00Z
Status	✅ Approved

Findings

Severity	Count
🚨 Critical	0
⚠️ Important	0
💡 Suggestion	1

AGENTS.md Compliance

• ✅ No any types — all new types use explicit interfaces
• ✅ All new exports wired through src/index.ts (pagination.ts added to barrel)
• ✅ Descriptive naming conventions followed (PaginationInfo, CollectiveTypeSummary, FriendPreview, etc.)
• ✅ Interfaces used for object shapes as required by shared package guidelines
• ✅ TypeScript strict mode compatible

Summary

Clean, well-scoped refactoring that eliminates duplicated inline type definitions. Extracting PaginationInfo into packages/shared/src/pagination.ts correctly centralises pagination metadata, and the frontend stores now properly import from the shared package instead of redefining locally. The extraction of CollectiveTypeSummary, RelationshipTypeSummary, FriendPreview, and CircleReorderItemSchema all follow the project's naming conventions and reduce duplication without changing runtime behaviour.

One minor suggestion: HealthCheckResponse was added to packages/shared/src/auth.ts (line ~111), but it describes the /api/health endpoint rather than anything auth-related. If the shared package grows, consider moving it to a dedicated health.ts file (or a general api.ts) to keep auth.ts focused on authentication concerns. Not a blocker.

---

_{🤖 Automated review by Claude Code • View CI Run}

[github-actions]

✅ Code review passed. No critical or important issues found. See summary comment for details.

[github-actions]

🎉 This PR is included in version 2.65.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀