What problem does it solve? Go developers frequently misuse context.Context by breaking propagation chains, leaking cancel functions, storing contexts in structs, or abusing context values, leading to leaked goroutines, ignored cancellations, and lost trace data. ## Core Features & Use Cases - Propagation Rules: Enforces passing the same context through HTTP handlers, services, databases, and external API calls using r.Context() and *Context variants. - Cancellation & Timeouts: Covers WithCancel, WithTimeout, WithDeadline, nested deadline semantics, AfterFunc, and WithoutCancel for background work outliving requests. - Context Values & Tracing: Teaches unexported key types, what belongs in context values versus function parameters, and trace ID propagation across services. - Use Case: When writing an HTTP handler that must send an audit log after the client disconnects, use context.WithoutCancel to preserve the trace_id while detaching cancellation. ## Quick Start Ask the AI to review your Go HTTP handler or service method for correct context.Context propagation, timeout handling, and cancellation leaks.