docs(repos): add usage examples to list repos and add pagination

[mbevc1]

Other kosli list * reference pages render an "Examples Use Cases" section from the command's Example field; list repos had none. Add examples covering the default listing, --name and --provider filters, and pagination, matching the style of list flows / list environments.

Also adds pagination and table headers to match backend defaults and behaviour.

[claude]

Claude finished @mbevc1's task in 1m 58s —— View job

---

Review — PR #1006 · docs(repos): add usage examples & pagination

• Gather context (read diff & changed files)
• Phase 1: Static analysis (build, vet, mod tidy)
• Phase 2: Code review
• Phase 3: Acknowledge good work

Phase 1 — Static analysis ✅

Check	Result
go build ./...	✅ passes
go vet ./cmd/kosli/	✅ clean
go mod tidy + git diff go.mod go.sum	✅ no changes

Phase 2 — Code review

This is a clean, well-scoped PR and the iterative review rounds already resolved the substantive points. Confirming the current state:

• Non-default page size — the example (--page-limit 25) and the pagination test now use 25, so the flag's effect is visible rather than mirroring the default 15. ✅
• Accurate long description — listReposLongDesc now states results are always paginated (first page, 15/page by default), matching the actual runtime behavior where run unconditionally sends page/per_page (listRepos.go:87-88). This correctly diverges from the list flows wording. ✅
• Footer + headers — printReposListAsTable now renders the NAME/URL/PROVIDER/TAGS header and a Showing page X of Y, total Z repos footer, backed by the new listReposResponse envelope. ✅
• Consistent page source — both the empty-list message and the footer read response.Page (documented in the inline comment at listRepos.go:134-136), so the two paths can't disagree. ✅

Minor / non-blocking observations:

1. printReposListAsTable(raw string, out io.Writer, page int) — the page parameter is now unused (the body reads response.Page throughout). It's required to satisfy the shared output.FormatOutputFunc signature, so this is fine and not a regression; just noting it in case a linter ever flags it.
2. Footer is appended unconditionally (no if pagination != nil guard like printFlowsListAsTable). Already discussed in-thread — acceptable given the endpoint always paginates and always returns these fields.

Testing — good coverage: the pagination case, --name/--provider/--repo-id filters, empty-result messaging, blank-TAGS rendering, and a standalone unit test (TestPrintReposListAsTableRendersBlankTagsCell) asserting header + footer without a live server. Test page size matches the documented example.

Phase 3 — Good work 👍

• Introducing listReposResponse as a named type cleans up the previous anonymous-struct unmarshal and makes the pagination fields explicit.
• The examples closely mirror the list flows / list environments style, giving the reference docs a consistent "Example Use Cases" section.
• The standalone table-rendering unit test is a nice touch — it exercises the formatting logic deterministically without depending on the local Kosli server.

Verdict: LGTM. All prior review concerns are addressed; no blocking issues.
· 20260708_repo_examples