For Jon: start Wave 1: create each new key below on its provider, save it to a file, and hand the file to an agent to set.
Why: Until 2026-10-03 the secrets sat in this repo encrypted with SOPS and age, and that ciphertext and the age key are still in git history. Every value counts as exposed until it's rotated.
Rule for every key: you create the new one and save it to a file; an agent sets it, deploys and checks; only then you revoke the old one. One key at a time.
Steps:- Wave 1 (low risk, start now). Create, hand over, then revoke the old one once the agent says the check passed:
- GH_TOKEN: github.com → Settings → Developer settings → Fine-grained tokens, same scopes.
- EXPO_TOKEN: expo.dev → Account settings → Access tokens.