@topy-ai/maggie 0.7.40 → 0.7.41

package/references/browser-inspection.md

@@ -27,6 +27,27 @@ interaction states and triggers
 responsive differences
 ```
 
+Behavioral checks may be declared instead of hidden in a bespoke script. The
+manifest is safe to commit because input values are not copied into evidence:
+
+```json
+{
+  "schemaVersion": "maggie-browser-interactions.v1",
+  "steps": [
+    {"id": "open", "action": "click", "selector": "[data-menu]"},
+    {"id": "visible", "action": "assert-visible", "selector": "[data-drawer]"},
+    {"id": "styles", "action": "assert-style", "selector": "[data-drawer]", "property": "display", "value": "block"},
+    {"id": "privacy", "action": "assert-no-request", "origin": "third-party.example"}
+  ]
+}
+```
+
+Run it with `maggie browser-audit ... --interactions .maggie/interactions.json`.
+Supported actions cover click, fill, type, select, press, wait, visibility and
+state assertions, computed-style assertions, and new-request assertions. The
+browser adapter owns the session and the audit records only step IDs and
+redacted outcomes.
+
 If a target requires login, a bot challenge, a consent interaction, or a
 private browser profile, stop at that boundary and ask the user to provide
 authorized access. Do not bypass access controls or record cookies in project