chore: symlink CLAUDE.md to AGENTS.md

[NathanFlurry]

No description provided.

[claude]

Claude finished @NathanFlurry's task —— View job

---

Code Review Complete ✅

I've reviewed the symlink changes from CLAUDE.md to AGENTS.md. Here's my comprehensive feedback:

Todo List:

• Read and analyze the changed files
• Review the symlink implementation
• Check content preservation
• Assess potential issues with symlinks
• Provide comprehensive feedback

Review Summary

This PR creates a symlink from CLAUDE.md to AGENTS.md, effectively renaming the development guide while maintaining backward compatibility. The implementation is technically sound, but there are several considerations:

✅ Positive Aspects

1. Content Preservation: The original development guide content is fully preserved in AGENTS.md
2. Backward Compatibility: Existing references to CLAUDE.md continue to work via the symlink
3. Clean Implementation: The symlink is properly created and resolves correctly
4. Atomic Change: Single commit that cleanly handles the file reorganization

⚠️ Potential Concerns

Cross-Platform Compatibility

• Issue: Symlinks may not work consistently on Windows systems, especially without proper Git configuration
• Impact: Windows developers might see broken references or encounter issues with file access
• Recommendation: Consider documenting Windows-specific setup requirements or using alternative approaches like file copying in CI

Git Behavior

• Issue: Some Git operations and tools may handle symlinks differently than regular files
• Impact: Could cause confusion in certain development workflows or IDEs
• Recommendation: Test with common development tools used by your team

Naming Convention

• Question: The change from CLAUDE.md to AGENTS.md suggests a shift in how the project views this configuration file
• Consideration: Ensure this naming aligns with your long-term vision - if this is specifically for Claude Code instructions, CLAUDE.md might be more descriptive

🔍 Technical Analysis

Code Quality: ✅ Excellent

• Clean, atomic change with proper Git operations
• No code quality issues

Security: ✅ No concerns

• Symlinks pose no security risks in this context
• No sensitive information exposed

Performance: ✅ No impact

• Symlinks have negligible performance overhead
• File access remains efficient

Best Practices: ⚠️ Minor considerations

• Consider adding documentation about the symlink for future contributors
• Might want to verify CI/CD systems handle the symlink correctly

📝 Recommendations

1. Test Windows Compatibility: Verify the symlink works properly on Windows development environments
2. Update Documentation: If there are any references to CLAUDE.md in other documentation, consider updating them to reflect the new primary location
3. CI/CD Verification: Ensure your build and deployment processes handle the symlink correctly
4. Team Communication: Consider mentioning this change to your team to avoid confusion

Verdict

This is a well-executed organizational change that maintains functionality while improving the file structure. The symlink approach is appropriate for maintaining backward compatibility. No blocking issues identified, though testing across different development environments would be prudent.

---

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore: symlink CLAUDE.md to AGENTS.md #1210 👈 (View in Graphite)
• fix(core): prevent calling onStateChange recurively when changing state from within onStateChange #1209
• fix(core): fix notifying onStateChange for non-state mutations to persisted state #1208
• chore: add redirect packages for @rivetkit/actor & @rivetkit/core #1207
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

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.

[graphite-app]

Merge activity

• Sep 12, 5:08 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Sep 12, 5:09 PM UTC: CI is running for this pull request on a draft pull request (#1211) due to your merge queue CI optimization settings.
• Sep 12, 5:09 PM UTC: Merged by the Graphite merge queue via draft PR: #1211.