Address review feedback: TrackOutputBytes sentinel error design is intentional

[Copilot]

Addresses review feedback questioning why ErrOutputBytesExceeded / ErrNegativeTrackingSize are returned directly from reflection-based decode paths rather than wrapped in *UnmarshalError.

Resolution

No code changes required. The design is intentional:

• Sentinel errors use errors.New (not fmt.Errorf) to keep TrackOutputBytes small enough for the Go compiler to inline
• Generated code wraps these sentinels via fmt.Errorf before they reach callers
• The existing comment at the declaration site already documents this contract

// Sentinel errors for TrackOutputBytes — using errors.New instead of
// fmt.Errorf keeps the function small enough for the Go compiler to inline.
// Callers wrap these with fmt.Errorf to add context.
var (
    ErrOutputBytesExceeded  = errors.New("output bytes limit exceeded")
    ErrNegativeTrackingSize = errors.New("negative tracking size")
)

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[tamirms]

Closing — improvements from this PR have been incorporated into #22 where applicable. Thank you!