Aura stops overstating what it knows

• Aura had been telling you things that were not true, and most of them had passing tests behind them. A run that stopped was reported as work that finished. A seal, a green verdict and a commit added up on screen to “it works”, which is a claim none of the three makes on its own. The reason you wrote down for a change was quietly replaced by Aura’s guess at it. This release is the sweep through all of it: every surface now says only what it actually knows, and names what it does not.
• Recovery no longer costs you what is open. Four different paths reset your working tree, and three of them presented themselves as the safe option while doing it — taking a save point printed a reference that led nowhere and called your work preserved; restoring reset the tree and then told you uncommitted work had been destroyed; a failed orchestration wave reset your own checkout with the error thrown away; and the rollback webhook did the same thing over the network with nobody at the keyboard. All four now anchor your work somewhere recoverable first, and refuse to reset at all if they cannot.
• Asking for the reason stopped rejecting the reason. Aura asks you to explain a change before it is committed, and then judged whether your explanation belonged to that change by looking for the function’s name inside your message. So a message that was just “monthly_total” passed, and “round the total to cents so invoices stop disagreeing with the bank” — the exact sentence Aura’s own guidance asks you to write — was refused, and you were told in green to go and write a worse one. An explanation now belongs to a change if it names something that changed, names a file that changed, or was recorded against the files you staged.
• A session says whose work it is. Three different voices had been flattened into one, so you could not tell your own words from an agent’s, and an agent that had stalled was described as idle. A session also stops naming itself after whatever command it happened to run, “Resume in app” opens the app, and a page about last Tuesday stops running its buttons against today.
• Save points open. Clicking one ran a command that has never existed, so the panel filled with a usage dump instead of your work. They are read from disk now, described in plain words, and the reason you gave is joined back on — and what Aura learns on its own carries where it came from, whether it ever left this machine, and can be taken back from your team.