Document message.Contents.Usage and message.UsageDetails.Add accessors

[PratikDhanave (PratikDhanave)]

What

Add doc comments to two exported accessors in message/content.go that were missing them:

• Contents.Usage() — sums the UsageDetails of every UsageContent in the slice, returning the aggregate token usage.
• UsageDetails.Add(other) — accumulates other into the receiver, summing each token count field and merging AdditionalCounts.

Why

Both are non-boilerplate exported accessors, yet their documented sibling Contents.Text already carries a doc comment while these two did not. Documenting them keeps the public API surface consistently discoverable via go doc and godoc. These accessors are the Go equivalents of the .NET/Python usage aggregation helpers (UsageDetails.Add / usage summing over content), so documenting their aggregation-and-merge semantics aligns the Go port's public docs with the cross-SDK behavior contract.

Testing

Docs-only change; no behavioral change. Verified with:

• go build ./..., go vet ./message/..., go test ./message/... all pass.
• gofmt -l message/content.go reports clean.
• go doc ./message Contents.Usage and go doc ./message UsageDetails.Add render the new comments.

[Copilot]

Pull request overview

This PR improves the public message package API documentation by adding missing Go doc comments for two exported accessors related to token-usage aggregation, aligning their discoverability and described semantics with the existing documented accessors.

Changes:

• Added a doc comment for Contents.Usage() describing that it aggregates UsageDetails across all UsageContent entries (returning zero usage when none are present).
• Added a doc comment for UsageDetails.Add(...) describing its field-wise accumulation behavior and AdditionalCounts merge semantics (including first-use map allocation).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Parity Review: No Issues Found

This PR adds godoc comments to two already-exported accessors in message/content.go:

• Contents.Usage() — aggregates UsageDetails across all UsageContent items
• UsageDetails.Add(other) — accumulates token counts and merges AdditionalCounts

This is a docs-only change (1 file, 2 added comment lines, zero behavioral change). No exported API surface was added, removed, or altered.

Cross-repo parity: The semantics (summing token-count fields, merging additional counts) are consistent with the upstream .NET/Python usage aggregation pattern. Documenting them keeps the Go public API discoverable and aligned with how the cross-SDK behavior contract is described in other languages.

Verdict: ✅ No parity issues. The parity-approved label is correct.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Go API Consistency Review Agent · 24.5 AIC · ⌖ 5.54 AIC · ⊞ 5.9K · ◷