Add scanner fixture for browser submit actions

[rossbuckley1990-hash]

Summary

Add a small scanner fixture that demonstrates a candidate browser/computer-use submit action.

Actenon’s scanner should help identify places where an AI agent, browser agent, or computer-use workflow may be able to submit a form, update settings, upload data, confirm a purchase, or trigger another consequential browser-side effect.

Why this matters

Browser agents are one of the clearest execution-gap surfaces. An agent can appear to be “just navigating” while actually submitting a real-world action.

A fixture makes this easier to test, document, and explain.

Suggested scope

Add a small intentionally unsafe example fixture under an appropriate test/examples location, such as:

• browser form submit
• settings update
• export CSV
• account deletion confirmation
• purchase confirmation

The fixture should be synthetic and safe. It must not contact any external service.

Acceptance criteria

• A new scanner fixture exists for a browser submit-style action.
• The scanner identifies it as a candidate consequential action path.
• The output remains advisory and uses consequence-class language.
• Tests are added or updated.
• No vulnerability claim is made.