fix(cli): report chunk truncation only when rows are omitted

[rudycelekli]

Summary

chunk list --all-pages reported meta.has_more=true when the complete document had exactly --limit chunks. Determine truncation before slicing using fetched rows and the server total, so reaching the limit with no omitted rows reports false. Genuine truncation and single-page behavior stay unchanged.

Validation

• Eight real root-command/SDK HTTP cases cover exact limits on one and multiple pages, below-limit totals, omitted known/fetched rows, single-page behavior, and empty documents. Both exact-limit regressions fail on original source; six healthy controls pass. All eight pass with this change, including counts, order, and request counts.
• Full CLI go test -count=1 ./... and go vet ./... pass.
• golangci-lint 2.12.2, run --new-from-rev=origin/main --concurrency=2 --timeout=2m ./..., passes from cli/.

Tests use temporary configuration and synthetic loopback HTTP. Full backend checks remain blocked by uncached backend dependencies; these results cover the CLI module. Developed and reviewed with AI assistance.

[Copilot]

🟢 Approval recommended

The logic matches the documented semantics and is comprehensively covered by focused regression tests.

0 open findings

What changed in this PR

Fixes incorrect meta.has_more reporting when fetched chunk counts exactly match --limit.

Changes:

• Detects truncation using fetched rows and server totals before slicing.
• Adds eight HTTP-backed pagination and truncation regression cases.

File	Description
cli/​cmd/​chunk/​list.go	Corrects exact-limit truncation detection.
cli/​cmd/​chunk/​list_truncation_test.go	Covers limit, pagination, ordering, and empty results.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.