feat(examples): add tic-tac-toe example and update hello-world

[NicholasKissel]

No description provided.

[railway-app]

🚅 Deployed to the rivet-pr-4012 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
mcp-hub	✅ Success (View Logs)	Web	Jan 22, 2026 at 11:45 pm
website	❌ Build Failed (View Logs)	Web	Jan 22, 2026 at 11:45 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Jan 22, 2026 at 11:45 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Jan 22, 2026 at 11:45 pm

[NicholasKissel]

• feat(examples): add tic-tac-toe example and update hello-world #4012 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Pull Request Review

This PR adds a new tic-tac-toe example and improves the hello-world example with better UI/UX. Overall, the code quality is good with comprehensive test coverage.

---

✅ Strengths

Tic-Tac-Toe Example

• Excellent test coverage: 183 lines of comprehensive tests covering all game scenarios
• Clean actor implementation with clear separation of concerns
• Good error handling with user-friendly error messages
• Type safety with TypeScript types

Hello-World Improvements

• Enhanced UX with animations and status indicators
• Consistent Rivet branding
• Better event structure with proper typing

---

🐛 Issues Found

1. README Documentation Issues

Tic-Tac-Toe README - Does not follow template in .claude/resources/EXAMPLE_TEMPLATE.md:

• Uses relative links in Resources section instead of absolute URLs
• Source code links should be standalone sentences, not bullet points

Hello-World README - Still uses relative links in Resources section

2. Code Quality Issues

examples/tic-tac-toe/src/actors.ts:38 - Array(9).fill(null) pattern could be clearer with explicit array literals in example code

examples/tic-tac-toe/frontend/App.tsx:39-44 - Unsafe type assertion without runtime validation

examples/tic-tac-toe/frontend/App.tsx:43,46 - Empty catch blocks swallow errors, add console.error logging

3. Missing Player Leave Handling

The game has no mechanism to handle player disconnection. Games become unplayable if a player leaves. Consider adding a leave action or documenting this limitation.

4. Test Coverage Gaps

Consider adding:

• Test for non-player attempting to make a move
• Edge case for join called with empty/null player ID

---

🔒 Security

Player ID uses Math.random() - acceptable for example but document that production should use UUID.

---

🎯 Recommendations

High Priority:

1. Fix README links to use absolute URLs per template
2. Add error logging in catch blocks
3. Add runtime type validation for API responses

Medium Priority:

4. Document player disconnect limitation or add leave handling
5. Validate player IDs in join action

Low Priority:

6. Use explicit array literals for clarity
7. Add missing test cases

---

✨ Overall Assessment

Code Quality: 4/5 | Test Coverage: 5/5 | Documentation: 3/5 | Security: 4/5

Solid PR with excellent test coverage. Main issues are documentation formatting and defensive programming improvements.

Recommendation: Approve with minor revisions (README formatting, error logging)