What problem does it solve? Schema, prompt, identity, adapter, cache, or rename changes often pass parser-level tests while stale behavior persists in alternate entry points, persisted state, or generated artifacts. This Skill prevents incomplete runtime validation by systematically mapping every consumer a changed value can reach. ## Core Features & Use Cases - Consumer Mapping: Marks each affected dimension (parser-to-runtime, alternate entry points, generated/cached values, fixtures, string remnants) as covered, not applicable, or unknown with reasons. - Old/New Token Search: Searches for both old and new identifiers beyond source files, including ignored build outputs and raw serialized shapes. - End-to-End Verification: Exercises runtime paths through final consumers such as TUI, exec, ACP, and task/session launches rather than stopping at parser tests. - Use Case: After renaming a configuration field, use this Skill to confirm the new name propagates through launch options, adapters, prompt caches, and historical-data importers before declaring the change complete. ## Quick Start Verify that my recent schema field rename reaches every runtime consumer, including adapters, caches, and persisted state, and report any remaining old-token hits.
