fix(jsonview): avoid width underflow in static string rendering

[sylvesterkaczmarek]

Summary

Avoid converting a negative remaining display width into an enormous unsigned truncation limit when rendering static JSON strings in narrow terminals.

Problem

formatResult currently truncates long strings with:

truncate.String(str, uint(width-1))

Object and array rendering can pass a non-positive width after subtracting the rendered key or numbering width. Converting width-1 to uint then wraps the negative value to a very large number, so the string is effectively not truncated and can spill far beyond the available terminal width.

Fix

Centralize string-width handling in a small helper that:

• returns no string content when no width is available;
• renders a single ellipsis when exactly one column is available;
• preserves strings that already fit;
• only converts a verified positive truncation width to uint.

Normal-width output is unchanged.

Regression coverage

Added focused tests covering:

• a non-positive string width, which previously retained the full string because of unsigned wraparound;
• the one-column case, which now deterministically renders a single ellipsis.

Validation

The branch is based directly on current upstream main (ee92673a416c0851a5fe8907a2453db7bd450633) and contains one signed commit touching only the static JSON renderer and its focused regression test. Full Go test execution is left to repository CI.

Risk

Low. The behavior change is limited to string values whose available display width is zero or too small to contain the original value.

[markstuart-oai]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-06T01:31:48.747898Z	10ad974	Manual request
🔒 Security Review	✅ Completed 2026-09-06T01:32:46.357870Z	10ad974	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 10ad97459e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: 10ad97459e

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.