feat: home-screen polish — CTA spacing + flip the dataset push entry

[aptracebloc]

Two small home-screen / output polish changes.

1. Detach closing/CTA lines with a blank line

New ui.Printer.Newline() (emits one blank line), called above the lines that conclude or call to action so they don't get lost against the field/log block above:

• cluster info — above ✔ Ready for tracebloc dataset push.
• dataset push --dry-run — above ✔ Dry-run complete …
• dataset rm — above ✔ Deleted …
• dataset rm --dry-run — above ✔ Dry-run — nothing was deleted.
• home screen — above the Add --help … footer

Not changed: the push ingestion summary (submit.go already emits that blank before RenderSummary); the cancel lines (left tight to the confirm prompt).

2. Flip the home-screen dataset push entry

Lead with the guided default rather than a flag example:

· tracebloc dataset push             — stage + ingest a dataset interactively (or use --help to see flags)

(was tracebloc dataset push ./data … (guided if you omit flags)). "interactively" echoes the tagline; bare command keeps the — column aligned.

Verification

make ci green; confirmed live (line-numbered output shows the real blank lines; home screen shows the flipped, aligned push entry). Existing substring-based tests unaffected.

🤖 Generated with Claude Code

---

Note

Low Risk
Terminal formatting and help text only; no ingestion, cluster, or auth behavior changes.

Overview
Adds ui.Printer.Newline() so closing success lines and footers sit on a blank line after field blocks, and wires it into cluster info, dataset push / dataset rm dry-run and post-delete success paths, plus the bare tracebloc home screen before the --help hint.

Updates the home screen dataset push line to emphasize the interactive default (bare command, “interactively”, pointer to --help for flags) instead of ./data and “guided if you omit flags”.

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

[LukasWodka]

👋 Heads-up — Code review queue is at 17 / 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#103 — fix(averaging): correctness foundations — DP, shape guard, sklearn weighting, bounded ensembles (#73) · author: @LukasWodka · reviewer: @shujaatTracebloc
• 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 · reviewer: @saqlainsyed007, @shujaatTracebloc
• client#207 — test(charts): add helm-unittest suite for ingestion-authz-configmap · 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#23 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned
• docs#47 — docs(environment-setup): #192 namespace/workspace flow (hold for client#192) · author: @LukasWodka · reviewer: @saadqbal
• docs#53 — docs: repoint old Setup Guide redirects · author: @LukasWodka · no reviewer assigned

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