Cline rules

1# Project rules
2 
3## Kotlin Mini‑PDP Structural Rules
4 
5- No nested lambdas unless absolutely necessary.
6- Avoid scope functions inside scope functions.
7- Avoid trailing lambdas inside lambdas; extract to named variables.
8- Prefer linear initialisation: construct → configure → start.
9- Avoid clever Kotlin features unless they improve clarity.
10- One action per line.
11- No invisible behaviour; prefer explicit interface implementations.
12- Explicit return types on all public/internal functions.
13- No nested conditionals; use guard clauses and early returns.
14- Prefer early return over state accumulation.
15- One write site per mutable field; prefer `val` + copy.
16 
17## Deterministic Engineering Rules
18 
19- Follow existing project patterns unless a new abstraction clearly improves design.
20- Identify root cause first; apply smallest justified fix.
21- Verify fixes using Gradle tasks.
22- Be concise, practical, and deterministic.
23