5.1.5 — SDK stream diagnostic correction

DSH Accounts & Usage 5.1.5

Commit: 8527a004b26e16d94d0e8872fbd49223621021c3 (annotated tag v5.1.5).
Based on published tag v5.1.4 commit 72ecf169b15a64c6c52a0b83c73c4998d63052fc; its governance/OAuth/client fixes are preserved.
Companion consumer: dsh-codex-compaction 0.4.0.

• Record SDK stream terminal diagnostics before lease freeze: completed, failed, cancelled, timed-out.
• Omit unavailable SDK-owned wire byte/event metrics rather than manufacturing zeros or counting normalized events as wire data.
• Preserve native compact diagnostics, error identities, usage, single-flight leases, cancellation and deadlines.
• No new authentication flow, credentials, core patch, data migration or client rebuild. Pinned SDKs remain auth 0.82.1 / native 0.84.4.

Fixed asset

dsh-token-usage-5.1.5.tgz
SHA256: 870975cb1c974b033d4033e3d2cdff9937dbfd0b8d98d777b6c23e8118580ee5

The asset is the exact previously accepted 61-file candidate. Package JSON values match the source commit; other packaged source files match byte-for-byte. The client asset is unchanged from v5.1.4. Packaged documentation retains preparation-stage labels; this release page records distribution status.

Validation and limits

Sixteen new injected transport/pinned SDK diagnostic regressions have red-to-green evidence. The initial isolated source passed 327 tests; the published-v5.1.4-based candidate then passed its full owner suite again in isolated snapshots. Paired consumer integration passed 32 tests with one optional real-time test skipped. Fixed-asset loader/GUI recovery passed without new model generation.

Older consumers may omit diagnostics on newly recognized terminal phases; execution is unchanged. Pair with compaction 0.4.0 for the expanded allowlist. These terminal diagnostics do not themselves prove a Basic summary commit. The final diagnostic delta has no additional real-provider/model validation; real second-account switching remains unverified.

Formal GitHub tag acceptance — passed

Actual npx --yes --ignore-scripts github:shaomingbo/dsh-token-usage#v5.1.5 and companion commands passed on both CLI 0.1.2-alpha.3 and 0.1.2-rc.1, with actual Base/Web 0.1.2-rc.1. Each row used a fresh HOME, DSH_HOME, cwd and cache, without a source override or provider credentials.

Install/repeat/status/uninstall, lifecycle blocking and unrelated-profile preservation passed. All 61 owner / 28 consumer packaged files and npx materializations matched the frozen candidates; tags retained the exact expected commits before and after. Real config dump/startup showed owner, compaction and provider entries active; the served client combo contained the exact frozen owner client bytes. Both temporary servers and fixture directories were cleaned up.

This verifies actual tag distribution, startup and client asset serving, not new browser-render/HMR or model-quality evidence. No sessions or generation were used. No production deployment or restart is included.