Browser Test

Combines browser-record and browser-replay so every UI test produces a replayable RVF artifact instead of disappearing when the run finishes. You open a browser, click and fill forms, wait for elements, assert on text or values, and take screenshots. All of that gets stored in a session container you can diff against later or replay in CI. The honest benefit is you're not re-authoring tests when something breaks, you're just re-running the stored session. It wires in aidefence_is_safe to quarantine injection attempts before they hit findings.md, and it indexes selectors by embedding similarity so future tests can locate elements without brittle XPath. If you're doing any kind of regression testing on web UIs, the replayability alone makes it worth trying.