Release 2.8.2

[mtmk]

Patch release with JetStream teardown fixes and a dependency bump.

• jetstream: simplify ordered push consumer sub teardown (Simplify ordered push consumer sub teardown #1191)
• jetstream: dispose ordered push consumer sub on teardown (Fix ordered push consumer subscription leak on teardown #1188)
• Bump MessagePack from 3.1.1 to 3.1.7 (Bump MessagePack from 3.1.1 to 3.1.7 #1183)
• di: clarify package descriptions for NuGet (Clarify DI package descriptions #1163)

[synadia-claude-reviewer]

Claude finished @mtmk's task in 1m 50s —— View job

---

PR Review: Release 2.8.2

• Gather context and read PR details
• Examine PR diff
• Review changed files and related code
• Post review summary

---

Review Summary

This is a clean patch release PR. The only diff in this PR itself is the version bump in version.txt (2.8.1 → 2.8.2), which is correct for a patch release. The substantive changes landed via the referenced PRs already merged to main.

JetStream subscription leak fix (#1188) — NatsJSOrderedPushConsumer.cs

The fix is correct and well-structured. DisposeAsync now disposes the current _sub after both background loops (_consumerCreateTask, _commandTask) have completed:

var sub = _sub;
if (sub != null)
{
    await sub.UnsubscribeAsync();
    await sub.DisposeAsync();
}

• Thread safety: _sub is volatile; reading it into a local after both tasks complete is safe — no new subscription can be assigned at that point.
• Ordering: Completing the channels (TryComplete) and awaiting both tasks before touching _sub is the right order. This matches the existing pattern in CreatePushConsumer (lines 374–375).
• Event handler cleanup: NatsJSOrderedPushConsumerSub.DisposeAsync already unhooks ConnectionOpened (line 491), so the root cause of the leak is properly severed.
• One minor note: _consumerCreateChannel.Writer.TryComplete() is awaited via _consumerCreateTask, but there's no await on the TryComplete calls themselves — this is fine since TryComplete is synchronous and the subsequent await on the tasks ensures the loops have fully drained.

MessagePack 3.1.1 → 3.1.7 (#1183): routine dependency bump, no concerns.

DI package description clarifications (#1163): docs-only, no code impact.

Overall: The release is sound. No correctness, security, or performance concerns.

[Jarema]

LGTM