temps

# Temps Treat Temps as a product workflow, not a command catalog. Understand the user's desired outcome, inspect the application or platform read-only, load only the relevant reference, make the smallest authorized change, and prove the result. Runtime requirements: a shell and either `bunx` or `npx` for CLI operations; Python 3.9+ for the bundled read-only capability detector. ## Required workflow 1. Classify the task: application preparation, deployment, platform operation, observability, recovery, or diagnosis. 2. Inspect before changing anything. Identify the repository framework, current Temps context, target project/environment, and existing setup. 3. Read only the references named in the routing table below. Do not load the complete command index or unrelated observability pillars. 4. For CLI work, use the pinned zero-install invocation and the safety contract in [references/cli-runtime.md](references/cli-runtime.md). 5. Before a state change, explain its target and effect. Ask for confirmation when the change is destructive, secret-bearing, or otherwise requires new authority. 6. Verify the outcome using a read-only CLI command, application test, and—when telemetry is involved—a real synthetic signal. ## Application capability checkpoint When creating, linking, migrating, reviewing, or deploying an application, inspect its observability setup before the final deployment step: ```bash python3 skills/temps/scripts/detect_project_capabilities....