observability-and-instrumentationlisted

# Observability and Instrumentation ## Overview Code you can't observe is code you can't operate. Observability is the ability to answer "what is the system doing and why?" from the outside, using the telemetry the code emits. Instrumentation is not a post-launch add-on — it's written alongside the feature, the same way tests are. If a feature ships without telemetry, the first user-reported bug becomes archaeology instead of a query. ## When to Use - Building any feature that will run in production - Adding a new service, endpoint, background job, or external integration - A production incident took too long to diagnose ("we couldn't tell what happened") - Setting up or reviewing alerting rules - Reviewing a PR that adds I/O, retries, queues, or cross-service calls **NOT for:** - Diagnosing a failure happening right now — use a debugging skill (observability is what makes debugging fast next time) - Profiling and optimizing measured slowness — use a performance optimization skill - Launch-day monitoring checklists and rollback triggers — use a shipping/launch skill; this skill covers the instrumentation that feeds them - User asks or mentions this skill in English (e.g., "use /observability-and-instrumentation", "run observability-and-instrumentation"). - O usuário pede ou menciona esta skill em português (ex.: "use /observability-and-instrumentation", "execute observability-and-instrumentation"). ## Process ### 1. Define "working" before instrumenting Telemetry wit