temps-best-practices

# Temps Best Practices Best practices for application code that runs on Temps. This skill owns the **runtime contract** and **production observability**; use `temps-cli` for platform operations. ## Required workflow 1. For any deployable application, read [references/runtime-contract.md](references/runtime-contract.md). 2. When any telemetry or replay is enabled, read [references/telemetry-hygiene.md](references/telemetry-hygiene.md). 3. Read only the reference for each observability pillar in scope. 4. Determine the deployment source. For repository builds, inspect and merge `.temps.yaml`; for image/static deployments, inspect the deployment health-path override because no repository config is available. 5. Run the runtime and telemetry verification checklists before considering the work complete. ## Runtime contract summary Every web application should expose a dedicated health endpoint. Repository builds configure it in `.temps.yaml` under the project's effective Temps Root Directory / Docker build context: ```yaml health: path: /healthz ``` Use `health.path`; do not rely on the currently parsed-but-unapplied `status`, `interval`, `timeout`, or `retries` fields. If OpenTelemetry server tracing is enabled, exclude the exact health path from incoming spans and routine access-log/request-metric noise. Keep the route, `.temps.yaml`, and filters synchronized. Image and static deployments cannot read `.temps.yaml`; set the same route through their deployment `health_ch...