Cursor rule

1---
2globs: apps/**/*, packages/**/*, drizzle/**/*, sql/**/*, config/**/*, Dockerfile, docker-compose.yml
3---
4 
5## Contribution & Refactor Guidelines
6 
7- **Prime rule**: Code is a liability, functionality is the asset. Any change must pay for its own complexity.
8 
9### 1. Before Large Changes (Refactors, New Infra, New Domains)
10 
11- Ask yourself, and write down in the PR description if possible:
12  - **Where is the bottleneck?** Latency, throughput, DX, or maintainability? Be concrete.
13  - **What is the simplest change that fixes it?** Prefer removal/cleanup over new systems.
14  - **What is the data flow?** Sketch: entrypoint → adapters → core → DB/Telegram → back.
15  - **What happens on failure?**
16    - If step B fails, does step A need a rollback or can we tolerate partial state?
17    - Is this best modeled as a saga / compensating action, or is “at-least-once” good enough?
18 
19### 2. Backend Mindset
20 
21- Avoid hidden in-memory state that couples requests:
22  - Session-local state lives in `CoreContext` or explicit stores, never in random globals.
23  - Cross-request state must go into the database or a well-defined cache layer.
24- For multi-step workflows:
25  - Make each step observable (events + logs) and ideally resumable.
26  - Design states explicitly (`pending`, `running`, `failed`, `completed`) rather than boolean flags.
27 
28### 3. TypeScript Style
29 
30- Strict TS is non-negotiable:
31  - Avoid `any` unless wrapping truly dynamic data, and confine it at the edge.
32  - Prefer small, composable types over giant “god” interfaces.
33- Functional style:
34  - Prefer pure functions and small modules over classes unless there is a clear lifecycle to model.
35  - Keep side effects at the boundary (adapters, services) and core logic pure where possible.
36 
37### 4. PR Hygiene
38 
39- Keep PRs focused:
40  - One domain behavior or refactor per PR.
41  - Mechanical renames and large formatting should be isolated from behavioral changes.
42- Tests:
43  - Add or update tests alongside behavior changes, especially for core and DB logic.
44  - Do not rely solely on manual E2E verification for critical paths.
45 
46