error-handling

Error wrapping in Go preserves the underlying cause by using `fmt.Errorf` with the `%w` verb. This maintains the error chain, allowing callers to inspect root causes via `errors.Is` and `errors.As` while adding debugging context.

Standard Go errors for HTTP APIs are defined using global error variables and generated via the `httptk` package. This ensures API endpoints return OCI-compliant responses that clients can easily distinguish using standard error checking functions.

Global error variables provide a standardized reference for consistent error checking across Go applications. They allow functions to return specific sentinel errors that callers can reliably compare against using `errors.Is` to determine exact failure modes.

OCI-compliant HTTP error responses are generated using the `httptk` package to standardize API failures. This enforces consistent error generation patterns that conform to OCI specifications for easily distinguishable client-side error handling.

Yes, `errors.Is` and `errors.As` work seamlessly with wrapped Go errors. Wrapping errors with `fmt.Errorf` using `%w` preserves the error chain, allowing these functions to traverse the wrapped errors and match specific types or sentinel values.

Yes, this approach handles both standard Go errors and HTTP API errors by enforcing global error variables and wrapping with `%w` for general robustness, while utilizing `httptk` factories specifically for OCI-compliant HTTP API error generation.