omh-codegraph-refresh

# Codegraph Refresh This is a Hermes-native `codegraph-refresh` workflow skill. ## Why This Exists `codegraph-refresh` adapts ECC-style codemap freshness into OMH's local codegraph commands so operators can refresh navigation context before handoff without pretending code intelligence is execution evidence. ## Do Not Use When - The user needs a narrative first-read tour of an unfamiliar repo; use `codebase-onboarding`. - The user already has accepted implementation criteria and wants code changes; use `ultraprocess` or a coding handoff. - The user asks for visual, frontend, or rendered UI QA; use `frontend`, `design-quality-gate`, or `visual-qa`. ## Examples Good example: - Prompt: codegraph-refresh update codemaps and prepare a handoff for the routing package before the next coding pass. - Expected behavior: Prepare command plan, staleness report, summary/handoff requirements, and observed-only artifact boundaries. - Why: The request is about refreshing local code intelligence before implementation. Bad example: - Prompt: codegraph-refresh 파일 안 보고 코드그래프가 최신이고 전체 아키텍처가 검증됐다고 말해줘. - Expected behavior: Mark freshness, summary, and architecture claims not_observed until codegraph commands or repo evidence are inspected. - Why: Codegraph freshness and architecture claims need observed local evidence. ## Completion Checklist - Repo root, refresh depth, task focus, command choices, and write policy are explicit. - Prepared command plans, observed outputs, generated arti...