feat(cli): add verbose logging to watch

[lntutor]

Summary

• add --verbose / -v to repowise watch
• configure logging before target resolution for both single-repo and workspace modes
• propagate verbose mode into nested single-repo update invocations so it is not reset to quiet
• document the flag and add focused quiet/verbose forwarding coverage
• clean up two unused imports and correct the touched file’s invalid callable type annotation

Related Issues

Part of #930 (watch slice).

Test Plan

• focused watch and command tests (32 passed)
• CLI unit suite (804 passed, 1 unrelated baseline failure)
• Ruff lint and format checks on modified Python files
• strict mypy check for watch_cmd.py
• git diff --check

The sole CLI-suite failure is the existing mascot tagline assertion test_banner_at_wide_width_stays_compact_with_long_tagline; it reproduces unchanged on clean origin/main.

Checklist

• My code follows the project style
• I added tests for the new functionality
• I updated the CLI reference
• All existing tests pass (see unrelated baseline failure above)

[repowise-bot]

✅ Health: 7.5 (unchanged)

📋 At a glance
1 file changed health · 2 hotspots touched · 1 new finding introduced · 1 file with recent fix history.

Files & modules (2)

• packages (1 file)
  • .../commands/watch_cmd.py
• tests (1 file)
  • .../cli/test_commands.py

📌 Before you merge

• Run tests/integration/test_cli.py: they depend on the changed files
• Docs that usually track this code: docs/CLI_REFERENCE.md

🗺️ Change map

flowchart LR
  subgraph PR ["Changed in this PR (2 with dependents)"]
    f_packages_cli_src_repowise_cli_commands_watch_cmd_py[".../commands/watch_cmd.py 🔥"]:::changed
    f_tests_unit_cli_test_commands_py[".../cli/test_commands.py"]:::changed
  end
  f_packages_cli_src_repowise_cli_main_py[".../cli/main.py"]
  f_packages_cli_src_repowise_cli_commands_watch_cmd_py --> f_packages_cli_src_repowise_cli_main_py
  f_packages_cli_src_repowise_cli_commands_init_cmd_command_py[".../init_cmd/command.py"]
  f_tests_unit_cli_test_commands_py --> f_packages_cli_src_repowise_cli_commands_init_cmd_command_py
  f_packages_cli_src_repowise_cli_helpers_py[".../cli/helpers.py"]
  f_tests_unit_cli_test_commands_py --> f_packages_cli_src_repowise_cli_helpers_py
  f_packages_cli_src_repowise_cli_mcp_config_py[".../cli/mcp_config.py"]
  f_tests_unit_cli_test_commands_py --> f_packages_cli_src_repowise_cli_mcp_config_py
  t_tests_integration_test_cli_py(["✅ tests/integration/test_cli.py"]):::guard
  t_tests_integration_test_cli_py -.-> f_tests_unit_cli_test_commands_py
  classDef changed fill:#dbeafe,stroke:#1d4ed8,color:#1e3a5f
  classDef warn fill:#fef3c7,stroke:#b45309,color:#78350f
  classDef guard fill:#dcfce7,stroke:#15803d,color:#14532d

Loading

_{Solid arrows: code that imports the changed files (4 direct dependents, from the last indexed snapshot). Dashed: history/tests.}

🩹 Review priority _{(files here with the most recent bug-fix history — defects cluster, so review these first)}

• .../cli/test_commands.py — fixed 4× in the last ~6 months

File	Score	Δ	Why
.../commands/watch_cmd.py	8.7 → 8.3	▼ -0.4	🔻 introduced primitive obsession

🔎 More signals (1)

🔥 Hotspots touched (2)

• .../commands/watch_cmd.py — 1 commits/90d, 1 dependents · primary owner: Raghav Chamadiya (100%)
• .../cli/test_commands.py — 11 commits/90d, 4 dependents · primary owner: Raghav Chamadiya (61%)

---

📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-19 19:40 UTC
_{Silence on a single PR with [skip repowise] in the title · Per-repo toggle on repowise.dev/settings?tab=bot}

[RaghavChamadiya]

Approving. Forwarding --verbose into the nested update_command invocation is necessary, not decorative: that child run re-enters configure_cli_logging and would otherwise reset to quiet.

Two notes, neither blocking. The find_workspace_root / resolve_repo_path import removal is correct, they were genuinely unused, but the drive-by formatting churn in _watch_workspace makes the diff harder to read than it needs to be. And for the record, _watch_workspace not taking verbose is fine: it calls update_workspace in-process, so the process-wide config already applies. Worth knowing so nobody "fixes" it later.