CLI does not print duration for databases create / databases load (and possibly other commands)

[divs1101-maker]

Summary

hotdata databases create and hotdata databases load (and likely other mutating commands) print no elapsed-time/duration in their output, unlike hotdata query (prints (N rows, X ms)-style timing) and async job flows (which expose created_at/completed_at on hotdata jobs <id>).

This makes it impossible to report or reason about how long a step took without instrumenting the shell call externally.

Repro

hotdata databases create --catalog airbnb --name sf-airbnb-listings
# -> prints id/name/catalog/connection/expires_at, no duration

hotdata databases load --catalog airbnb --table listings --url https://hotdata.dev/data/sf-airbnb-listings.parquet
# -> prints "Table loaded", full_name, rows — no duration

Compare to hotdata query "...", which prints elapsed time, and hotdata search "...", which prints (N rows, X ms).

Expected

Every command that does non-trivial server-side work (databases create, databases load/tables load, databases fork, search create sync path, etc.) prints how long it took, consistent with query and search.

Impact

Users (and agents driving the CLI) cannot report accurate step timings for a workflow without wrapping every invocation in an external timer. This came up while summarizing the steps of a load-and-index workflow: query and search timings were available, but databases create and databases load had none to report.

Environment

• hotdata CLI v0.34.1
• Reported by: divya@hotdata.dev