jakevin
6b3dffd398
* feat(gmail): add browser-backed adapter * docs(gmail): document adapter commands * refactor(gmail): remove unsupported write surface * chore(gmail): split author workflow into dedicated PR --------- Co-authored-by: OpenCLI-sol <opencli-sol@users.noreply.github.com>
1.6 KiB
schema_version, last_verified, source
| schema_version | last_verified | source |
|---|---|---|
| 1.1 | 2026-08-25 | global |
Site-specific pitfalls
pitfall:search_does_not_submit_with_synthetic_events
trigger: an agent fills Gmail search by assigning .value and dispatching synthetic Enter
symptom: input text changes but URL/results stay on the previous query
workaround: use opencli gmail search; browser fallback must use native text insertion plus raw native Enter
verified_at: 2026-08-25
pitfall:cached_thread_has_no_fresh_response
trigger: an agent opens a recently loaded thread expecting a new network response
symptom: no /fd capture although the thread body is visibly rendered
workaround: use opencli gmail thread; fallback scopes [data-message-id] and .a3s to the rendered thread
verified_at: 2026-08-25
pitfall:private_post_is_not_a_write_signal
trigger: an agent classifies Gmail requests only by HTTP method
symptom: read-only /bv and /fd POSTs are mistaken for writes, or private write POSTs are replayed
workaround: classify by user-visible action and observed effect; never replay private Gmail writes
verified_at: 2026-08-25
pitfall:private_sync_writes_are_not_replayable_contracts
trigger: an agent tries to turn one captured /sync send or delete request into a production command
symptom: replay depends on opaque positional state or a page-generated anti-abuse token and may fail, duplicate, or mutate the wrong message
workaround: do not fabricate or replay Gmail private writes; use Google OAuth with Gmail scopes for supported API-backed write commands
verified_at: 2026-08-25