That matches my experience too - tests and plans are still the backbone. What I keep running into is the step before reading tests or code: when a change is la

That matches my experience too - tests and plans are still the backbone. What I keep running into is the step before reading tests or code: when a change is large or mechanical, I’m mostly trying to answer "did behavior or API actually change, or is this mostly reshaping?" so I know how deep to go etc. Agree we’re all still experimenting here.