dopplerlisted

# Doppler (env-style secrets) Doppler is the default store for every env-style secret — API keys, tokens, passwords, connection strings — in place of a plaintext `.env`. One source of truth, synced across the user's Windows and macOS machines, with nothing secret committed. The account's workplace is `sava`. ## Context - Doppler CLI: !`command -v doppler >/dev/null 2>&1 && echo INSTALLED || echo MISSING` - Existing projects: !`doppler projects --json 2>&1 | tr ',' '\n' | grep -o '"name":"[^"]*"' || echo UNAVAILABLE` - Configs in this repo's project: !`doppler configs --json 2>&1 | tr ',' '\n' | grep -o '"name":"[^"]*"' || echo "UNBOUND — list with doppler configs -p <shard>"` - This repo's doppler.yaml: !`test -f doppler.yaml && cat doppler.yaml || echo NONE` - This directory's binding: !`doppler configure get project --plain 2>/dev/null | grep . || echo UNBOUND` ## 1. Resolve project and config — never guess them Read the coordinates off **Existing projects** and **Configs in this repo's project** (Context) — a coordinate is a project *and* a config, and under the shard rule the config carries the app's identity: - The workplace name `sava` is **not** a project. Never `-p sava`. - Doppler's sample project `example-project` is not one of the user's. Never write to it. - **A new app gets a config, not a project.** The workplace is capped at **10 projects**, all ten are in use, and `doppler projects create` now fails with `Your workplace has reached its limit of 10 pro