docs(mail): record Gmail Radar runtime state #738

Closed
codex wants to merge 1 commit from codex/gmail-radar-runtime-docs into main
Collaborator

Summary

  • Passes Gmail OAuth env placeholders through to gmail-triage-mcp.
  • Records that Gmail Radar is live for p_durlej_me in metadata/header-only mode.
  • Updates the mail loop runbook maintenance checklist with the current OAuth env mapping.

Safety

  • No secret values are added.
  • No mailbox bodies, snippets, attachments, auth headers, or tokens are included.
  • Gmail Radar remains documented as metadata/header-only.
  • Label/archive/write behavior remains explicitly unproven and out of scope.

Validation

  • PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json passed.

Spec sources read

  • compose/apps/compose.yaml — scoped runtime env wiring for gmail-triage-mcp.
  • runbooks/mail-loops.md — operator-facing Gmail/Missive/Fastmail runtime map.

Non-goals

  • No runtime deploy or service restart.
  • No Gmail scope expansion.
  • No secret rotation or migration.
  • No mailbox content access.
## Summary - Passes Gmail OAuth env placeholders through to `gmail-triage-mcp`. - Records that Gmail Radar is live for `p_durlej_me` in metadata/header-only mode. - Updates the mail loop runbook maintenance checklist with the current OAuth env mapping. ## Safety - No secret values are added. - No mailbox bodies, snippets, attachments, auth headers, or tokens are included. - Gmail Radar remains documented as metadata/header-only. - Label/archive/write behavior remains explicitly unproven and out of scope. ## Validation - `PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json` passed. ## Spec sources read - `compose/apps/compose.yaml` — scoped runtime env wiring for `gmail-triage-mcp`. - `runbooks/mail-loops.md` — operator-facing Gmail/Missive/Fastmail runtime map. ## Non-goals - No runtime deploy or service restart. - No Gmail scope expansion. - No secret rotation or migration. - No mailbox content access.
docs(mail): record Gmail Radar runtime state
All checks were successful
canary-required / collect-diff (pull_request) Successful in 5s
platformctl plan / auto-apply scope (pull_request) Successful in 22s
canary-required / canary (pull_request) Has been skipped
base-is-main / guard (pull_request) Successful in 1s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 19s
patchwarden-pr-sanity / sanity (pull_request) Successful in 1m42s
a56742c51e
First-time contributor

Patchwarden PR sanity

  • Status: eligible_sanity_clean
  • PR: 738
  • Commit: a56742c51ea2caabf004bc4d6f2723f9c0dd5500
  • Security-sensitive label: present
  • Authority: advisory model review plus deterministic blockers only
  • 3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

global-glm / glm-5.1:cloud

  • Status: ok

  • Verdict: OK

  • medium OAuth client secret passed to container runtime

    • Evidence: compose/apps/compose.yaml line +1329 adds GMAIL_GOOGLE_OAUTH_CLIENT_SECRET: ${GMAIL_GOOGLE_OAUTH_CLIENT_SECRET:-} alongside CLIENT_ID and REFRESH_TOKEN
    • Next: Confirm that Infisical or equivalent vault injects this at runtime and that the container image does not log env vars on startup. The pattern is consistent with existing ACCESS_TOKEN vars, but client_secret is a higher-sensitivity credential than access tokens.

global-deepseek / deepseek-v4-pro:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

redteam / kimi-k2.6:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

Policy notes

  • GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
  • Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
  • Auto-merge is not enabled here.
<!-- patchwarden-pr-sanity:pdurlej/platform:PR-738 --> # Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `738` - Commit: `a56742c51ea2caabf004bc4d6f2723f9c0dd5500` - Security-sensitive label: `present` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - **`medium`** OAuth client secret passed to container runtime - Evidence: `compose/apps/compose.yaml line +1329 adds `GMAIL_GOOGLE_OAUTH_CLIENT_SECRET: ${GMAIL_GOOGLE_OAUTH_CLIENT_SECRET:-}` alongside CLIENT_ID and REFRESH_TOKEN` - Next: Confirm that Infisical or equivalent vault injects this at runtime and that the container image does not log env vars on startup. The pattern is consistent with existing ACCESS_TOKEN vars, but client_secret is a higher-sensitivity credential than access tokens. ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.
Owner

PR-zero queue collapse: closing this parked security-sensitive Gmail Radar/runtime-state PR without merge. It is secret-adjacent and stale relative to the current queue; if still needed, reopen as a fresh, narrow security-sensitive PR with current runtime evidence and explicit non-secret scope. No runtime, OAuth, mailbox, or secret mutation was performed.

PR-zero queue collapse: closing this parked security-sensitive Gmail Radar/runtime-state PR without merge. It is secret-adjacent and stale relative to the current queue; if still needed, reopen as a fresh, narrow security-sensitive PR with current runtime evidence and explicit non-secret scope. No runtime, OAuth, mailbox, or secret mutation was performed.
pdurlej closed this pull request 2026-06-17 23:17:20 +02:00
All checks were successful
canary-required / collect-diff (pull_request) Successful in 5s
platformctl plan / auto-apply scope (pull_request) Successful in 22s
canary-required / canary (pull_request) Has been skipped
base-is-main / guard (pull_request) Successful in 1s
Required
Details
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 19s
patchwarden-pr-sanity / sanity (pull_request) Successful in 1m42s
Required
Details

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!738
No description provided.