feat(masters): add direct masters add — create Мастер кампаний

[axisrow]

Summary

• Implements direct masters add — creates a brand-new "Конверсии и трафик" Мастер кампаний by driving the same create wizard a human uses (Мастер кампаний has no API surface at all, same as list/get/suspend/resume/update).
• Step 0 live recon (read-only, no campaign was ever created/saved) is committed as tests/fixtures/masters_wizard_create.html and found the create flow is not the multi-page "Далее" wizard the issue originally assumed: one micro-step (landing URL + client-side format validation) followed by a single long form, terminating in two buttons — "Запустить кампанию" (launch) and "Сохранить как черновик" (draft) — instead of masters update's single "Сохранить кампанию".
• --headline/--text/--region are required (repeat for multiple values), even though Yandex's own wizard auto-generates headlines/texts by scanning the landing page — add refuses to silently publish AI-written ad copy the caller never reviewed, given there's no sandbox/rollback for Мастер кампаний.
• --weekly-budget optional; --draft/--launch (default --launch) picks the terminal button.
• NOT idempotent — a second run with the same arguments creates a second campaign, not an update. Documented in --help, README, and CHANGELOG per the issue's "Риски" section.
• Classified DANGEROUS in smoke_matrix.py / test_dangerous_commands.sh — no --sandbox equivalent exists for Мастер кампаний mutations.

Test plan

• pytest tests/test_masters.py -q — 112 tests covering every new private helper (_fill_landing_url, _wait_for_step2, _add_repeating_values, _set_region, _set_weekly_budget_on_create, _click_terminal_button, create_master) plus CLI wiring, all against fake Page/Locator objects (no real browser).
• pytest -q — full offline suite green (2691 passed; the 62 errors are a pre-existing, unrelated VCR/aiohttp version-mismatch environment issue, not caused by this change).
• black/flake8 clean on all touched files.
• Live verification (manual, per issue direct masters add — создание Мастера кампаний #632 "Верификация") — not performed in this PR. create_master is offline-tested only; end-to-end launch/draft behavior against a real account (including where the created campaign's ID can be read from) still needs a live pass with --draft first.

Closes #632

[axisrow]

Code review (post-merge)

Retroactive review requested by issue #648 (item 3) since PR #647 shipped without a formal review pass. Ran the standard 5-angle review (CLAUDE.md compliance, bug scan, git-blame/history, prior-PR review comments, code-comment compliance) against the diff as merged (cf1552e) and cross-checked every finding against current main.

No live issues found. Summary of what the passes surfaced:

• All 5 reviewers independently flagged one historical gap: _wait_for_step2 (as merged) used a raw time.monotonic() poll loop instead of the injectable clock — the pattern CLAUDE.md's "Browser poll loops use an injectable clock" section (issue Offline test suite is too slow (full run ~4-5 min, tests/test_masters.py alone ~2-3 min) #767) now forbids. The clock module (direct_cli/browser/_clock.py) didn't exist yet when feat(masters): add direct masters add — create Мастер кампаний #647 was authored, so this wasn't a violation of an existing rule at merge time. The function was independently rewritten (issue masters add: step 1 URL field no longer advances via CampaignFormUrl.button (Combobox markup drift) #690/masters create: region picker (RegionsTreeEditor/RegionsTreeTagGroup) no longer renders on step 2, breaking create_master end-to-end #705 live re-recon) and later hardened onto _poll_until (clock-safe) — confirmed current _wait_for_step2 (direct_cli/browser/masters.py:7118) uses _poll_until, not a raw deadline. No action needed.
• _verify_created's original design was a weaker, no-reload check versus the sibling update_master/_verify_saved pattern — but the original docstring said so explicitly rather than hiding it, and it was subsequently strengthened by masters create: reload-based region verification in _verify_created needs live post-click URL recon #744/masters add: confirm the edit page renders the region widget for a LAUNCHED campaign #776/masters add: support conversion goals — the create form is rejected without one #777 to add a real reload-and-reread (current direct_cli/browser/masters.py:8970-9089).
• Region-set verification was explicitly documented as unreliable at merge time (_read_region_tags's docstring said as much) and _verify_created deliberately skipped verifying it rather than trusting a broken reader — later fixed once _wait_for_created_campaign_id (masters create: reload-based region verification in _verify_created needs live post-click URL recon #744) gave verification a page to reload against.
• _add_target_action's bounded-timeout root-cause bug (ba3a269) is inherited for free by create_master since it calls the same shared helper — no separate fix needed there.
• One still-open, pre-existing and documented gap (not a feat(masters): add direct masters add — create Мастер кампаний #647 defect): --launch (actual publish, not --draft) has not yet been exercised in a live run — only --draft has (campaign 713337891, per masters add: support conversion goals — the create form is rejected without one #777's resolution). Relevant to issue direct masters — follow-up: Этапы B/C/D update, живая проверка add/archive/update, ревью #647 #648 item 2 (live verification of masters add), not to this review.

No CLAUDE.md violations, no unresolved bugs, no inconsistency between code comments and behavior found in the current state of the code this PR introduced.

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}