verifylisted

# Verify Verify from the current source of truth. ## Route - **Local verify:** For ordinary verification requests, inspect and test locally. Never call an external LLM. - **Claude crosscheck:** Only when the user explicitly asks to involve Claude in this task. Codex remains the host and owns implementation; Claude analyzes and verifies in read-only plan mode. - Infer `analyze`, `plan`, `full`, or `verify` from the request. If implementation is excluded, stop before it. Otherwise an explicit request to crosscheck and do the work uses `full`. ## Shared rules - Treat review-only requests as read-only. Fix findings only when the user asks for changes. - Start with `git status --short` and the relevant diff or stated baseline. - Trace callers, contracts, authorization, state changes, and cache or persistence effects before judging completion. - Confirm each finding at the cited file and reachable call path. Do not accept another agent's claim without checking it. - Run the smallest existing local checks that cover the change. Prefer the project's test command; use syntax or build checks only when they prove the relevant property. - A direct request to run tests is approval for local tests. Ask separately before DB, network, remote, destructive, or service-changing checks. - Never call `codex`, `codex exec`, or `codex_ask.sh` from this Codex entrypoint. - A generic "검증해줘" is not permission to call Claude. An explicit task-scoped request such as "클로드랑 크로스체크해줘" authorizes Claude