Add legal docs, redesign profiles and chats tab, fix fullscreen images, add code style

Signed-off-by: denis0001-dev <denis0001.dev@ya.ru>

.cursor/rules/code-style.mdc

@@ -0,0 +1,16 @@
+---
+description: Read CODE_STYLE.md before writing or refactoring Kotlin/Compose code
+alwaysApply: true
+---
+
+# Code style
+
+Before writing or editing Kotlin / Compose code in this repo:
+
+1. **Read** [`CODE_STYLE.md`](../../CODE_STYLE.md) at the repository root.
+2. **Follow** it — write idiomatic, well-structured code from the start; match neighboring files when a rule is ambiguous.
+3. **Do not ask the user style questions** when implementing new code.
+
+For style cleanup on an existing diff or file set, use the **`adapt-to-style`** skill.
+
+Build and platform rules remain in `android.mdc`.

.cursor/rules/kotlin-clean-code.mdc

@@ -1,13 +0,0 @@
----
-description: Keep Kotlin code clean — inline single-use helpers, match project conventions
-globs: app/shared/**/*.kt,utils/shared/**/*.kt
-alwaysApply: false
----
-
-# Kotlin clean code
-
-- If a function, variable, or small wrapper is used **once**, inline it at the call site unless it clarifies a non-obvious boundary (network call, animation controller, crypto).
-- Prefer existing project components (`ActionButton`, `Category`, `ExpressiveStepFlow`, `apiRequest`) over new abstractions.
-- Match surrounding naming, imports, and composable structure; read adjacent files before adding helpers.
-- Extract only when shared by **2+** call sites or when the block exceeds ~40 lines of non-trivial logic (pager math, crypto, API wiring).
-- No hardcoded user-visible strings in shared UI — use Compose Multiplatform resources (`composeResources/values/strings.xml` + `values-ru`).