docs: the DLQ example does not compile, and three statements no longer match the code

[EricAndrechek]

Area: docs · docs · found via #612's "Follow-ups" (all three predate that branch)

Three defects, each verified against 4ff50745:

1. The DLQ example does not compile. docs/src/content/docs/sdk/admin.md:61 and :65 both declare const { data } inside one fenced block, so pasting it into a file is a redeclaration error. The block two paragraphs below gets it right (:71-72 uses const { data: clicks } for the second call).

2. That example shows a count the server never returns. admin.md:62 reads // data: { tables: { "clicks": 3, "users": 0 }, total: 3 }. deadLetterTables (internal/mq/deadletter.go:8-17) builds its map only from subjects the stream reports a count for, so a table with nothing parked never appears as a key — a 0 value is unreachable.

3. api.md's ?table= row is misleading about total. The row at docs/src/content/docs/api.md:800 says ?table=clicks "returns only the clicks count". A filter narrows tables but not total, which stays the tenant's whole parked count — stated at internal/mq/mq.go:313 ("Total is every parked message of the tenant, whatever the filter") and pinned by internal/mq/embedded_test.go:802.

4. settings-directory.mdx:219 calls the unreadable-envelope exception "new in this release", which goes stale at the next release and says nothing to a reader who does not know which release they are on.

Note: #583 story 11 owns settings-directory.mdx, api.md and configuration.mdx for the tenancy content. These are separate defects that happen to live on two of those pages.

Related: #612, #583

---

From the merged-PR follow-up sweep (#612 "Follow-ups"); validated by code-read against 4ff50745 on 2026-09-28.