Copilot instructions

1---
2applyTo: "**/GraphQL/**/*.cs"
3---
4 
5# GraphQL Layer Rules
6 
7These rules apply exclusively to the `GraphQL` project layer.
8 
9## Layer Separation
10- **Zero business logic** — resolvers delegate to `Core` services
11- HotChocolate packages (`HotChocolate.*`) belong in this layer only — never reference them from `Core`, `DataAccess`, or `Worker`
12- Input/Output types are defined here, separate from domain entities in `Abstractions`
13 
14## Implementation-First Approach
15- Use annotation-based (implementation-first) type definitions — not schema-first SDL
16- Leverage HotChocolate's built-in mutation conventions (`[UseMutationConvention]` + `[Error<T>]`) for consistent error handling
17 
18## Attribute Stacking Order
19When combining data attributes on a resolver, stack in this exact order (top to bottom):
20 
21```csharp
22[UsePaging]        // 1. Pagination (outermost)
23[UseProjection]    // 2. Projection
24[UseSorting]       // 3. Sorting
25[UseFiltering]     // 4. Filtering (innermost)
26```
27 
28Wrong order causes silent misbehavior.
29 
30## DataLoader Convention
31- Name: `{Entity}By{Key}DataLoader`
32- Every resolver that fetches child entities must use a DataLoader — no `GetByIdAsync` in a loop
33- DataLoaders live in this layer, not in `Core`
34 
35## Type Registration
36- Ensure `AddTypes()` includes all required types
37- Use `[Module]` attribute for automatic type discovery where applicable
38 
39## Resolver Parameters
40- Use `[Service]` attribute on injected service parameters
41- Use `[Parent]` attribute in type extension resolvers
42- Always propagate `CancellationToken`
43