RFC-0001 · P1 · cli — rename dataset → data (ingest / list / delete; keep aliases one cycle)

[LukasWodka]

Parent: backend#830 (RFC-0001 epic) · RFC: §6.2 (naming rationale), §8 · Flow family: backend#879 (Data) · Phase 1 — CLI, buildable now (no backend dependency)
Related: the ingestion-bug set (cli#67–#77) is on these same commands — they must keep working via aliases

Why

The naming is locked: the noun is data (not dataset), and the verbs are data ingest / data list / data delete:

• ingest, never push — "push" implies egress to a remote (git / cloud). This data stays on-prem, inside the customer's own cluster/workspace; ingest (pull-into-your-own-workspace) is the honest, reassuring verb for sensitive-data users.
• delete, never rm — the destructive verb is spelled out: beginner-clear and consistent with client … delete.

Scope

• Rename the command group dataset → data; verbs push → ingest, rm → delete (list unchanged).
• Keep dataset, push, rm as hidden aliases for one deprecation cycle — don't break existing scripts, docs, or the cli#67–dataset push: category-irrelevant flags are silently accepted and ignored (e.g. --target-size on tabular, --schema on images) #77 bug repros.
• Update help text, usage, examples, error messages, and shell completion to the new names; don't advertise the old ones.

Acceptance

• data ingest / data list / data delete work; dataset push / dataset rm still work (hidden, optionally with a one-line deprecation hint).
• Help/usage shows the new names; the aliases are not advertised.
• No behavior change beyond naming — the ingestion logic (and the cli#67–dataset push: category-irrelevant flags are silently accepted and ignored (e.g. --target-size on tabular, --schema on images) #77 fixes) is untouched.

Work Type: Feature · Squad: DevEx · Area: SDK (CLI) · Priority: P1