Merge pull request #134 from codeflash-ai/live-connector-e2e

Add live connector e2e coverage

Author: mohammedahmed18

.github/workflows/connector-live-e2e.yml

@@ -8,6 +8,6 @@ enabled = true
 
 [vars]
 LOCALITY_TOKEN_MODE = "handle"
-LOCALITY_NOTION_REDIRECT_URIS = "http://localhost:8757/oauth/notion/callback,http://127.0.0.1:8757/oauth/notion/callback"
+LOCALITY_NOTION_REDIRECT_URIS = "http://localhost:8757/oauth/notion/callback,http://127.0.0.1:8757/oauth/notion/callback,https://api.dev.locality.dev/v1/oauth/notion/callback"
 LOCALITY_GOOGLE_DOCS_REDIRECT_URIS = "http://localhost:8757/oauth/google-docs/callback,http://127.0.0.1:8757/oauth/google-docs/callback"
 LOCALITY_GMAIL_REDIRECT_URIS = "http://localhost:8757/oauth/gmail/callback,http://127.0.0.1:8757/oauth/gmail/callback"

apps/oauth-service/wrangler.toml

@@ -172,6 +172,32 @@ Locality removes that exact File Provider item and signals both the `draft/` and
 `sent/` containers. Remote or unconfirmed item deletion remains blocked. This
 does not require the user to run `loc pull` or refresh Finder.
 
+## Live E2E
+
+`tests/live_gmail_vfs_roundtrip.sh` exercises the live Gmail API, CLI
+mount/pull/diff/push, daemon, and Linux FUSE projection. It creates an unsent
+Gmail draft through the mounted `draft/` folder, verifies the draft projection,
+and deletes the Gmail draft through Gmail API cleanup.
+
+Use a stored `connection:gmail-live` credential and a recipient address:
+
+```bash
+secret_ref='connection:gmail-live'
+secret_hex="$(printf '%s' "$secret_ref" | od -An -tx1 -v | tr -d ' \n')"
+export LOCALITY_GMAIL_LIVE_CREDENTIAL_JSON="$(cat "$HOME/.loc/credentials/$secret_hex")"
+export LOCALITY_GMAIL_LIVE_TO_EMAIL='you@example.com'
+```
+
+Use the full stored credential JSON. The live harness requires
+`access_token`, `oauth_broker_url`, `refresh_token_handle`, and numeric
+`expires_at` so it can exercise broker refresh when the token expires.
+
+Run the gated live check:
+
+```bash
+LOCALITY_LIVE_GMAIL_VFS=1 tests/live_gmail_vfs_roundtrip.sh
+```
+
 ## Useful Commands
 
 Connect with the local broker:

docs/e2e-behavior-coverage.md

@@ -129,6 +129,32 @@ Agenda:
 with `sendUpdates=all`. Setting `google_calendar.conference: google_meet`
 requests a Google Meet link with `conferenceDataVersion=1`.
 
+## Live E2E
+
+`tests/live_google_calendar_vfs_roundtrip.sh` exercises the live Google
+Calendar API, CLI mount/pull/diff/push path, daemon, and Linux FUSE projection.
+It creates a scratch draft event through the mounted `draft/` directory,
+verifies the pushed event appears under `events/`, and deletes the event through
+Google Calendar API cleanup.
+
+To reuse a stored `connection:google-calendar-live` credential:
+
+```bash
+secret_ref='connection:google-calendar-live'
+secret_hex="$(printf '%s' "$secret_ref" | od -An -tx1 -v | tr -d ' \n')"
+export LOCALITY_GOOGLE_CALENDAR_LIVE_CREDENTIAL_JSON="$(cat "$HOME/.loc/credentials/$secret_hex")"
+```
+
+Use the full stored credential JSON. The live harness requires
+`access_token`, `oauth_broker_url`, `refresh_token_handle`, and numeric
+`expires_at` so it can exercise broker refresh when the token expires.
+
+Run the gated live test:
+
+```bash
+LOCALITY_LIVE_GOOGLE_CALENDAR_VFS=1 tests/live_google_calendar_vfs_roundtrip.sh
+```
+
 ## Useful Commands
 
 Connect with the local broker:

docs/gmail-connector.md

@@ -118,6 +118,36 @@ Live testing found and fixed several integration issues:
 - The OAuth broker project must have both Google Docs API and Google Drive API
   enabled.
 
+## Live E2E
+
+`tests/live_google_docs_vfs_roundtrip.sh` exercises the live Google Docs API,
+CLI mount/pull/diff/push paths, `localityd`, and the Linux FUSE projection. It
+uses isolated Locality state and a temporary shared root, creates one generated
+Google Docs page through the mounted filesystem, verifies the create marker
+survives a pull after push, edits the created document through mounted
+`page.md`, verifies the edit marker survives another pull, and trashes the
+created Drive file during cleanup.
+
+Set the required environment from a stored `connection:google-docs-live`
+credential and choose a scratch workspace folder:
+
+```bash
+secret_ref='connection:google-docs-live'
+secret_hex="$(printf '%s' "$secret_ref" | od -An -tx1 -v | tr -d ' \n')"
+export LOCALITY_GOOGLE_DOCS_LIVE_CREDENTIAL_JSON="$(cat "$HOME/.loc/credentials/$secret_hex")"
+export LOCALITY_GOOGLE_DOCS_LIVE_WORKSPACE_FOLDER='Locality Live E2E'
+```
+
+Use the full stored credential JSON. The live harness requires
+`access_token`, `oauth_broker_url`, `refresh_token_handle`, and numeric
+`expires_at` so it can exercise broker refresh when the token expires.
+
+Run the gated test explicitly:
+
+```bash
+LOCALITY_LIVE_GOOGLE_DOCS_VFS=1 tests/live_google_docs_vfs_roundtrip.sh
+```
+
 ## Useful Commands
 
 Connect with the local broker:

docs/google-calendar-connector.md

@@ -104,6 +104,27 @@ Sidecar remote ids use `linear-context:<issue_id>:comments`,
 `linear-context:<issue_id>:history`. Apply and concurrency checks reject these
 ids as read-only before any `issueUpdate` mutation is attempted.
 
+## Live E2E
+
+`tests/live_linear_vfs_roundtrip.sh` exercises the live Linear API, CLI
+mount/pull/diff/push flow, daemon, and Linux FUSE projection. It edits one
+existing scratch issue body through the mounted `page.md`, pushes the marker to
+Linear, pulls it back, and restores the original issue content before exiting.
+
+Set the API key and scratch issue UUID before running it:
+
+```bash
+export LINEAR_API_KEY='lin_api_...'
+export LOCALITY_LINEAR_LIVE_ISSUE_ID='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
+```
+
+The issue should be scratch content because the test temporarily appends a
+unique marker to the issue body and then restores the saved original content.
+
+```bash
+LOCALITY_LIVE_LINEAR_VFS=1 tests/live_linear_vfs_roundtrip.sh
+```
+
 ## Attachments
 
 Linear issue attachments are external links. During hydration of

docs/google-docs-connector.md

@@ -88,6 +88,37 @@ deletes, push writes, undo writes, and autosave writes under Slack mounts.
 V1 does not post messages, subscribe to Slack events, or store arbitrary Slack
 search results.
 
+## Live E2E
+
+`tests/live_slack_vfs_read.sh` exercises the live Slack API, CLI
+mount/pull/status, daemon, and Linux FUSE projection by reading a known
+conversation's `recent.md` and verifying Slack remains read-only through the
+mounted filesystem and product push validation. The live script refuses
+`public_channel` mounts because Slack public-channel reads can auto-join
+channels; use a private channel, DM, or group DM where the app is already
+present.
+
+To reuse a stored `connection:slack-live` credential in isolated test state:
+
+```bash
+secret_ref='connection:slack-live'
+secret_hex="$(printf '%s' "$secret_ref" | od -An -tx1 -v | tr -d ' \n')"
+export LOCALITY_SLACK_LIVE_CREDENTIAL_JSON="$(cat "$HOME/.loc/credentials/$secret_hex")"
+export LOCALITY_SLACK_LIVE_CONVERSATION_ID='G0123456789'
+```
+
+Use the full stored credential JSON. The live harness requires
+`access_token`, `oauth_broker_url`, `refresh_token_handle`, and numeric
+`expires_at` so it can exercise broker refresh when the token expires.
+
+Set `LOCALITY_SLACK_LIVE_TYPES` when the target conversation is not covered by
+the default `private_channel,im,mpim` type set. Do not set `public_channel` for
+this live test.
+
+```bash
+LOCALITY_LIVE_SLACK_VFS=1 tests/live_slack_vfs_read.sh
+```
+
 ## Useful commands
 
 ```bash