2. A reasonable near-term goal could be to make changes in one file propagate across the code base, so it remains consistent. This requires analyzing the call graph, which is something Sourcegraph already knows how to do. The next step could be to execute multi-file refactors without specifying which files to modify; e.g., "add support for WebAuthn using our auth provider's SDK".
2. Your "reasonable near-term goal" is right in line with what we are thinking. Basically, "auto-edits" is f(edit that meets deterministic trigger criteria) --> multi-file diff. Here are some examples we have in mind; any others you had in mind?
update a type signature --> ripple that change across to all call sites/value literals (kinda like symbolic rename does today, but for more than just the name)
rename something --> update the docs
change code with a comment nearby --> update the comment if it's now invalid
update a func impl --> propose a new test case