feat: add dataset list command

[aptracebloc]

Adds tracebloc dataset list — a read-only listing of the datasets ingested into the cluster (the tables in training_test_datasets). Scope A: names only.

Behaviour

• Bare tracebloc dataset list runs against your current kubeconfig context + its namespace. --kubeconfig/--context/--namespace are optional overrides (zero-value-safe, same as cluster info); --output-json emits {namespace, release, count, datasets[]} on stdout (human output → stderr).
• Empty state points at dataset push; --help links the dashboard (https://ai.tracebloc.io/metadata) for the full catalog.

Mechanism

Reuses the dataset rm exec seam — push.SPDYExecutor + findRunningPod + IngestionDatabase — to run one query in the mysql pod:

SELECT table_name FROM information_schema.tables
WHERE table_schema = 'training_test_datasets' ORDER BY table_name;

information_schema (not SHOW TABLES) means a never-pushed cluster returns an empty list, not an error. Raw output → []string via a pure, unit-tested parser.

Exit codes

0 listed (incl. empty) · 3 kubeconfig · 4 no parent release in the namespace · 7 cluster query failed.

Verification

• make ci green. Cluster-free tests: parseDatasetList, renderDatasetList (empty + populated), writeDatasetListJSON (shape + nil→[]).
• Live on EKS dev: human listing rendered 69 datasets; --output-json produced clean JSON on stdout (banner on stderr).

🤖 Generated with Claude Code

---

Note

Low Risk
Read-only cluster query reusing the existing mysql exec seam; no data mutations or auth changes.

Overview
Adds tracebloc dataset list, a read-only way to see ingested dataset table names in the cluster. It is registered under dataset, mentioned on the root home screen, and follows the same kubeconfig / namespace flags and exit codes (3, 4, 7) as dataset push and cluster info.

The command loads the parent release, then calls new push.ListDatasets, which execs into the mysql pod (same SPDYExecutor / findRunningPod path as teardown) and runs an information_schema query so a never-pushed cluster returns an empty list instead of failing. Human output lists names (with an empty-state hint toward dataset push); --output-json writes {namespace, release, count, datasets[]} on stdout with banner on stderr, including JSON error objects on early failures like dataset push.

Unit tests cover mysql output parsing, rendering, JSON shape, and the JSON-on-failure contract.

^{Reviewed by Cursor Bugbot for commit 13f004c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

👋 Heads-up — Code review queue is at 18 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• averaging-service#102 — chore(kanban): declare staging as prod-truth branch via .kanban.yml · author: @LukasWodka · no reviewer assigned
• averaging-service#98 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned
• backend#732 — feat(experiments): add per-experiment aggregation_strategy field (#730) · author: @LukasWodka · no reviewer assigned
• client-runtime#79 — docs(#59): feasibility — delete pod_tokens (and the reconciler)? · author: @saadqbal · no reviewer assigned
• client-runtime#89 — feat(proxy): stateless signed pod-proxy tokens (#79 option D) · author: @saadqbal · no reviewer assigned
• data-ingestors#146 — test(schema): lock category enum to the engine's TaskCategory (anti-drift) · author: @LukasWodka · reviewer: @saadqbal
• data-ingestors#148 — Develop to prod · author: @divyasinghds · reviewer: @saadqbal
• design-system#19 — fix: un-track coverage/ and node_modules/ from git · author: @LukasWodka · no reviewer assigned
• design-system#22 — ci: add Vitest test workflow · author: @LukasWodka · reviewer: @aptracebloc
• design-system#23 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 860c271. Configure here.}