internal: Move github rules to cursor rules

Author: ntucker

.github/instructions/manager.instructions.md renamed to .cursor/rules/manager.mdc

@@ -1,5 +1,8 @@
 ---
-applyTo: '**/*.ts'
+description: Guidelines for implementing @data-client/react Managers
+globs:
+  - '**/*.ts'
+alwaysApply: false
 ---
 # Guide: Using `@data-client/react` Managers for global side effects
 
@@ -131,4 +134,4 @@ ReactDOM.createRoot(document.body).render(
     <App />
   </DataProvider>,
 );
-```
+```

.github/instructions/react.instructions.md renamed to .cursor/rules/react.mdc

@@ -1,7 +1,9 @@
 ---
-applyTo: '**/*.tsx'
+description: Usage patterns for @data-client/react hooks and components
+globs:
+  - '**/*.tsx'
+alwaysApply: false
 ---
-
 ## Rendering
 
 ```ts
@@ -123,4 +125,4 @@ For more detailed usage, refer to the [Manager Guide](.github/instructions/manag
 - [useSuspense](https://dataclient.io/docs/api/useSuspense)
 - [Controller](https://dataclient.io/docs/api/Controller)
 
-**ALWAYS follow these patterns and refer to the official docs for edge cases. Prioritize code generation that is idiomatic, type-safe, and leverages automatic normalization/caching via schema definitions.**
+**ALWAYS follow these patterns and refer to the official docs for edge cases. Prioritize code generation that is idiomatic, type-safe, and leverages automatic normalization/caching via schema definitions.**

.github/instructions/rest.instructions.md renamed to .cursor/rules/rest.mdc

@@ -1,5 +1,9 @@
 ---
-applyTo: '**/*.ts*'
+description: Patterns for using @data-client/rest to model resources and endpoints
+globs:
+  - '**/*.ts'
+  - '**/*.tsx'
+alwaysApply: false
 ---
 # Guide: Using `@data-client/rest` for Resource Modeling
 
@@ -241,4 +245,4 @@ export const IssueResource = resource({
 - [Schema Guide](https://dataclient.io/rest/api/schema#schema-overview)
 - [Relational Data Guide](https://dataclient.io/rest/guides/relational-data)
 
-**ALWAYS follow these patterns and refer to the official docs for edge cases. Prioritize code generation that is idiomatic, type-safe, and leverages automatic normalization/caching via schema definitions.**
+**ALWAYS follow these patterns and refer to the official docs for edge cases. Prioritize code generation that is idiomatic, type-safe, and leverages automatic normalization/caching via schema definitions.**