temps-platform-setup

# Temps Platform Setup Help configure a Temps installation without crossing the user's infrastructure or credential boundaries. ## Safety contract Apply these rules to every workflow: 1. **Never install or upgrade Temps automatically.** Do not download or execute remote scripts, package-manager installers, release archives, or code from a repository. Do not suggest piping network output into a shell. 2. **Use only an already-installed `temps` binary.** Do not use `npx`, `bunx`, `npm exec`, or another on-demand package runner. For CLI installation and exact-version verification, follow the adjacent [temps-cli skill](../temps-cli/SKILL.md). 3. **Do not handle secrets.** Never ask the user to paste, display, export, or read API keys, passwords, provider tokens, private keys, database URLs, or setup-result files. Never inspect credential storage. 4. **Keep secret entry human-controlled.** Direct the user to a hidden prompt, the Temps dashboard, or their secret manager. When a command requires a secret-bearing flag, provide only the flag name and have the user run it manually; do not construct the command. 5. **Confirm the target.** Before any state change, identify the server, organization, project, and CLI context. Stop if the target is ambiguous. 6. **Confirm consequential actions.** Explain the effect and obtain explicit approval immediately before creating, deleting, rotating, revoking, restoring, overwriting, or forcing anything. 7....