Whether this twin's answers match a captured real vendor response.
REST GET /gmail/v1/users/{userId}/profile Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/messages Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/messages/{id} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST POST /gmail/v1/users/{userId}/messages/send Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /upload/gmail/v1/users/{userId}/messages/send (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /upload/gmail/v1/users/{userId}/messages (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/import Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /upload/gmail/v1/users/{userId}/messages/import (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/{id}/modify Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/batchModify Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/batchDelete Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/{id}/trash Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/messages/{id}/untrash Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST DELETE /gmail/v1/users/{userId}/messages/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/messages/{messageId}/attachments/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/drafts Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/drafts/{id} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST POST /gmail/v1/users/{userId}/drafts Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /upload/gmail/v1/users/{userId}/drafts (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST PUT /gmail/v1/users/{userId}/drafts/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST PUT /upload/gmail/v1/users/{userId}/drafts/{id} (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/drafts/send Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /upload/gmail/v1/users/{userId}/drafts/send (simple multipart) Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST DELETE /gmail/v1/users/{userId}/drafts/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/threads Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/threads/{id} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST POST /gmail/v1/users/{userId}/threads/{id}/modify Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/threads/{id}/trash Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/threads/{id}/untrash Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST DELETE /gmail/v1/users/{userId}/threads/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/labels Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/labels/{id} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST POST /gmail/v1/users/{userId}/labels Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST PUT /gmail/v1/users/{userId}/labels/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST PATCH /gmail/v1/users/{userId}/labels/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST DELETE /gmail/v1/users/{userId}/labels/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/history Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/settings/filters Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/settings/filters/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST POST /gmail/v1/users/{userId}/settings/filters Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST DELETE /gmail/v1/users/{userId}/settings/filters/{id} Not checked
this row is showing the completion fallback, not a measurement gap: the REST write round trip (sandboxes/gmail/rest-writes.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
REST GET /gmail/v1/users/{userId}/settings/forwardingAddresses Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/settings/forwardingAddresses/{forwardingEmail} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/settings/sendAs Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
REST GET /gmail/v1/users/{userId}/settings/sendAs/{sendAsEmail} Not checked
nothing has ever compared this surface against real Gmail. It IS one of the 14 surfaces in the L1 upstream read lane, so a capture would verify it — but twin-gmail's golden is captured BY HAND and never by CI (F-1101, 2026-08-09: no FIDELITY_GMAIL_TOKEN repo secret exists or will), and nobody has run one: a person exports the token in a shell and runs bun run tools/fidelity-watch/capture-gmail-upstream-golden.ts against a hand-seeded throwaway mailbox.
See tools/fidelity-watch/SECRETS.md § Gmail.
MCP create_draft Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP list_drafts Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/gmail/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP get_thread Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/gmail/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP get_message Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/gmail/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP search_threads Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/gmail/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP label_thread Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP unlabel_thread Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP apply_sensitive_thread_label Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP list_labels Not checked
this row is showing the completion fallback, not a measurement gap: the MCP read leg (sandboxes/gmail/mcp-reads.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP label_message Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP unlabel_message Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP apply_sensitive_message_label Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.
MCP create_label Not checked
this row is showing the completion fallback, not a measurement gap: the MCP write round trip (sandboxes/gmail/level2.ts) covers this surface, needs no credential, and runs on every scheduled run. Seeing this text means that leg did not reach it — the capture did not run, its fixture is not committed, or the sequence stopped early at an earlier step.
Run tsx tools/fidelity-watch/capture-gmail-m1.ts and commit every fixture it writes. It says nothing about parity with real Gmail, which only the L1 upstream lane can answer.