direct-cli 0.5.2__tar.gz → 0.5.4__tar.gz

{direct_cli-0.5.2 → direct_cli-0.5.4}/.github/workflows/quality.yml

@@ -38,6 +38,9 @@ jobs:
       - name: Type check
         run: mypy .
 
+      - name: Pyright
+        run: pyright
+
       - name: Run offline tests
         # Offline default comes from pyproject addopts (skips the live-network
         # markers). integration_write stays in — it replays VCR cassettes offline.

{direct_cli-0.5.2 → direct_cli-0.5.4}/AGENTS.md

@@ -35,13 +35,33 @@ Naming rules:
 
 ### Input Rules
 
-- All user-facing input must be passed only through typed CLI flags.
+- In default headless mode, all user-facing input must be passed only through typed CLI flags.
+- Authentication input prompts require explicit `direct auth login --interactive`.
 - `--json` is not part of the public CLI contract.
 - User-facing parameters must not be passed through `--json`.
 - The CLI must not accept `SelectionCriteria`, nested payloads, update payloads, bidding rules, or any other user-facing command input through `--json`.
 - Typed flags and JSON blobs must not be mixed as part of one public command contract.
 - If the API requires a complex object, the CLI must expose explicit flags or subcommands instead of forwarding raw JSON.
 
+### Authorization Execution Mode
+
+- Authorization is headless and non-interactive by default, including when stdin and stdout are terminals. TTY detection must never enable login dialogs or browser UI by itself.
+- `direct auth login` defaults to the headless API flow: print the authorization URL and accept the completion code later through typed flags or explicit stdin input.
+- Login menus and OAuth code prompts require `direct auth login --interactive`.
+- Manual browser login requires explicit `--interactive` or `--headful`. `--allow-no-tty` only overrides the terminal check; it does not authorize browser UI by itself.
+- Chrome import is headless by default. Failed headless verification must not retry in a visible browser automatically.
+- Missing or expired credentials in ordinary commands produce an actionable error, never an implicit login.
+- Saving credentials into an existing profile requires explicit `--force`; the headless completion and token import refuse to overwrite otherwise.
+
+### Data Safety — No Silent Overwrites
+
+- Stored user data (auth profiles, credentials, folder bindings, browser sessions) is never replaced silently.
+- A write is either the command's declared purpose (the command then reports what was replaced) or requires an explicit confirmation flag (`--force`). Ordinary commands never write stored user data as a side effect.
+- Overwriting an existing auth profile requires explicit `--force` on the CLI layer and `overwrite=True` on the helper layer; the refusal names the current owner's login.
+- Replacing an existing `YANDEX_DIRECT_TOKEN` in the folder `.env` prints a warning naming the previous owner.
+- New write paths for stored user data must go through the guarded helpers (`save_oauth_profile`, `save_env_credentials`); bypassing the guard is a contract violation.
+- Production API mutations are always explicit commands, classified SAFE / WRITE_SANDBOX / DANGEROUS in `direct_cli/smoke_matrix.py`.
+
 ### Command Formatting Rules
 
 - Every canonical CLI command must be written strictly on a single line.