fix(deps): update module golang.org/x/term to v0.37.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
golang.org/x/term	v0.34.0 -> v0.37.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 1 additional dependency was updated

Details:

Package	Change
golang.org/x/sys	v0.37.0 -> v0.38.0

[github-actions]

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

• The update from v0.34.0 to v0.37.0 appears to be a minor version increment with no documented breaking changes
• golang.org/x/term is part of the Go extended packages and follows Go's compatibility promise
• The IsTerminal function signature and behavior remain unchanged across versions
• No security vulnerabilities identified in the version range
• Also updates golang.org/x/sys from v0.37.0 to v0.38.0 as a transitive dependency

🎯 Impact Scope Investigation

• Single usage location: cmd/root.go:28 uses term.IsTerminal(int(os.Stdout.Fd())) to detect terminal output
• Function compatibility: The IsTerminal function maintains the same signature func IsTerminal(fd int) bool
• No direct API usage of new features: The codebase only uses the basic terminal detection functionality
• Minimal surface area: Only imports the package and uses one stable function
• No impact on other dependencies: This is a leaf dependency with no cascading effects on the project's architecture

💡 Recommended Actions

• Immediate merge recommended: This is a safe dependency update with no breaking changes
• No code modifications required: The existing usage pattern remains fully compatible
• No configuration changes needed: The update is transparent to the application logic
• Consider running existing tests: While not required for compatibility, running go test ./... would verify continued functionality

🔗 Reference Links

• golang.org/x/term v0.37.0 Documentation
• Go Module Compatibility Guidelines

Generated by koki-develop/claude-renovate-review