[jeremydmiller]

Closes #5772.

Problem

With TrackConnections = TrackLevel.Verbose, EventTracingConnectionLifetime.writeVerboseEvents emitted marten.append.event only for operations deriving from Weasel.Storage.AppendEventOperationBase. Both Quick routes fell through, and their Role() is Events, so the fallback branch skipped them too:

• The bulk route. QuickAppendEventsOperationBase handles one mt_quick_append_events call per stream. Under QuickWithServerTimestamps, the V9 default, nearly every append and StartStream goes through it.
• The per-event Quick route that reads its sequence back. This is weasel#747, live since Read back the seq_id a per-event Start draws, so a failed batch tombstones it (#5454 follow-up) #5755 merged. QuickAppendEventWithVersionReadingSequenceOperation is internal to Weasel and implements IStorageOperation directly. It is what a Quick-mode StartStream uses (and the daemon's side-effect appends).

Fix

• The tracer handles three cases:
  • AppendEventOperationBase: one event, as before.
  • QuickAppendEventsOperationBase: one event per event in its StreamAction.
  • The new TracedQuickAppendEventOperation: one event.
• TracedQuickAppendEventOperation is a Marten wrapper around Weasel's per-event Quick operation that exposes Event / Stream. ClosedShapeEventDocumentStorage.QuickAppendEventWithVersion wraps only when TrackConnections == Verbose (fixed at store construction), and only an operation that is neither an AppendEventOperationBase nor a NoDataReturnedCall. Below Verbose nothing is wrapped and nothing changes. The wrapper forwards ConfigureCommand, PostprocessAsync (so the seq_id read-back still happens), Role, DocumentType, TryTransform and ToString. Like the wrapped operation, it is not a NoDataReturnedCall.

The cleaner long-term shape is a public interface in Weasel for per-event append operations, which the tracer could check instead of the wrapper. That needs a Weasel release, so this PR doesn't wait on it.

Tests

CoreTests/Bugs/Bug_5772_verbose_tracing_of_quick_appends captures the marten.connection activity under Verbose. It asserts exactly one marten.append.event per appended event, in order, across Rich, Quick and QuickWithServerTimestamps, for both StartStream and Append. The Quick StartStream case also asserts every event's Sequence was still read back through the wrapper.

	Rich	Quick	QuickWithServerTimestamps
master	green	red (Start + Append)	red (Start + Append)
tracer change only, no wrapper	green	red (Start only)	green
this PR	green	green	green

Run locally on net10.0 / PG17: Bug_5772*, EventTracingConnectionLifetimeTests, marten_activity_parenting and Bug_3911*, 30/30 pass.

Not covered by a test: the daemon side-effect append path, which uses the same QuickAppendEventWithVersion and so gets the same wrapping.

No public API change.

🤖 Generated with Claude Code