Repository navigation
Version 0.3.8 helps you change code without losing sight of why it was written. Every file in a long-running project carries promises: what it was meant to do, what someone agreed it would handle and which tests were meant to prove it. Those promises usually sit in old plans that nobody rereads. EWAI now brings them back at the moment they matter.
Ask a file what it's responsible for. Before you change a file, run ewai index behaviour <path> or simply ask your assistant. You'll see the outcomes earlier work linked to it, the acceptance criteria behind them, and the tests and evidence recorded when they were delivered, with the most relevant first.
Know when old evidence has gone stale. EWAI checks each piece of recorded evidence against what's on disk now and tells you if it's changed. It's honest about what it can't see, too. Finding nothing doesn't mean nothing is affected, and EWAI won't claim old work is still correct. That judgement stays with you.
Your assistant remembers too. When you plan, build or review, EWAI adds a short reminder of earlier outcomes linked to the files you're about to touch, so your assistant can recheck them without being asked. It's kept brief, so the work in front of you still comes first.
Confirm what you actually reviewed. Impact assessments now show the earlier outcomes worth rechecking. If anything changes between your review and your confirmation, EWAI asks you to take another look rather than recording a decision on evidence you never saw. If you confirm assessments through the API, include the previewId from the preview.