temps-platform-setup

# Temps Platform Setup Provision a Temps instance and hand it back as a verified CLI context while keeping infrastructure scope, browser approval, and credentials under the user's control. ## Safety contract Apply these rules to every workflow: 1. **Require an explicit target.** Before provisioning, identify the exact server hostname/IP, SSH identity, setup mode, release channel or pinned version, administrator email, and local context name. The user's direct request to provision that target is authorization for the scoped install; ask again only if a destructive conflict or materially different choice appears. 2. **Authenticate every executable artifact.** Download the official installer as a file, require its independently reviewed digest pinned below, run `bash -n`, and inspect its material actions. Before execution, enumerate its transitive scripts, binaries, packages, and container images. Every executable artifact needs an immutable reference plus a signature, attestation, or digest from a separately trusted source. Refuse automated installation when that provenance is unavailable; a checksum from the same mutable origin and manual source review are not authenticity proofs. Never pipe network output into a shell. 3. **Treat installer output as secret-bearing.** Headless installation output and `~/.temps/setup-result.json` can contain the generated administrator password and API key. Redirect the raw transcript to a mode-0...