direct-cli 0.2.9.2__tar.gz → 0.2.11__tar.gz

{direct_cli-0.2.9.2 → direct_cli-0.2.11}/.github/copilot-instructions.md

@@ -77,7 +77,7 @@ Never invoke these commands in automated tests against a real account.
 | `bidmodifiers set` | Changes bid multipliers (device, region, time, etc.) |
 
 ### 🟡 Reversible but affect live traffic
-`campaigns suspend/resume/archive/unarchive`, `ads suspend/resume/archive/unarchive`, `keywords suspend/resume/archive/unarchive`, `audiencetargets suspend/resume`
+`campaigns suspend/resume/archive/unarchive`, `ads suspend/resume/archive/unarchive`, `keywords suspend/resume`, `audiencetargets suspend/resume`
 
 ### 🟡 Account-wide mutations
 `clients update` — modifies account-level settings.

{direct_cli-0.2.9.2 → direct_cli-0.2.11}/.gitignore

@@ -39,6 +39,7 @@ coverage.xml
 .venv
 
 # IDE
+.claude/
 .vscode/
 .idea/
 *.swp

{direct_cli-0.2.9.2 → direct_cli-0.2.11}/CLAUDE.md

@@ -52,8 +52,17 @@ Click group-of-groups. Each Yandex Direct API resource = one file in `direct_cli
 
 ## Dangerous Commands — Never Auto-Test
 
-- **Irreversible (delete):** `campaigns/adgroups/ads/keywords/audiencetargets delete`
-- **Financial:** `bids set`, `keywordbids set`, `bidmodifiers set`
-- **Live traffic:** `suspend/resume/archive/unarchive` on campaigns, ads, keywords
-- **Mutations:** all `add`/`update` subcommands (test with `--dry-run`)
-- **Safe (read-only):** all `get` subcommands, `changes check*`, `dictionaries list-names`, `keywordsresearch has-search-volume`, `reports list-types`
+Smoke command safety is tracked in `direct_cli/smoke_matrix.py`. Every CLI
+subcommand belongs to exactly one category:
+
+- **SAFE:** production read-only smoke tests in `scripts/test_safe_commands.sh`.
+- **WRITE_SANDBOX:** live mutating smoke tests through
+  `scripts/test_sandbox_write.sh`; these must call only `direct --sandbox ...`
+  and must not touch production data.
+- **DANGEROUS:** manual-only checklist in `scripts/test_dangerous_commands.sh`;
+  the script exits with status 1 by design and must not be used as an
+  automated runner.
+
+Never auto-test production mutations: agency client changes, live bid changes,
+moderation, lifecycle operations, `clients update`, or any `delete` without
+`--sandbox`.

{direct_cli-0.2.9.2 → direct_cli-0.2.11}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: direct-cli
-Version: 0.2.9.2
+Version: 0.2.11
 Summary: Command-line interface for Yandex Direct API
 Author: axisrow
 License: MIT
@@ -97,6 +97,23 @@ Notes:
 - Authorization is performed via `direct auth login`.
 - Alias `auth_login` is not supported.
 
+Credential resolution priority:
+
+| Priority | Source | Example |
+|----------|--------|---------|
+| 1 | Explicit CLI options | `direct --token TOKEN --login LOGIN campaigns get` |
+| 2 | OAuth profile storage | `direct --profile agency1 campaigns get` |
+| 3 | Profile-specific env vars | `YANDEX_DIRECT_TOKEN_AGENCY1`, `YANDEX_DIRECT_LOGIN_AGENCY1` |
+| 4 | Base env vars or project `.env` | `YANDEX_DIRECT_TOKEN`, `YANDEX_DIRECT_LOGIN` |
+| 5 | 1Password references | `--op-token-ref`, `YANDEX_DIRECT_OP_TOKEN_REF` |
+| 6 | Bitwarden references | `--bw-token-ref`, `YANDEX_DIRECT_BW_TOKEN_REF` |
+
+The project `.env` file is loaded automatically. If a profile is selected
+with `--profile` or `direct auth use --profile NAME`, Direct CLI does not
+fall back to base `YANDEX_DIRECT_LOGIN`; this prevents mixing a profile token
+with a login from the project `.env`. For multi-account setups, prefer OAuth
+profiles or profile-specific env vars instead of base credentials.
+
 Install with `pip install direct-cli`, then run commands with `direct`.
 Invoking the deprecated `direct-cli` entrypoint exits with
 `use direct instead of direct-cli`.
@@ -145,6 +162,17 @@ the runtime CLI by default. If compatibility is ever needed, an alias must be
 added as an explicit exception with the concrete legacy syntax that still has to
 be supported.
 
+#### Removed Legacy Names
+
+| Legacy name                | Canonical name               |
+|----------------------------|------------------------------|
+| `dynamictargets`           | `dynamicads`                 |
+| `smarttargets`             | `smartadtargets`             |
+| `negativekeywords`         | `negativekeywordsharedsets`  |
+| `list`                     | `get`                        |
+| `checkcamp`                | `check-campaigns`            |
+| `checkdict`                | `check-dictionaries`         |
+
 #### Input Rules
 
 - All user-facing input must be passed only through typed CLI flags.
@@ -177,7 +205,7 @@ direct dictionaries get-geo-regions \
 #### Flag Design Rules
 
 - List inputs use comma-separated CLI syntax where appropriate.
-- Money and bid values stay human-readable in CLI input and are converted internally to the API wire format.
+- Money and bid values are passed in micro-rubles (API-native format). Values below 100,000 trigger a validation hint suggesting the correct scale.
 - Selector fields remain explicit flags, for example:
   - `--id`
   - `--campaign-id`
@@ -221,7 +249,7 @@ direct campaigns get --ids 1,2,3
 direct changes check-campaigns --timestamp 2026-04-14T00:00:00
 direct keywordsresearch has-search-volume --keywords "buy laptop,buy desktop"
 direct smartadtargets update --id 456 --priority HIGH
-direct dynamicads set-bids --id 789 --bid 12.5 --context-bid 9 --priority HIGH
+direct dynamicads set-bids --id 789 --bid 12500000 --context-bid 9000000 --priority HIGH
 direct dictionaries get-geo-regions --name Moscow --region-ids 225,187 --exact-names Москва,Санкт-Петербург --fields GeoRegionId,GeoRegionName
 ```
 
@@ -229,7 +257,7 @@ Invalid examples:
 
 ```bash
 direct dictionaries get-geo-regions --json '{"GeoRegionIds":[225]}' --fields GeoRegionId,GeoRegionName
-direct dynamicads set-bids --id 789 --bid 12.5 --json '{"StrategyPriority":"HIGH"}'
+direct dynamicads set-bids --id 789 --bid 12500000 --json '{"StrategyPriority":"HIGH"}'
 direct dictionaries get-geo-regions \
   --region-ids 225 \
   --fields GeoRegionId,GeoRegionName
@@ -247,12 +275,12 @@ direct campaigns get --ids 1,2,3 --format table
 direct campaigns get --fetch-all --format csv --output campaigns.csv
 
 # Create (use --dry-run to preview the request)
-direct campaigns add --name "My Campaign" --start-date 2024-02-01 --type TEXT_CAMPAIGN --budget 1000 --setting ADD_METRICA_TAG=YES --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
+direct campaigns add --name "My Campaign" --start-date 2024-02-01 --type TEXT_CAMPAIGN --budget 1000000000 --setting ADD_METRICA_TAG=YES --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
 direct campaigns add --name "Dynamic Campaign" --start-date 2024-02-01 --type DYNAMIC_TEXT_CAMPAIGN --setting ADD_METRICA_TAG=NO --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
-direct campaigns add --name "Smart Campaign" --start-date 2024-02-01 --type SMART_CAMPAIGN --network-strategy AVERAGE_CPC_PER_FILTER --filter-average-cpc 1 --counter-id 123 --dry-run
+direct campaigns add --name "Smart Campaign" --start-date 2024-02-01 --type SMART_CAMPAIGN --network-strategy AVERAGE_CPC_PER_FILTER --filter-average-cpc 1000000 --counter-id 123 --dry-run
 
 # Update / lifecycle
-direct campaigns update --id 12345 --name "New Name" --status SUSPENDED --budget 100 --start-date 2024-02-10 --end-date 2024-03-01
+direct campaigns update --id 12345 --name "New Name" --status SUSPENDED --budget 100000000 --start-date 2024-02-10 --end-date 2024-03-01
 direct campaigns suspend --id 12345
 direct campaigns resume --id 12345
 direct campaigns archive --id 12345
@@ -286,7 +314,7 @@ direct ads delete --id 99999
 
 ```bash
 direct keywords get --campaign-ids 1,2,3
-direct keywords add --adgroup-id 12345 --keyword "buy laptop" --bid 10.50 --context-bid 5.25 --user-param-1 segment-a --user-param-2 segment-b --dry-run
+direct keywords add --adgroup-id 12345 --keyword "buy laptop" --bid 10500000 --context-bid 5250000 --user-param-1 segment-a --user-param-2 segment-b --dry-run
 direct keywords update --id 88888 --keyword "updated keyword text"
 direct keywords delete --id 88888
 ```
@@ -324,22 +352,22 @@ direct retargeting add --name "List A" --type AUDIENCE --rule "ALL:12345:30|6789
 direct retargeting update --id 55 --name "Renamed" --rule "ANY:12345:30" --dry-run
 
 # Bids and modifiers
-direct bids set --keyword-id 123 --bid 15
-direct bids set-auto --keyword-id 123 --max-bid 20 --position PREMIUMBLOCK --scope SEARCH --dry-run
-direct keywordbids set --keyword-id 321 --search-bid 8 --network-bid 3
-direct keywordbids set-auto --keyword-id 321 --target-traffic-volume 100 --increase-percent 10 --bid-ceiling 12.5 --dry-run
+direct bids set --keyword-id 123 --bid 15000000
+direct bids set-auto --keyword-id 123 --max-bid 20000000 --position PREMIUMBLOCK --scope SEARCH --dry-run
+direct keywordbids set --keyword-id 321 --search-bid 8000000 --network-bid 3000000
+direct keywordbids set-auto --keyword-id 321 --target-traffic-volume 100 --increase-percent 10 --bid-ceiling 12500000 --dry-run
 direct bidmodifiers add --campaign-id 123 --type DEMOGRAPHICS_ADJUSTMENT --value 150 --gender GENDER_MALE --age AGE_25_34 --dry-run
 direct bidmodifiers set --id 99 --value 130 --dry-run
 
 # Canonical multiword groups
 direct negativekeywordsharedsets update --id 123 --keywords "foo,bar"
-direct audiencetargets add --adgroup-id 100 --retargeting-list-id 200 --bid 12 --priority HIGH --dry-run
-direct audiencetargets set-bids --id 101 --context-bid 7 --priority LOW --dry-run
-direct dynamicads add --adgroup-id 33 --name "Webpage A" --condition "URL:CONTAINS_ANY:test|shop" --condition "PAGE_CONTENT:CONTAINS:baz" --bid 3 --context-bid 2 --priority HIGH --dry-run
-direct smartadtargets add --adgroup-id 55 --name "Audience A" --audience ALL_SEGMENTS --condition "CATEGORY_ID:EQUALS:42" --average-cpc 3 --average-cpa 4 --priority HIGH --available-items-only YES --dry-run
+direct audiencetargets add --adgroup-id 100 --retargeting-list-id 200 --bid 12000000 --priority HIGH --dry-run
+direct audiencetargets set-bids --id 101 --context-bid 7000000 --priority LOW --dry-run
+direct dynamicads add --adgroup-id 33 --name "Webpage A" --condition "URL:CONTAINS_ANY:test|shop" --condition "PAGE_CONTENT:CONTAINS:baz" --bid 3000000 --context-bid 2000000 --priority HIGH --dry-run
+direct smartadtargets add --adgroup-id 55 --name "Audience A" --audience ALL_SEGMENTS --condition "CATEGORY_ID:EQUALS:42" --average-cpc 3000000 --average-cpa 4000000 --priority HIGH --available-items-only YES --dry-run
 direct smartadtargets update --id 456 --priority HIGH
-direct smartadtargets set-bids --id 456 --average-cpc 10.5 --average-cpa 15 --priority HIGH
-direct dynamicads set-bids --id 789 --bid 12.5 --context-bid 9 --priority HIGH
+direct smartadtargets set-bids --id 456 --average-cpc 10500000 --average-cpa 15000000 --priority HIGH
+direct dynamicads set-bids --id 789 --bid 12500000 --context-bid 9000000 --priority HIGH
 
 # Shared bidding strategies
 direct strategies get --limit 5
@@ -349,8 +377,8 @@ direct strategies archive --id 42 --dry-run
 
 # Dynamic feed ad targets
 direct dynamicfeedadtargets get --adgroup-ids 123 --limit 5
-direct dynamicfeedadtargets add --adgroup-id 33 --name "Feed slice A" --condition "CATEGORY:EQUALS:shoes" --bid 5 --dry-run
-direct dynamicfeedadtargets set-bids --id 789 --bid 6.5 --context-bid 4 --dry-run
+direct dynamicfeedadtargets add --adgroup-id 33 --name "Feed slice A" --condition "CATEGORY:EQUALS:shoes" --bid 5000000 --dry-run
+direct dynamicfeedadtargets set-bids --id 789 --bid 6500000 --context-bid 4000000 --dry-run
 
 # Extensions, assets, feeds, and clients
 direct sitelinks add --sitelink "Docs|https://example.com/docs" --sitelink "Help|https://example.com/help|Desk" --dry-run
@@ -409,7 +437,7 @@ The following commands make **irreversible changes** — use with caution:
 | `keywords delete --id` | Permanently deletes a keyword |
 | `audiencetargets delete --id` | Permanently deletes an audience target |
 
-Commands that affect live ad delivery: `suspend`, `resume`, `archive`, `unarchive` (available on `campaigns`, `ads`, `keywords`).
+Commands that affect live ad delivery: `suspend`, `resume`, `archive`, `unarchive` (available on `campaigns`, `ads`), `suspend`, `resume` (also on `keywords`).
 
 Commands that affect bids and spending: `bids set`, `keywordbids set`, `bidmodifiers set`.
 
@@ -439,6 +467,27 @@ YANDEX_DIRECT_LIVE_WRITE=1 pytest -m integration_live_write -v  # live draft cas
 YANDEX_DIRECT_LIVE_WRITE=1 pytest -m integration_live_write -v --record-mode=rewrite  # re-record live draft cassette
 ```
 
+#### Smoke command scripts
+
+Every CLI subcommand is classified in `direct_cli/smoke_matrix.py`.
+
+| Category | Script | When to run |
+|---|---|---|
+| SAFE | `scripts/test_safe_commands.sh` | Production read-only smoke checks; requires `YANDEX_DIRECT_TOKEN` and `YANDEX_DIRECT_LOGIN` |
+| WRITE_SANDBOX | `scripts/test_sandbox_write.sh` | Live sandbox write smoke checks; requires `YANDEX_DIRECT_TOKEN` and `YANDEX_DIRECT_LOGIN`; reports `PASS`, `FAIL`, `SANDBOX_LIMITATION`, or `NOT_COVERED` for each command |
+| DANGEROUS | `scripts/test_dangerous_commands.sh` | Manual checklist only; exits with status 1 by design |
+
+Current command surface:
+
+| Metric | Count |
+|---|---:|
+| WSDL-backed API services | 29 |
+| Supported API services including Reports | 30 |
+| WSDL operations | 112 |
+| CLI groups including `auth` | 31 |
+| CLI subcommands including `auth` | 122 |
+| API CLI subcommands excluding `auth` | 118 |
+
 ### API Coverage And Drift Monitoring
 
 The project now distinguishes four surfaces:
@@ -471,24 +520,43 @@ CI runs a scheduled API coverage workflow that:
   parity and live-discovered model gap counts;
 - checks the cached WSDL files against the live Yandex Direct API on schedule.
 
-#### Re-recording write cassettes
+#### Live sandbox write smoke
+
+`WRITE_SANDBOX` smoke is a live check against the Yandex Direct **sandbox**.
+It does not replay stored HTTP traffic and it does not create new recordings.
+Run it only when you intentionally want to call `api-sandbox.direct.yandex.com`:
+
+```bash
+set -a && source .env && set +a
+scripts/test_sandbox_write.sh
+```
 
-The write tests replay HTTP traffic captured from the Yandex Direct **sandbox**
-(`--sandbox` is injected automatically).  Cassettes live under
-`tests/cassettes/test_integration_write/` and are checked into git.
+The runner executes matrix commands through `direct --sandbox ...`, creates
+temporary sandbox prerequisites where possible, and cleans them up best-effort.
+The report contains one row per `WRITE_SANDBOX` command:
 
-If you change the request payload of any write command (e.g. adding a field),
-the matching cassette stops replaying and the test fails with a body-mismatch
-error.  To regenerate:
+- `PASS` means the command completed against the live sandbox API.
+- `SANDBOX_LIMITATION` means the request reached the API and hit a known
+  sandbox-only limitation such as codes `8800`, `1000`, `3500`, or `5004`.
+- `FAIL` means an unexpected CLI or API error.
+- `NOT_COVERED` means the runner does not yet know how to safely build the
+  prerequisites for that command.
+
+The same OAuth token works for both production and the sandbox; no separate
+sandbox token is needed.
+
+#### Re-recording write cassettes
+
+The `integration_write` pytest tier still replays stored write-test traffic
+for regression coverage. If you change those tests or their payloads and
+intentionally need to refresh the fixtures, regenerate them separately:
 
 ```bash
 set -a && source .env && set +a        # load YANDEX_DIRECT_TOKEN / LOGIN
 pytest -m integration_write -v --record-mode=rewrite
 ```
 
-**The same OAuth token works for both production and the sandbox** — no
-separate sandbox token is needed.  After recording, **always audit the
-generated YAMLs for leaked secrets**:
+After recording, **always audit the generated YAMLs for leaked secrets**:
 
 ```bash
 grep -r "$YANDEX_DIRECT_TOKEN" tests/cassettes/   # must return nothing
@@ -583,6 +651,45 @@ YANDEX_DIRECT_LOGIN=ваш_логин_на_яндексе
 direct --token ВАШ_ТОКЕН --login ВАШ_ЛОГИН campaigns get
 ```
 
+Используйте профильные credentials из `.env`:
+
+```env
+YANDEX_DIRECT_TOKEN_AGENCY1=token-1
+YANDEX_DIRECT_LOGIN_AGENCY1=client-login-1
+YANDEX_DIRECT_TOKEN_AGENCY2=token-2
+YANDEX_DIRECT_LOGIN_AGENCY2=client-login-2
+```
+
+OAuth и profile-команды:
+
+```bash
+direct auth login
+direct auth login --profile agency1
+direct auth login --code abc123 --profile agency1
+direct auth login --oauth-token y0_example --profile agency1
+direct auth list
+direct auth use --profile agency1
+direct auth status --profile agency1
+direct --profile agency1 campaigns get
+```
+
+Порядок выбора credentials:
+
+| Приоритет | Источник | Пример |
+|-----------|----------|--------|
+| 1 | Явные CLI-опции | `direct --token TOKEN --login LOGIN campaigns get` |
+| 2 | OAuth profile storage | `direct --profile agency1 campaigns get` |
+| 3 | Профильные env vars | `YANDEX_DIRECT_TOKEN_AGENCY1`, `YANDEX_DIRECT_LOGIN_AGENCY1` |
+| 4 | Базовые env vars или project `.env` | `YANDEX_DIRECT_TOKEN`, `YANDEX_DIRECT_LOGIN` |
+| 5 | 1Password references | `--op-token-ref`, `YANDEX_DIRECT_OP_TOKEN_REF` |
+| 6 | Bitwarden references | `--bw-token-ref`, `YANDEX_DIRECT_BW_TOKEN_REF` |
+
+Файл `.env` в проекте загружается автоматически. Если профиль выбран через
+`--profile` или `direct auth use --profile NAME`, Direct CLI не подставляет
+base `YANDEX_DIRECT_LOGIN`; это защищает от смешивания токена из профиля с
+логином из project `.env`. Для нескольких аккаунтов используйте OAuth profiles
+или профильные env vars, а не базовые credentials.
+
 Установка остаётся через `pip install direct-cli`, а запуск команд теперь идет
 через `direct`. Вызов deprecated entrypoint `direct-cli` завершается ошибкой с
 подсказкой `use direct instead of direct-cli`.
@@ -593,6 +700,7 @@ direct --token ВАШ_ТОКЕН --login ВАШ_ЛОГИН campaigns get
 |-------|----------|
 | `--token` | OAuth-токен доступа к API |
 | `--login` | Direct client login |
+| `--profile` | Имя credential profile |
 | `--sandbox` | Использовать тестовое API (песочница) |
 
 ### Использование
@@ -624,6 +732,17 @@ Command naming rules:
 должен быть добавлен как явное exception-правило с конкретным legacy syntax из
 `tapi-yandex-direct`, который действительно нужно поддержать.
 
+Удалённые исторические имена:
+
+| Историческое имя           | Каноническое имя             |
+|----------------------------|------------------------------|
+| `dynamictargets`           | `dynamicads`                 |
+| `smarttargets`             | `smartadtargets`             |
+| `negativekeywords`         | `negativekeywordsharedsets`  |
+| `list`                     | `get`                        |
+| `checkcamp`                | `check-campaigns`            |
+| `checkdict`                | `check-dictionaries`         |
+
 `direct` — это канонический transport entrypoint над API Яндекс Директа,
 устанавливаемый пакетом `direct-cli`. Канонические имена CLI-групп следуют
 нормализованным Python-именам из `tapi-yandex-direct`, а имена подкоманд —
@@ -704,7 +823,7 @@ direct dictionaries get-geo-regions \
 #### Flag Design Rules
 
 - List inputs use comma-separated CLI syntax where appropriate.
-- Money and bid values stay human-readable in CLI input and are converted internally to the API wire format.
+- Money and bid values are passed in micro-rubles (API-native format). Values below 100,000 trigger a validation hint suggesting the correct scale.
 - Selector fields remain explicit flags, for example:
   - `--id`
   - `--campaign-id`
@@ -747,7 +866,7 @@ Valid canonical examples:
 direct campaigns get --ids 1,2,3
 direct changes check-campaigns --timestamp 2026-04-14T00:00:00
 direct keywordsresearch has-search-volume --keywords "buy laptop,buy desktop"
-direct dynamicads set-bids --id 789 --bid 12.5
+direct dynamicads set-bids --id 789 --bid 12500000
 direct dictionaries get-geo-regions --region-ids 225 --fields GeoRegionId,GeoRegionName
 ```
 
@@ -755,7 +874,7 @@ Invalid examples:
 
 ```bash
 direct dictionaries get-geo-regions --json '{"GeoRegionIds":[225]}' --fields GeoRegionId,GeoRegionName
-direct dynamicads set-bids --id 789 --bid 12.5 --json '{"StrategyPriority":"HIGH"}'
+direct dynamicads set-bids --id 789 --bid 12500000 --json '{"StrategyPriority":"HIGH"}'
 direct dictionaries get-geo-regions \
   --region-ids 225 \
   --fields GeoRegionId,GeoRegionName
@@ -773,12 +892,12 @@ direct campaigns get --ids 1,2,3 --format table
 direct campaigns get --fetch-all --format csv --output campaigns.csv
 
 # Создать (--dry-run покажет запрос без отправки)
-direct campaigns add --name "Моя кампания" --start-date 2024-02-01 --type TEXT_CAMPAIGN --budget 1000 --setting ADD_METRICA_TAG=YES --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
+direct campaigns add --name "Моя кампания" --start-date 2024-02-01 --type TEXT_CAMPAIGN --budget 1000000000 --setting ADD_METRICA_TAG=YES --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
 direct campaigns add --name "Динамическая кампания" --start-date 2024-02-01 --type DYNAMIC_TEXT_CAMPAIGN --setting ADD_METRICA_TAG=NO --search-strategy HIGHEST_POSITION --network-strategy SERVING_OFF --dry-run
-direct campaigns add --name "Смарт-кампания" --start-date 2024-02-01 --type SMART_CAMPAIGN --network-strategy AVERAGE_CPC_PER_FILTER --filter-average-cpc 1 --counter-id 123 --dry-run
+direct campaigns add --name "Смарт-кампания" --start-date 2024-02-01 --type SMART_CAMPAIGN --network-strategy AVERAGE_CPC_PER_FILTER --filter-average-cpc 1000000 --counter-id 123 --dry-run
 
 # Обновление и управление статусом
-direct campaigns update --id 12345 --name "Новое название" --status SUSPENDED --budget 100 --start-date 2024-02-10 --end-date 2024-03-01
+direct campaigns update --id 12345 --name "Новое название" --status SUSPENDED --budget 100000000 --start-date 2024-02-10 --end-date 2024-03-01
 direct campaigns suspend --id 12345
 direct campaigns resume --id 12345
 direct campaigns archive --id 12345
@@ -812,7 +931,7 @@ direct ads delete --id 99999
 
 ```bash
 direct keywords get --campaign-ids 1,2,3
-direct keywords add --adgroup-id 12345 --keyword "купить ноутбук" --bid 10.50 --context-bid 5.25 --user-param-1 segment-a --user-param-2 segment-b --dry-run
+direct keywords add --adgroup-id 12345 --keyword "купить ноутбук" --bid 10500000 --context-bid 5250000 --user-param-1 segment-a --user-param-2 segment-b --dry-run
 direct keywords update --id 88888 --keyword "updated keyword text"
 direct keywords delete --id 88888
 ```
@@ -850,22 +969,22 @@ direct retargeting add --name "Список A" --type AUDIENCE --rule "ALL:12345
 direct retargeting update --id 55 --name "Переименованный список" --rule "ANY:12345:30" --dry-run
 
 # Ставки и модификаторы
-direct bids set --keyword-id 123 --bid 15
-direct bids set-auto --keyword-id 123 --max-bid 20 --position PREMIUMBLOCK --scope SEARCH --dry-run
-direct keywordbids set --keyword-id 321 --search-bid 8 --network-bid 3
-direct keywordbids set-auto --keyword-id 321 --target-traffic-volume 100 --increase-percent 10 --bid-ceiling 12.5 --dry-run
+direct bids set --keyword-id 123 --bid 15000000
+direct bids set-auto --keyword-id 123 --max-bid 20000000 --position PREMIUMBLOCK --scope SEARCH --dry-run
+direct keywordbids set --keyword-id 321 --search-bid 8000000 --network-bid 3000000
+direct keywordbids set-auto --keyword-id 321 --target-traffic-volume 100 --increase-percent 10 --bid-ceiling 12500000 --dry-run
 direct bidmodifiers add --campaign-id 123 --type DEMOGRAPHICS_ADJUSTMENT --value 150 --gender GENDER_MALE --age AGE_25_34 --dry-run
 direct bidmodifiers set --id 99 --value 130 --dry-run
 
 # Канонические многословные группы
 direct negativekeywordsharedsets update --id 123 --keywords "foo,bar"
-direct audiencetargets add --adgroup-id 100 --retargeting-list-id 200 --bid 12 --priority HIGH --dry-run
-direct audiencetargets set-bids --id 101 --context-bid 7 --priority LOW --dry-run
-direct dynamicads add --adgroup-id 33 --name "Webpage A" --condition "URL:CONTAINS_ANY:test|shop" --condition "PAGE_CONTENT:CONTAINS:baz" --bid 3 --context-bid 2 --priority HIGH --dry-run
-direct smartadtargets add --adgroup-id 55 --name "Audience A" --audience ALL_SEGMENTS --condition "CATEGORY_ID:EQUALS:42" --average-cpc 3 --average-cpa 4 --priority HIGH --available-items-only YES --dry-run
+direct audiencetargets add --adgroup-id 100 --retargeting-list-id 200 --bid 12000000 --priority HIGH --dry-run
+direct audiencetargets set-bids --id 101 --context-bid 7000000 --priority LOW --dry-run
+direct dynamicads add --adgroup-id 33 --name "Webpage A" --condition "URL:CONTAINS_ANY:test|shop" --condition "PAGE_CONTENT:CONTAINS:baz" --bid 3000000 --context-bid 2000000 --priority HIGH --dry-run
+direct smartadtargets add --adgroup-id 55 --name "Audience A" --audience ALL_SEGMENTS --condition "CATEGORY_ID:EQUALS:42" --average-cpc 3000000 --average-cpa 4000000 --priority HIGH --available-items-only YES --dry-run
 direct smartadtargets update --id 456 --priority HIGH
-direct smartadtargets set-bids --id 456 --average-cpc 10.5 --average-cpa 15 --priority HIGH
-direct dynamicads set-bids --id 789 --bid 12.5 --context-bid 9 --priority HIGH
+direct smartadtargets set-bids --id 456 --average-cpc 10500000 --average-cpa 15000000 --priority HIGH
+direct dynamicads set-bids --id 789 --bid 12500000 --context-bid 9000000 --priority HIGH
 
 # Общие стратегии ставок
 direct strategies get --limit 5
@@ -875,8 +994,8 @@ direct strategies archive --id 42 --dry-run
 
 # Динамические таргеты по фиду
 direct dynamicfeedadtargets get --adgroup-ids 123 --limit 5
-direct dynamicfeedadtargets add --adgroup-id 33 --name "Срез фида А" --condition "CATEGORY:EQUALS:shoes" --bid 5 --dry-run
-direct dynamicfeedadtargets set-bids --id 789 --bid 6.5 --context-bid 4 --dry-run
+direct dynamicfeedadtargets add --adgroup-id 33 --name "Срез фида А" --condition "CATEGORY:EQUALS:shoes" --bid 5000000 --dry-run
+direct dynamicfeedadtargets set-bids --id 789 --bid 6500000 --context-bid 4000000 --dry-run
 
 # Расширения, ассеты, фиды и клиенты
 direct sitelinks add --sitelink "Docs|https://example.com/docs" --sitelink "Help|https://example.com/help|Desk" --dry-run
@@ -936,7 +1055,7 @@ direct campaigns get --fetch-all   # все страницы
 | `keywords delete --id` | Безвозвратно удаляет ключевое слово |
 | `audiencetargets delete --id` | Безвозвратно удаляет условие подбора аудитории |
 
-Команды, влияющие на показ рекламы: `suspend`, `resume`, `archive`, `unarchive` (доступны для `campaigns`, `ads`, `keywords`).
+Команды, влияющие на показ рекламы: `suspend`, `resume`, `archive`, `unarchive` (доступны для `campaigns`, `ads`), `suspend`, `resume` (также для `keywords`).
 
 Команды, влияющие на ставки и расходы: `bids set`, `keywordbids set`, `bidmodifiers set`.
 
@@ -966,24 +1085,64 @@ YANDEX_DIRECT_LIVE_WRITE=1 pytest -m integration_live_write -v  # replay live dr
 YANDEX_DIRECT_LIVE_WRITE=1 pytest -m integration_live_write -v --record-mode=rewrite  # перезапись live draft-кассеты
 ```
 
-#### Перезапись write-кассет
+#### Smoke-скрипты команд
+
+Каждая CLI-подкоманда классифицирована в `direct_cli/smoke_matrix.py`.
+
+| Категория | Скрипт | Когда запускать |
+|---|---|---|
+| SAFE | `scripts/test_safe_commands.sh` | Production smoke-проверки только на чтение; нужны `YANDEX_DIRECT_TOKEN` и `YANDEX_DIRECT_LOGIN` |
+| WRITE_SANDBOX | `scripts/test_sandbox_write.sh` | Live sandbox write-проверки; нужны `YANDEX_DIRECT_TOKEN` и `YANDEX_DIRECT_LOGIN`; отчёт печатает `PASS`, `FAIL`, `SANDBOX_LIMITATION` или `NOT_COVERED` для каждой команды |
+| DANGEROUS | `scripts/test_dangerous_commands.sh` | Только ручной checklist; специально завершается с кодом 1 |
+
+Текущая поверхность команд:
+
+| Метрика | Количество |
+|---|---:|
+| WSDL-backed API services | 29 |
+| API services с учётом Reports | 30 |
+| WSDL operations | 112 |
+| CLI groups с `auth` | 31 |
+| CLI subcommands с `auth` | 122 |
+| API CLI subcommands без `auth` | 118 |
+
+#### Live sandbox write smoke
+
+`WRITE_SANDBOX` smoke — это live-проверка против **sandbox-окружения**
+Яндекс Директа. Она не воспроизводит сохранённый HTTP-трафик и не создаёт
+новые записи. Запускайте её только когда намеренно хотите обратиться к
+`api-sandbox.direct.yandex.com`:
 
-Write-тесты воспроизводят HTTP-трафик, записанный против **sandbox-окружения**
-Яндекс Директа (`--sandbox` подставляется автоматически). Кассеты лежат в
-`tests/cassettes/test_integration_write/` и закоммичены в git.
+```bash
+set -a && source .env && set +a
+scripts/test_sandbox_write.sh
+```
+
+Runner выполняет команды matrix через `direct --sandbox ...`, создаёт
+временные sandbox prerequisites там, где это безопасно, и удаляет их
+best-effort. Отчёт содержит одну строку на каждую команду `WRITE_SANDBOX`:
+
+- `PASS`: команда прошла против live sandbox API.
+- `SANDBOX_LIMITATION`: запрос дошёл до API и получил известное ограничение
+  sandbox, например коды `8800`, `1000`, `3500` или `5004`.
+- `FAIL`: неожиданный CLI/API error.
+- `NOT_COVERED`: runner пока не умеет безопасно построить prerequisites.
+
+Один и тот же OAuth-токен работает и для продакшена, и для sandbox; отдельный
+sandbox-токен не нужен.
+
+#### Перезапись write-кассет
 
-Если меняется payload какой-то из write-команд (например, добавили поле),
-соответствующая кассета перестанет воспроизводиться, тест упадёт с
-body-mismatch. Перезапись:
+Уровень `integration_write` в pytest всё ещё воспроизводит сохранённый
+write-трафик для регрессионного покрытия. Если вы меняете эти тесты или их
+payload и намеренно хотите обновить fixtures, перезаписывайте их отдельно:
 
 ```bash
 set -a && source .env && set +a        # загрузить YANDEX_DIRECT_TOKEN / LOGIN
 pytest -m integration_write -v --record-mode=rewrite
 ```
 
-**Один и тот же OAuth-токен работает и для продакшена, и для sandbox** —
-отдельный sandbox-токен не нужен. После перезаписи **обязательно проверьте
-YAML-ы на утечку секретов**:
+После перезаписи **обязательно проверьте YAML-ы на утечку секретов**:
 
 ```bash
 grep -r "$YANDEX_DIRECT_TOKEN" tests/cassettes/   # должно быть пусто