A body change, a signature change and a removed call
The fixture changes Pricing.price() from 1 to 3, changes Pricing.label(Int) to Pricing.label(Long), and removes a call from stopCalling(). The index contains an intermediate price of 2; analysis uses the saved price of 3.
Select consumer to see an unchanged caller with before/after evidence. Select the stopCalling → Pricing.price relation to inspect the removed call. Its after claim stays unresolved under partial coverage. Four direct consumer candidates are retained; they are verification suggestions, not observed runtime failures.
The example selects main only. A separate qualification selects the test compilation and finds a relationship from PriceTest.kt. Neither inspection executes tests.
Use the same workflow on saved Kotlin edits
clew change inspect --repo <repo> --target-ref <branch> \
--language kotlin --profile kotlin-jvm-gradle-analysis \
--compilation :/main --working-tree --base HEAD
clew change graph --comparison <returned-id>
clew change render --comparison <returned-id> --output <new-report.html>
clew change check-freshness --comparison <returned-id>
clew change source --comparison <returned-id> \
--node <returned-node-id> --side after
clew change forget --comparison <returned-id>Use repository discovery for the exact profile and compilation of your project. Add test compilations explicitly. For Rust, use the discovered syntax profile and Cargo compilation; the report does not invent compiler-resolved callers.
Three separate questions
- Are the retained claims readable and valid? Source, fact and comparison digests bind the evidence.
- Does the snapshot still match this checkout? Further saved edits produce
LIVE_CHANGED. Create a new comparison when current edits are needed. - Is the selected scope complete? Compiler failures, unresolved targets, test scope and truncation remain explicit. Valid evidence and a fresh checkout do not remove those limitations.
The local report has no background watcher, network dependencies or implicit publication. Repeated rendering reads retained evidence without compiling the project. Exact source windows are bounded; follow nextOffset when needed.
Inspect the method behind the example
The retained report comes from an earlier qualification fixture. Its embedded source remains readable offline; its comparison ID is no longer live. Historical fixture and repository measurements are available in the evidence archive.