@bonesofspring/ai-rules 0.2.14 → 0.2.16

package/presets/cursor/nuxt/rules/preset-no-cross-stack-leakage.mdc

@@ -9,18 +9,18 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-no-cross-stack-leakage.md -->
 
-
 # Preset no cross-stack leakage
 
-Запрет протекания stack-specific имён, путей и handoff stems между пресетами.
+Ban leakage of stack-specific names, paths, and handoff stems across presets.
 
 ## Principles
 
-- `next` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `nuxt` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `svelte` must not require iOS-only agents/tooling (`xcuitest-*`, `xcodebuild` as required handoff, Keychain-only rules).
-- `ios-swift` must not ship Playwright handoffs or Next lint recipes as required commands.
-- `go` / `java` / `php-hexagonal` / `php-laravel` / `mcp-ts` must not ship Playwright, XCUITest, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
+- `next` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `nuxt` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `svelte` must not require iOS-only or Android-only agents/tooling (`xcuitest-*`, `instrumentation-test-*`, `xcodebuild` as required handoff, Keychain-only rules).
+- `ios-swift` must not ship Playwright handoffs, Android `instrumentation-test-*` handoffs, or Next lint recipes as required commands.
+- `android-kotlin` must not ship Playwright, XCUITest, `xcodebuild`, or Next lint recipes as required handoffs.
+- `go` / `java` / `php-hexagonal` / `php-laravel` / `mcp-ts` must not ship Playwright, XCUITest, Android instrumentation agents, Next lint recipes, or `xcodebuild`/`SwiftLint` as required handoffs.
 - `mcp-ts` must not ship Go tool commands (`go test`, `go vet`, `golangci-lint`) or `integration-test-*` agents as required delivery gates.
 - Shared core must not embed stack paths (`app/src/**`, `Features/**`, `playwright`, `xcodebuild`).
 
@@ -29,25 +29,37 @@ alwaysApply: false
 In ios-swift `chain-team-phases.sh` / agent handoffs (Cursor + Claude):
 
 - `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`
+- `instrumentation-test-` as required Android handoffs
 - `app/__tests__/e2e` as a required path
 - Positive yarn recipes `lint:js` / `lint:css` as commands to run (negation prose alone is weak — prefer zero occurrences)
 
 Required instead: `xcuitest-test-*` stems; build-verifier mentions `xcodebuild` or `post-change-build` / `xcode-tooling`.
 
+## Forbidden in android-kotlin hooks/agents (FAIL)
+
+In android-kotlin `chain-team-phases.sh` / agent handoffs (Cursor + Claude):
+
+- `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`
+- `app/__tests__/e2e` as a required path
+- `xcuitest-test-`, positive `xcodebuild` / `SwiftLint` as required handoffs
+- Positive yarn recipes `lint:js` / `lint:css` as commands to run
+
+Required instead: `instrumentation-test-*` stems; build-verifier mentions `gradle-tooling` and/or `post-change-build` (Gradle wrapper discovery — not `xcodebuild` as the default gate).
+
 ## Forbidden in next hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Next app work
 
 ## Forbidden in nuxt hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for Nuxt app work
 - Frontend profile mirrors `next`: Playwright / `lint:js` / `lint:css` allowed
 
 ## Forbidden in svelte hooks/agents (FAIL when present as required)
 
-- `xcuitest-test-` as handoff stems
+- `xcuitest-test-` / `instrumentation-test-` as handoff stems
 - Requiring `xcodebuild` / SwiftLint as the default post-change gate for SvelteKit app work
 - Frontend profile mirrors `next` / `nuxt`: Playwright / `lint:js` / `lint:css` allowed
 
@@ -57,7 +69,7 @@ Shared backend-stack bans (`go`, `java`, `php-hexagonal`, and `php-laravel`):
 
 - `playwright-test-`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`
 - Positive yarn recipes `lint:js` / `lint:css`
-- `xcuitest-test-`, `xcodebuild`, `SwiftLint` as required handoffs
+- `xcuitest-test-`, `instrumentation-test-`, `xcodebuild`, `SwiftLint` as required handoffs
 - Agent file `accessibility-reviewer` (no UI surface)
 
 Required instead: `integration-test-*`; build-verifier / `post-change-test` plus stack tooling — `go-tooling` (`go test`, `go vet`), `java-tooling` (`mvn test` / `./gradlew test`), or `php-tooling` (`php artisan test` / `composer test` / `vendor/bin/phpunit`).
@@ -68,9 +80,9 @@ Same UI/mobile bans as backend stacks, plus:
 
 - `playwright-test-`, `playwright-agents`, `playwright-e2e`, `user-playwright`, `app/__tests__/e2e`
 - Positive yarn recipes `lint:js` / `lint:css` as required gates
-- `xcuitest-test-`, `xcodebuild`, `SwiftLint` as required handoffs
+- `xcuitest-test-`, `instrumentation-test-`, `xcodebuild`, `SwiftLint` as required handoffs
 - Go tool commands as required MCP delivery gates: `go test`, `go vet`, `golangci-lint`
-- Agent files: `playwright-test-*`, `xcuitest-test-*`, `integration-test-*`, `accessibility-reviewer`
+- Agent files: `playwright-test-*`, `xcuitest-test-*`, `instrumentation-test-*`, `integration-test-*`, `accessibility-reviewer`
 
 Required instead: package-manager–discovered typecheck/test (`mcp-ts-tooling`, `post-change-test`); Phase 1 gates `build-verifier` + `security-reviewer`.
 
@@ -81,4 +93,4 @@ Required instead: package-manager–discovered typecheck/test (`mcp-ts-tooling`,
 
 ## Chain fork
 
-`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `nuxt`, `svelte`, `ios-swift`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).
+`hooks/chain-team-phases.sh` must differ **byte-wise** pairwise among `next`, `nuxt`, `svelte`, `ios-swift`, `android-kotlin`, `go`, `java`, `mcp-ts`, `php-hexagonal`, and `php-laravel` (per platform).

package/presets/cursor/nuxt/rules/preset-pr-checklist.mdc

@@ -9,19 +9,18 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-pr-checklist.md -->
 
-
 # Preset PR checklist
 
-Чеклист для PR, затрагивающих `packages/ai-rules/presets/**` (и dogfood `.cursor/` sync).
+Checklist for PRs that touch `packages/ai-rules/presets/**` (and dogfood `.cursor/` sync).
 
 ## Before merge
 
-- [ ] **SoT:** правки в `packages/…` (не только root `.cursor/`)
-- [ ] **Core:** если менялся `_shared/core/**` — обновлены все `<!-- shared-core: … -->` consumers (или documented intentional fork)
-- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel — см. `preset-twin-sync`)
-- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table актуален
+- [ ] **SoT:** edits in `packages/…` (not only root `.cursor/`)
+- [ ] **Core:** if `_shared/core/**` changed — all `<!-- shared-core: … -->` consumers updated (or documented intentional fork)
+- [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, android-kotlin, go, java, mcp-ts, php-hexagonal, and php-laravel — see `preset-twin-sync`)
+- [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table is current
 - [ ] **Token budget:** alwaysApply / session-start ≤ 3; meta rules not always-on
-- [ ] **Leakage:** нет чужих stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
+- [ ] **Leakage:** no foreign stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
 - [ ] **Twin depth:** domain ≥15 lines; thin aliases documented
 - [ ] **README:** stack `rules/README.md` core→stack mapping / catalog updated if stems added
 - [ ] **CHANGELOG / package README:** note when public preset paths or install surface change

package/presets/cursor/nuxt/rules/preset-token-budget.mdc

@@ -9,21 +9,20 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-token-budget.md -->
 
-
 # Preset token budget
 
-Инварианты загрузки правил в **установленном** пресете (consumer app).
+Invariants for rule loading in an **installed** preset (consumer app).
 
 ## Hard caps
 
 | Platform | Always-on | Cap |
 |----------|-----------|-----|
 | Cursor | `alwaysApply: true` | **≤ 3** |
-| Claude | rules **without** `paths:` | **ровно 3** |
+| Claude | rules **without** `paths:` | **exactly 3** |
 
 **Claude Option A (README exclusion):** when counting Claude rules without `paths:` / session-start, **exclude `**/README.md`** (topic indexes are not session-start rules). The intended session-start trio remains **exactly 3**; body budget sums **only those 3** rules.
 
-Session-start body budget (где задокументировано): ≤140 строк суммарно (stretch ≤120).
+Session-start body budget (where documented): ≤140 lines total (stretch ≤120).
 
 ## Meta / author rules
 

package/presets/cursor/nuxt/rules/preset-twin-sync.mdc

@@ -9,7 +9,6 @@ alwaysApply: false
 
 <!-- shared-core: meta/preset-twin-sync.md -->
 
-
 # Preset twin sync
 
 Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
@@ -27,6 +26,7 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 | `mcp-ts` | `presets/cursor/mcp-ts/rules/*.mdc` | `presets/claude/mcp-ts/rules/<topic>/` | Keep in `claude/mcp-ts/rules/README.md` |
 | `php-hexagonal` | `presets/cursor/php-hexagonal/rules/*.mdc` | `presets/claude/php-hexagonal/rules/<topic>/` | Keep in `claude/php-hexagonal/rules/README.md` |
 | `php-laravel` | `presets/cursor/php-laravel/rules/*.mdc` | `presets/claude/php-laravel/rules/<topic>/` | Keep in `claude/php-laravel/rules/README.md` |
+| `android-kotlin` | `presets/cursor/android-kotlin/rules/*.mdc` | `presets/claude/android-kotlin/rules/<topic>/` | Keep in `claude/android-kotlin/rules/README.md` |
 
 ## Same-PR checklist
 
@@ -51,5 +51,6 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 - **mcp-ts:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java; mapping table required).
 - **php-hexagonal:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts; mapping table required).
 - **php-laravel:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts / php-hexagonal; mapping table required).
+- **android-kotlin:** missing Claude twin for a changed Cursor rule → **FAIL** (same as next / ios-swift / go / java / mcp-ts / php-*; mapping table required).
 
 Dogfood: sync packages → root `.cursor/` after Cursor SoT changes (not the reverse). Use `packages/ai-rules/scripts/sync-dogfood-cursor.sh`.

package/presets/cursor/nuxt/rules/public-imports.mdc

@@ -1,5 +1,5 @@
 ---
-description: Импорт доменных типов и API только через публичные barrel @/types и @/api
+description: Import domain types and API only through public barrels @/types and @/api
 globs:
   - components/**/*
   - stores/**/*
@@ -10,16 +10,16 @@ alwaysApply: false
 impact: HIGH
 ---
 
-# Публичные импорты (`@/types`, `@/api`)
+# Public imports (`@/types`, `@/api`)
 
-**Коллизии:** импорт типов — раздел `@/types` ниже; API вне `api/**` — раздел `@/api` ниже (дублирует ESLint `no-restricted-imports` в `eslint.config.mjs`).
+**Collisions:** type imports — `@/types` section below; API outside `api/**` — `@/api` section below (mirrors ESLint `no-restricted-imports` in `eslint.config.mjs`).
 
 ## `@/types`
 
-- **Публичный API типов** — barrel `types/index.ts`; импортировать типы только как `@/types` (или `@/types/index`).
-- **Запрещено** обходить barrel: `@/types/<что‑угодно>`, кроме enum.
-- **Enum** — только `@/types/enums` / `@/types/enums.ts`.
-- Внутри `types/**` — относительные импорты между файлами слоя.
+- **Public types API** — barrel `types/index.ts`; import types only as `@/types` (or `@/types/index`).
+- **Forbidden** to bypass the barrel: `@/types/<anything>`, except enums.
+- **Enums** — only `@/types/enums` / `@/types/enums.ts`.
+- Inside `types/**` — relative imports between layer files.
 
 ```typescript
 // ✅
@@ -30,23 +30,23 @@ import { SomeEnum } from '@/types/enums'
 import type { TUserProfile } from '@/types/User.types'
 ```
 
-Новые публичные типы — реэкспорт в `types/index.ts` по **`layer-barrel-exports.mdc`**.
+New public types — re-export in `types/index.ts` per **`layer-barrel-exports.mdc`**.
 
 ## `@/api`
 
-- **Публичный API** — barrel `api/index.ts`. Вне `api/**` — только `import … from '@/api'` (или `@/api/index`).
-- **Запрещено** снаружи слоя: `@/api/<что‑угодно>`, кроме `@/api/index`.
-- Внутри `api/**` — относительные импорты и `@/api/services/**`, `@/api/clients/**`.
+- **Public API** — barrel `api/index.ts`. Outside `api/**` — only `import … from '@/api'` (or `@/api/index`).
+- **Forbidden** from outside the layer: `@/api/<anything>`, except `@/api/index`.
+- Inside `api/**` — relative imports and `@/api/services/**`, `@/api/clients/**`.
 
 ```typescript
-// ✅ в store, UI, lib вне api
+// ✅ in store, UI, lib outside api
 import { MedcardApiService } from '@/api'
 
-// ❌ снаружи api
+// ❌ outside api
 import { MedcardApiService } from '@/api/services/MedcardApiService/MedcardApiService'
 ```
 
-Новые публичные символы API — реэкспорт в `api/index.ts` по **`layer-barrel-exports.mdc`**.
+New public API symbols — re-export in `api/index.ts` per **`layer-barrel-exports.mdc`**.
 ## Incorrect
 
 ```ts

package/presets/cursor/nuxt/rules/reference-features.mdc

@@ -1,5 +1,5 @@
 ---
-description: Эталонные фичи репозитория — копировать структуру при реализации новых задач. Заполните пути после init в целевом репо.
+description: Repository reference features — copy structure when implementing new tasks. Fill paths after init in the target repo.
 globs:
   - components/**/*
   - stores/**/*
@@ -10,40 +10,40 @@ alwaysApply: false
 
 <!-- shared-core: architecture/reference-features.template.md -->
 
-# Эталонные фичи (reference features)
+# Reference features
 
 ## Stack notes
 
-Перед реализацией найди фичу того же типа и **повтори её структуру**, не изобретая новую организацию файлов.
+Before implementing, find a feature of the same type and **mirror its structure**; do not invent a new file organization.
 
 Taxonomy / shared core: [`presets/_shared/README.md`](../../../../_shared/README.md) · [Preset contribution guide](../../../../docs/PRESET-CONTRIBUTION.md).
 
-## Таблица эталонов
+## Reference table
 
-Замени **TBD** на реальные пути после договорённости в команде (или при `ai-rules init` в целевом репо):
+Replace **TBD** with real paths after team agreement (or on `ai-rules init` in the target repo):
 
-| Слой | Эталон | Что копировать |
-|------|--------|----------------|
+| Layer | Reference | What to copy |
+|-------|-----------|--------------|
 | UI page | **TBD** `components/pages/<Example>/` | `components/`, `*.data.ts`, `styles.ts`, barrel |
 | Store | **TBD** `stores/<example>.ts` | `defineStore`, actions, getters, types |
 | API service | **TBD** `api/services/<example>/` | service, mappers, barrel |
 | Types module | **TBD** `types/<example>/` | domain types, JSDoc, barrel export |
-| Unit tests | **TBD** рядом с эталонным mapper/service | `*.spec.ts`, describe/it naming |
+| Unit tests | **TBD** next to the reference mapper/service | `*.spec.ts`, describe/it naming |
 | E2E area | **TBD** `tests/e2e/<Area>/` | `*.cases.md`, page objects, `_shared/` |
 
-## Как использовать
+## How to use
 
-1. Определи затронутые слои из `decomposition.md` или задачи.
-2. Открой эталон из таблицы (после заполнения путей).
-3. Зеркаль именование, порядок файлов, паттерны импортов и тестов.
-4. Если эталона нет — выбери **самую близкую** существующую фичу того же слоя и зафиксируй выбор в handoff.
+1. Identify affected layers from `decomposition.md` or the task.
+2. Open the reference from the table (after paths are filled).
+3. Mirror naming, file order, import patterns, and tests.
+4. If there is no reference — pick the **closest** existing feature of the same layer and record the choice in the handoff.
 
 ## Living conventions
 
 Post-init gotchas / patterns / decisions: **`.cursor/team/conventions.md`** (and the twin tool path if both Cursor and Claude are installed). Consumer-owned; not always-on. See root `AGENTS.md` § Living conventions.
 
-## Связанные правила
+## Related rules
 
-- `code-quality-and-refactoring.mdc` — повторять паттерны, не deep-import.
-- `feature-delivery-workflow.mdc` — порядок слоёв.
-- skill `feature-delivery` — end-to-end сценарий.
+- `code-quality-and-refactoring.mdc` — repeat patterns, no deep-import.
+- `feature-delivery-workflow.mdc` — layer order.
+- skill `feature-delivery` — end-to-end scenario.

package/presets/cursor/nuxt/rules/store-pinia.mdc

@@ -1,31 +1,31 @@
 ---
-description: Pinia stores и клиентское состояние приложения (Nuxt)
+description: Pinia stores and client application state (Nuxt)
 globs: stores/**/*.ts,stores/**/*.js
 alwaysApply: false
 impact: HIGH
 ---
 
-# Общие принципы
+# General principles
 
-- Использовать **Pinia** (`defineStore`) — setup или options store, как у соседей в репо.
-- Модуль: `@pinia/nuxt` (или установленный эквивалент) — проверить `package.json` / `nuxt.config`.
-- В store хранить **доменные модели**, не сырые DTO из API.
-- Маппинг DTO → domain — в `api/**` (или server mappers) **до** записи в store.
-- Разделять серверное состояние (данные API) и локальное UI‑состояние (фильтры/флаги) — UI-only можно в composable/`ref` страницы, если так принято в репо.
+- Use **Pinia** (`defineStore`) — setup or options store, as neighbors do in the repo.
+- Module: `@pinia/nuxt` (or the installed equivalent) — check `package.json` / `nuxt.config`.
+- Store **domain models**, not raw API DTOs.
+- DTO → domain mapping — in `api/**` (or server mappers) **before** writing to the store.
+- Separate server state (API data) from local UI state (filters/flags) — UI-only may live in a composable/`ref` on the page if that is the repo convention.
 
-# Запрещено в этом пресете
+# Forbidden in this preset
 
 - RTK / Redux: `createSlice`, `createAsyncThunk`, RTK Query, `useDispatch` / `useSelector`, stem `store-rtk`.
-- Сырой `$fetch` / `fetch` из store в обход `~/api` / `@/api` сервисов (кроме узких documented исключений репо).
+- Raw `$fetch` / `fetch` from the store bypassing `~/api` / `@/api` services (except narrow documented repo exceptions).
 
-# Структура
+# Structure
 
-- Один доменный модуль — свой файл в `stores/**` (например `stores/profile.ts`).
-- Экспорт: `useXStore` через `defineStore('x', …)`.
-- State: явный тип; аккуратная инициализация.
-- Getters — производные от domain state; actions вызывают сервисы из `~/api` / `@/api` (`public-imports`).
+- One domain module — its own file under `stores/**` (e.g. `stores/profile.ts`).
+- Export: `useXStore` via `defineStore('x', …)`.
+- State: explicit type; careful initialization.
+- Getters — derived from domain state; actions call services from `~/api` / `@/api` (`public-imports`).
 
-# Асинхронность
+# Async
 
 ```ts
 // Incorrect — raw HTTP + DTO in state
@@ -50,19 +50,19 @@ export const useProfileStore = defineStore('profile', {
 })
 ```
 
-# Типизация и ошибки
+# Typing and errors
 
-- Доменные типы из `~/types` / `@/types`.
-- Ошибки транспорта — контракты из `@/types` / принятый класс ошибки клиента (`http-client`), не выдуманные axios shapes.
-- В UI: `storeToRefs` для state; actions вызывать напрямую с store.
+- Domain types from `~/types` / `@/types`.
+- Transport errors — contracts from `@/types` / the accepted client error class (`http-client`), not invented axios shapes.
+- In UI: `storeToRefs` for state; call actions directly on the store.
 
-# Тестирование
+# Testing
 
-- Покрывать важные stores (инициализация, переходы, actions с моком API).
-- Unit: Vitest; мокать `~/api` сервисы.
+- Cover important stores (init, transitions, actions with mocked API).
+- Unit: Vitest; mock `~/api` services.
 
-# Требование к агенту
+# Agent requirement
 
-- Не класть HTTP/transport в компоненты.
-- Строго типизировать state/actions.
-- Следовать стилю соседних stores.
+- Do not put HTTP/transport in components.
+- Strictly type state/actions.
+- Follow neighboring store style.

package/presets/cursor/nuxt/rules/technical-retro.mdc

@@ -1,16 +1,16 @@
 ---
-description: Роль агента для проведения технического ретроспективы (retro) команды / спринта. On-demand — предпочтительнее slash-команда /technical-retro.
+description: Agent role for running a technical retrospective (retro) for a team / sprint. On-demand — prefer the /technical-retro slash command.
 alwaysApply: false
 ---
 
 <!-- shared-core: review/technical-retro.md -->
 
-# Техническое ретро — rule alias
+# Technical retro — rule alias
 
-Полный сценарий (включая блок **«Работа агентов»** для slug из team tasks) — в slash-команде:
+Full scenario (including the **“Agent work”** block for a slug from team tasks) lives in the slash command:
 
 **`commands/technical-retro.md`** → `/technical-retro`
 
 When a task has `metrics.json`, use the local aggregation script and state the cohort, sample size, incomplete artifacts, attribution confidence, active attempt duration, and human-gate wait separately. Do not score malformed artifacts or gate wait as agent work.
 
-Используй rule только если command недоступен. Не дублируй содержимое command в ответе — следуй command-файлу и skill `technical-retro`.
+Use this rule only if the command is unavailable. Do not duplicate the command contents in the response — follow the command file and skill `technical-retro`.

package/presets/cursor/nuxt/rules/tests-e2e-structure.mdc

@@ -1,51 +1,50 @@
 ---
-description: Структура e2e тестов и планов (Playwright)
+description: Structure of e2e tests and plans (Playwright)
 globs: tests/e2e/**/*
 alwaysApply: false
 ---
 
-# Структура e2e в проекте
-
-- Папка e2e: `tests/e2e/**`.
-- Планы сценариев:
-  - `*.cases.md` файлы — **канонический источник сценариев**.
-- Тесты:
-  - `*.spec.ts` файлы — реализация сценариев на Playwright.
-- Общие утилиты и абстракции:
-  - `tests/e2e/_shared/**` — константы, fluent‑интерфейсы, хелперы.
-
-# Принципы
-
-- Каждый сценарий из `*.cases.md` должен иметь соответствующий тест (или набор тестов).
-- **Нельзя** ослаблять проверки в тестах, если это противоречит бизнес‑ожиданиям из планов.
-- Предпочтительно использовать:
-  - page‑objects (например, `OrderHistoryPage.ts`);
-  - общие хелперы из `_shared`.
-
-# Именование e2e‑тестов
-
-- Язык:
-  - все названия `test` / `it`, `describe`‑блоков и шагов в `*.cases.md` должны быть сформулированы **на русском языке**, описывая поведение и ожидаемый результат.
-- Формат заголовков e2e‑тестов (`test(...)` / `it(...)`):
-  - перед текстовым описанием сценария указывается **префикс с номером** в формате: `ПРЕФИКС-XXX Описание сценария`.
-  - `ПРЕФИКС` — аббревиатура из **первых букв слов** тестируемой сущности, записанная **латиницей в верхнем регистре**.
-    - пример: `OrderHistory` → `OH`, `BillingReport` → `BR`.
-  - `XXX` — порядковый номер теста **с тремя разрядами и лидирующими нулями**: `001`, `002`, `010`, `123` и т.д.
-  - пример полного названия e2e‑теста:
-    - `test('OH-001 Отображается список заказов', async ({ page }) => { ... })`
-  - внутри одной сущности (`ПРЕФИКС`) номера тестов должны образовывать **непротиворечивую последовательность**, без дубликатов номеров.
-
-# data-testid для e2e
-
-- **Приоритет селекторов:** `data-testid` для стабильных элементов; `getByRole` и `getByLabel` для форм и доступных элементов.
-- **Именование:** схема `{parent}__{element}` (например, `history-page__title`, `history-page__recognition-banner__attach-files-button`).
-- **Где добавлять:** на корневые контейнеры страниц и ключевые интерактивные элементы (кнопки, ссылки, поля), к которым обращаются page objects.
-- **При изменении UI:** обновлять data-testid в компонентах и соответствующие селекторы в page objects; сверять с `*.cases.md`.
-
-# Требование к агенту
-
-При добавлении/изменении e2e‑тестов:
-- Сначала смотреть соответствующий `*.cases.md` и синхронизировать названия сценариев.
-- Размещать спеки рядом с планами в той же директории.
-- Переиспользовать общие page‑objects и хелперы, а не копировать селекторы напрямую в каждый тест.
-
+# E2E structure in the project
+
+- E2E folder: `tests/e2e/**`.
+- Scenario plans:
+  - `*.cases.md` files — **canonical source of scenarios**.
+- Tests:
+  - `*.spec.ts` files — Playwright scenario implementation.
+- Shared utilities and abstractions:
+  - `tests/e2e/_shared/**` — constants, fluent interfaces, helpers.
+
+# Principles
+
+- Every scenario from `*.cases.md` must have a matching test (or set of tests).
+- **Do not** weaken assertions in tests if that contradicts business expectations from the plans.
+- Prefer:
+  - page objects (e.g. `OrderHistoryPage.ts`);
+  - shared helpers from `_shared`.
+
+# E2E test naming
+
+- Language:
+  - all `test` / `it` names, `describe` blocks, and steps in `*.cases.md` must be formulated **in Russian**, describing behavior and the expected result. <!-- i18n-keep: E5 -->
+- E2E title format (`test(...)` / `it(...)`):
+  - before the scenario description, put a **numbered prefix** in the form: `PREFIX-XXX Scenario description`.
+  - `PREFIX` — abbreviation from the **first letters of the words** of the entity under test, written in **Latin uppercase**.
+    - example: `OrderHistory` → `OH`, `BillingReport` → `BR`.
+  - `XXX` — sequential test number **with three digits and leading zeros**: `001`, `002`, `010`, `123`, etc.
+  - full e2e title example:
+    - `test('OH-001 Отображается список заказов', async ({ page }) => { ... })` <!-- i18n-keep: E5 -->
+  - within one entity (`PREFIX`), test numbers must form a **consistent sequence** without duplicate numbers.
+
+# data-testid for e2e
+
+- **Selector priority:** `data-testid` for stable elements; `getByRole` and `getByLabel` for forms and accessible elements.
+- **Naming:** scheme `{parent}__{element}` (e.g. `history-page__title`, `history-page__recognition-banner__attach-files-button`).
+- **Where to add:** on page root containers and key interactive elements (buttons, links, fields) that page objects target.
+- **When UI changes:** update data-testid in components and matching selectors in page objects; align with `*.cases.md`.
+
+# Agent requirement
+
+When adding/changing e2e tests:
+- First look at the matching `*.cases.md` and sync scenario names.
+- Place specs next to plans in the same directory.
+- Reuse shared page objects and helpers; do not copy selectors into every test.