Send Yourself a Gmail

GH#896 — single approval. Removed `gate: true` from the `gmail_compose` step so the draft runs automatically (reversible, nothing sent), and kept `gate: true` only on `gmail_send` — the one irreversible act, with the send-time refuse-on-drift check. The run now asks for exactly one approval (the send) instead of two. Prose updated to describe the single-approval flow. No change to the steps' `to`/`subject`/`body` facts the drift check verifies.

GH#883 — fix the input declaration so the app prompts for the email address. v0.0.1 relied on `{{input.email}}` + a markdown Inputs table, but the app collects run-inputs only from a structured `inputs:` MAP in the workflow frontmatter (a YAML sequence or a docs table is not read) — so the run prompted for nothing and `{{input.email}}` resolved empty. Added the `inputs.email` map (label/description/required/type/example) so the run stage renders the email field and blocks start until it is filled.

GH#883 — initial release. A browser-connector showcase: draft and send a test email to yourself, each of the two steps (`gmail_compose`, `gmail_send`) behind the real approval gate. Both steps pass the same `to`/`subject`/`body`, so the send's refuse-on-drift check has an approved baseline to verify the live compose against. No skills, prompts, services, or LLM — the only steps are the gated MCP browser actions served by the skrptiq-browser connector.