grace-refreshlisted

Synchronize the GRACE shared artifacts with the actual codebase. ## Refresh Modes Default to the narrowest scope that can still answer the drift question. ### `targeted` (default during active execution) - scan only changed modules, touched imports, and directly affected dependency surfaces - use when a controller already has wave results or graph delta proposals - ideal after a clean multi-agent wave ### `full` - scan the whole source tree - use after refactors, manual edits across many modules, phase completion, or when targeted refresh finds suspicious drift ## Process ### Step 1: Choose Scope Decide whether the refresh should be `targeted` or `full`. 1. If the caller provides changed files, module IDs, or graph delta proposals, start with `targeted` 2. If no reliable scope is available, or the graph may have drifted broadly, use `full` 3. Escalate from `targeted` to `full` when the localized scan reveals wider inconsistency When the optional `grace` CLI is available, you may use `setup-grace-lint <project-root>` as a quick preflight before starting a broader refresh. Treat it as a hint source, not as the refresh itself. You may also use: - `grace module find <changed-path-or-query> --path <project-root>` to resolve the likely module scope from changed files or names - `grace module show M-XXX --path <project-root> --with verification` to grab the shared/public contract, dependency, and verification context - `grace file show <path> --path <project-root> --contrac