ry-reviewlisted

# ry-review ## Purpose Find real issues before merge or deploy. Default mode is report-only: do not edit files unless the user explicitly asks after seeing findings. ## Workflow 1. Determine review target: current diff, branch vs main, PR, file scope, or prompt scope. 2. Initialize missing context with `ry-init` if needed. 3. Use Serena to map changed symbols and affected integration graph (`get_symbols_overview`, targeted `find_symbol`, `find_referencing_symbols`). 4. Use `rldyour-explore` for current implementation best practices when the review depends on external technology behavior. 5. Run reviewer tracks. Use parallel subagents when this review request or an explicit-review `ry-start` request calls for parallel review. 6. Consolidate findings by severity and confidence. Validate uncertain findings with code evidence. 7. Output Russian report with exact paths, impact, suggested fixes, and whether each finding is must-fix. ## Review Target Parsing When the user asks for a time-window or history-based review, resolve the review target before dispatching reviewers: - `last N days` / `за последние N дней`: compute the exact commit range with `git log --since`. - `since DATE` / `с DATE`: use the explicit date as the lower bound. - `PR #N` or `issue #N`: inspect the GitHub PR/issue and verify its relevance against current code before treating it as a finding. - `branch vs main`: review the merge-base diff plus related commits. - `since last deploy`: identify the las