docs(go): Add unreleased SDK options and Scope.SetAttributes (#16789)

Author: giortzisg

docs/platforms/go/common/configuration/options.mdx

@@ -142,6 +142,14 @@ When set to `true`, the SDK does not emit metrics. By default, metrics are enabl
 
 </SdkOption>
 
+## Client Reports Options
+
+<SdkOption name="DisableClientReports" type="bool" defaultValue="false">
+
+When set to `true`, the SDK does not send client reports. Client reports track the number of discarded events and their reasons, helping you monitor SDK health. By default, client reports are enabled.
+
+</SdkOption>
+
 ## Tracing Options
 
 <SdkOption name="EnableTracing" type="bool" defaultValue="false">
@@ -150,7 +158,7 @@ Enables performance tracing. When enabled, the SDK will create transactions and
 
 </SdkOption>
 
-<SdkOption name="TracesSampleRate" type="float64" defaultValue="0.0" envVar="SENTRY_TRACES_SAMPLE_RATE">
+<SdkOption name="TracesSampleRate" type="float64" defaultValue="0.0">
 
 A number between `0.0` and `1.0`, controlling the percentage chance a given transaction will be sent to Sentry (`0.0` represents 0% while `1.0` represents 100%.) Applies equally to all transactions created in the app. Either this or `TracesSampler` must be defined to enable tracing.
 
@@ -191,6 +199,18 @@ When set to `true`, the W3C Trace Context HTTP `traceparent` header is propagate
 
 </SdkOption>
 
+<SdkOption name="StrictTraceContinuation" type="bool" defaultValue="false">
+
+When set to `true`, the SDK requires matching organization IDs in the incoming baggage header for continuing a trace. This is useful for preventing trace continuation from 3rd-party services that happen to be instrumented by Sentry but belong to a different organization.
+
+</SdkOption>
+
+<SdkOption name="OrgID" type="uint64">
+
+Configures the organization ID used for trace propagation and features like `StrictTraceContinuation`. In most cases, the organization ID is already parsed from the DSN. This option should be used when non-standard Sentry DSNs are used, such as self-hosted or when using a local Relay.
+
+</SdkOption>
+
 <SdkOption name="TraceIgnoreStatusCodes" type="[][]int">
 
 A list of HTTP status codes that should not be traced. Each element can be either:
@@ -301,6 +321,12 @@ An optional set of SSL certificates to use. See the [Providing SSL Certificates]
 
 </SdkOption>
 
+<SdkOption name="DisableTelemetryBuffer" type="bool" defaultValue="false">
+
+When set to `true`, disables the telemetry buffer layer for prioritizing events and uses the legacy transport layer instead.
+
+</SdkOption>
+
 ### Providing SSL Certificates
 
 By default, TLS uses the host's root CA set. If you don't have `ca-certificates` (which should be your go-to way of fixing the issue of the missing certificates) and want to use `gocertifi` instead, you can provide pre-loaded cert files as one of the options to the `sentry.Init` call:

docs/platforms/go/common/enriching-events/scopes/index.mdx

@@ -71,3 +71,28 @@ On the other hand, <PlatformIdentifier name="with-scope" /> creates a clone of t
 made will stay isolated within the <PlatformIdentifier name="with-scope" /> callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call <PlatformIdentifier name="clear" /> to briefly remove all context information.
+
+## Setting Attributes
+
+You can set typed attributes on the scope using `SetAttributes`. These attributes are attached to logs and metrics emitted within the scope. Attributes use the `attribute` package for type safety.
+
+```go
+import "github.com/getsentry/sentry-go/attribute"
+
+sentry.ConfigureScope(func(scope *sentry.Scope) {
+	scope.SetAttributes(
+		attribute.String("user.role", "admin"),
+		attribute.Int("retry.count", 3),
+		attribute.Bool("feature.enabled", true),
+		attribute.Float64("score", 99.5),
+	)
+})
+```
+
+To remove an attribute from the scope, use `RemoveAttribute`:
+
+```go
+sentry.ConfigureScope(func(scope *sentry.Scope) {
+	scope.RemoveAttribute("user.role")
+})
+```