feat: Logs sent via SentrySdk.Logger no longer require EnableLogs

[jamescrosswell]

Phase 1 of #5479, split out of #5504.

Summary

Reaching for SentrySdk.Logger (or any SentryStructuredLogger) is already an explicit statement that you want those logs in Sentry, so requiring EnableLogs = true on top of it was an unnecessary hoop. That gate is gone.

The whole change is one branch in SentryStructuredLogger.Create:

-return options.EnableLogs
-    ? new DefaultSentryStructuredLogger(hub, options, clock, batchCount, batchInterval)
-    : DisabledSentryStructuredLogger.Instance;
+return new DefaultSentryStructuredLogger(hub, options, clock, batchCount, batchInterval);

What this deliberately does not change

SentryOptions.EnableLogs stays, still defaults to false, and is not obsolete. The logging integrations — Sentry.Extensions.Logging, Sentry.Serilog, Sentry.NLog, Sentry.Log4Net — each check EnableLogs themselves before calling hub.Logger.CaptureLog(...), so they are entirely unaffected and continue to honour the option.

That is what makes this seam clean: the integrations sit in front of the gate being removed, not behind it. The evidence is that not a single Verify snapshot or API-approval file changed — if any integration had started emitting logs, the Simple / Versioning snapshots would have moved, as they did in #5504.

Leaving them alone is deliberate rather than incidental. Those integrations instrument a general-purpose ILogger-style surface where "I configured logging" says much less about whether you want the logs in Sentry, and each one produces three different things from a single log call — breadcrumbs, events, and structured logs. Changing that is a breaking change, so it belongs in the next major version.

The option's XML doc now says exactly which of the two it governs.

Notes for review

• Sentry.Samples.Console.Basic used the direct API only, and its comment claimed the option "enables Sentry Logs created via SentrySdk.Logger" — no longer true, so both are gone. Every other sample uses a logging integration and keeps EnableLogs = true untouched.
• Two HubTests cases described the option toggling this API and no longer have any meaning; Logger_IsDisabled_DoesNotCaptureLog is replaced by Logger_EnableLogsDisabled_StillCapturesLog, asserting the new behaviour directly. Create_EnableLogsDisabled_NewDefaultInstance covers the same at the factory.
• The existing integration tests that assert EnableLogs still gates them (SentrySinkTests.Emit_StructuredLogging_IsEnabled, SentryAppenderTests.DoAppend_StructuredLogging_IsEnabled, SentryStructuredLoggerTests.IsEnabled_HubAndOptions_Returns) are untouched and now serve as the guard against this phase leaking into the next.
• No CHANGELOG.md entry — scripts/verify-changelog.sh rejects manual ## Unreleased sections, so the commit subject is the changelog line.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.72%. Comparing base (5cd6ad6) to head (b4c3769).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5512      +/-   ##
==========================================
- Coverage   74.74%   74.72%   -0.03%     
==========================================
  Files         513      513              
  Lines       18829    18827       -2     
  Branches     3682     3681       -1     
==========================================
- Hits        14074    14068       -6     
- Misses       3875     3878       +3     
- Partials      880      881       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.