fix: SSR vote counts for session detail ticks and add comment count button

[marcodejongh]

Tick-level VoteButtons were hardcoded with initialUpvotes={0} and
initialUserVote={0}, which prevented them from ever loading real vote
counts. This adds upvotes to the SessionDetailTick type and batch-fetches
tick vote counts in the backend resolver so they render correctly on
initial page load. Also replaces standalone CommentSection with
FeedCommentButton (with new defaultExpanded prop) to show the SSR'd
comment count.

https://claude.ai/code/session_015CCDzunZzCLDf2vkf4yvVW

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
boardsesh	Building	Preview, Comment	Mar 1, 2026 9:24am

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[claude]

Claude Review

✅ Ready to merge - Minor test coverage gap noted below, but nothing blocking.

Issues

1. Test doesn't verify tick upvotes are passed correctly - packages/web/app/session/__tests__/session-detail-content.test.tsx:58-61

   The VoteButton mock only captures entityType and entityId, not initialUpvotes. The test at line 272 verifies the tick VoteButton exists but doesn't verify the upvotes value (which was the bug being fixed). Consider adding data-initial-upvotes={initialUpvotes} to the mock and asserting it equals 3 (the value in makeSession).

[claude]

Claude Review

✅ Ready to merge - No significant issues found.

The implementation correctly adds SSR vote counts by:

• Batch-fetching tick votes in the backend resolver with proper null coalescing
• Extending the SessionDetailTick type consistently across GraphQL schema and TypeScript types
• Removing the now-unnecessary initialUserVote={0} prop (VoteButton handles undefined correctly via line 53's ?? 0)
• Adding tests that verify SSR upvotes are passed through

Tests are appropriately updated to cover the new functionality.