chore: tidy docs and helm comments

docs/runbooks/staging-environment.md

@@ -35,7 +35,7 @@ render references **47** keys across three ExternalSecrets — **41 staging-pref
   - **Deliberately NOT shared — the prod GitHub PAT.** `commonly-github-pat` has
     write power over prod repos, and staging auto-deploys every merge (the reckless
     lane), so `githubPat.enabled: false` in values-staging omits the `GITHUB_PAT`
-    ref from the staging render entirely (Cofounder's ruling — the same principle
+    ref from the staging render entirely (the same principle
     that keeps atlasAdmin off staging). The backend reads GITHUB_PAT lazily and
     degrades (GitHub routes report not-configured) rather than crashing. Staging
     agents that ever need git get a separate fine-grained PAT on a throwaway repo,

k8s/helm/commonly/templates/configmaps/litellm-config.yaml

@@ -47,9 +47,9 @@ data:
       # V4.1 for compatibility. The group name carries the build so a key
       # scoped to it says what it buys; re-check the changelog before trusting
       # the name after DeepSeek's next Flash update. Used by the dsh writer
-      # seats (D50), through their own budget-capped virtual key.
+      # seats, through their own budget-capped virtual key.
       #
-      # Budget (Sam, D50: the DeepSeek writers are budget-capped). Two caps:
+      # Budget (the DeepSeek writers are budget-capped). Two caps:
       #   1. This deployment: $200 per month across EVERY caller of the group.
       #      Over it, LiteLLM answers 429 "crossed budget" and does not reroute
       #      (there is no fallback for this group). Spend for this cap is
@@ -59,8 +59,8 @@ data:
       #   2. The writers' virtual key: models=[deepseek-flash-1017],
       #      max_budget 200, budget_duration 30d. Stored in LiteLLM's Postgres,
       #      so it survives restarts and is the auditable record
-      #      (/key/info). Minted after this ships; the file lives 0600 on the
-      #      fleet host, never in the repo.
+      #      (/key/info). Minted after this ships; the key lives 0600 with
+      #      its operator, never in the repo.
       - model_name: deepseek-flash-1017
         litellm_params:
           model: deepseek/deepseek-flash
@@ -113,7 +113,7 @@ data:
       # all fallback chains below. If the model is reinstated, restore it as a
       # paired entry alongside nemotron above.
 
-      # --- D111 (2026-10-27): GPT/Codex access revoked. Every chatgpt/* alias below is
+      # --- 2026-10-27: GPT/Codex access revoked. Every chatgpt/* alias below is
       # repointed to the deepseek/deepseek-v4-flash backend so callers keep their
       # model_name but get DeepSeek. The ChatGPT OAuth path (chatgpt/responses/*, the
       # codex-auth-rotator sidecar, auth.json) is dormant until GPT access returns;
@@ -194,7 +194,7 @@ data:
           model: openai/gpt-image-1
           api_key: os.environ/OPENAI_API_KEY
 
-      # Direct Anthropic routes removed under D76. Claude on hosted runtimes
+      # Direct Anthropic routes removed. Claude on hosted runtimes
       # awaits OpenRouter routing; BYO Claude Code remains independent.
 
     router_settings:
@@ -203,7 +203,7 @@ data:
       # (writes /chatgpt-auth/rotate-now → sidecar polls and swaps auth.json).
       routing_strategy: least-busy
       enable_pre_call_checks: true
-      # Fallback chain. Under D111 (2026-10-27) the gpt-5.4*/openai-codex/* Codex
+      # Fallback chain. Since 2026-10-27 the gpt-5.4*/openai-codex/* Codex
       # entries that used to fall through to nemotron here were removed — those
       # aliases now point straight at deepseek-v4-flash, and nemotron is dead (the
       # gateway it served is parked; OpenRouter keys expired 2026-10-25). The only
@@ -221,7 +221,7 @@ data:
       # callers" alert fires (docs/runbooks/alerting.md#litellm-failing). There is
       # no nemotron or Codex tier behind it any more.
       fallbacks:
-        # D111 (2026-10-27): gpt-5.4*/openai-codex/*/codex-cli gpt->nemotron fallbacks
+        # 2026-10-27: gpt-5.4*/openai-codex/*/codex-cli gpt->nemotron fallbacks
         # removed — those aliases now point straight at deepseek-v4-flash (primary), and
         # nemotron itself is dead (OpenRouter keys expired 2026-10-25).
         # Dead routes fall back to deepseek-v4-flash (2026-10-15). Probing every
@@ -243,7 +243,7 @@ data:
         - {"nvidia/nemotron-3-super-120b-a12b:free": ["deepseek-v4-flash"]}
       # One retry on rate-limit with a deliberate 1s delay. This retry is a global
       # router setting and still applies to every deployment. The Codex auth.json
-      # rotation it was originally written for is dormant post-D111 (no chatgpt/*
+      # rotation it was originally written for is dormant since 2026-10-27 (no chatgpt/*
       # route consumes the rotator now); for the repointed aliases a 429 simply
       # retries the same deepseek-v4-flash deployment after 1s, then fails fast.
       #

k8s/helm/commonly/values-dev.yaml

@@ -8,7 +8,7 @@ global:
 errorTracking:
   enabled: true
 
-# commonly-dev-e2b-api-key has one enabled version (Cofounder, 2026-10-15).
+# commonly-dev-e2b-api-key has one enabled version (2026-10-15).
 # Tools stay opt-in per install, so this offers code runs to nobody until an
 # agent declares commonly_run_code.
 hostedSandbox:
@@ -220,7 +220,7 @@ externalSecrets:
 
 agents:
   clawdbot:
-    # PARKED 2026-08-20 (Sam) — the moltbot tier is retiring in favour of
+    # PARKED 2026-08-20 — the moltbot tier is retiring in favour of
     # pi/OpenCode wrapper adapters (ADR-021/ADR-023, #1050). Its credential
     # stack had been dead since 2026-07-02 — both cluster codex tokens expired,
     # OpenRouter 401 "User not found" — and nobody noticed for seven weeks,
@@ -289,7 +289,7 @@ agents:
         adapter: codex
         storage: 1Gi
         tokenSecret: cloud-codex-cody-token
-        # Parked 2026-08-12 (Sam: the working fleet is the Sharpen pod).
+        # Parked 2026-08-12.
         # Identity, PVC, and token secret stay; flip to 1 to revive.
         replicas: 0
 
@@ -439,20 +439,18 @@ hostedMcp:
   hiddenEntries:
     # Client secrets exist, but Workspace MCP enrollment is still off.
     - google-calendar
-    # Not walked end to end on staging before the 10-23 deploy (Cofounder plan B: unwalked ships hidden).
+    # Not walked end to end on staging before the 10-23 deploy; unwalked entries ship hidden.
     # Remove each line once its staging walk passes.
     - atlassian
     - sentry
-    # Added by #2429 (deploy 4). Hidden until each is walked end to end (Cofounder 10-23).
+    # Added by #2429. Hidden until each is walked end to end.
     - notion
     - gitlab
     - supabase
     # The 10-27 prod walk failed before Airtable's consent screen ("invalid client_id
     # or mismatched redirect_uri"). Hidden until TASK-318 lands and a walk passes.
     - airtable
-  # Mongo User _id(s) permitted to walk each hidden hosted-MCP entry (#2649, TASK-485).
-  # lily-shen is the designated walk user (keeps the walk off Sam's account, Cofounder 10-24).
-  # Sentry and Atlassian stay hidden for every other account (Atlassian added for its walk, D153).
+  # Mongo User _id(s) permitted to walk each hidden hosted-MCP entry (#2649).
   hiddenEntryUserAllowlist:
     atlassian:
       - "6a47891ee025ce2e0ca1d30b"

k8s/helm/commonly/values-staging.yaml

@@ -49,7 +49,7 @@ email:
 
 # No prod GitHub PAT on staging. The shared commonly-github-pat has write power over
 # prod repos, and staging auto-deploys every merge (the reckless lane), so the
-# api-keys render must not reference it (Cofounder's ruling, same principle as
+# api-keys render must not reference it (the same principle as
 # keeping atlasAdmin off staging). The backend uses GitHub App installation tokens
 # and does not read this key. If staging agents ever need git, that is a
 # separate fine-grained PAT on a throwaway repo, post-11/1.