fix(databases): surface the id change when load recreates a managed database

[eddietejeda]

Summary

Loading an undeclared table into a managed database triggers an auto-declare path that delete + recreates the database (managed DBs have no add-table endpoint) — which mints a new database id. This was silent unless existing tables had synced data, so:

• the id printed by databases create goes stale after the next load of a new table, and
• databases delete <create-time-id> then fails with "no database with id".

I hit this directly while testing: databases create --catalog X printed one id, but after databases load the database was listed under a different id, and delete-by-printed-id failed.

Root cause

databases create is correct — its returned id matches databases list immediately (verified). The id only changes inside tables_load's recreate path (src/databases.rs), and that change was never surfaced when there was no synced data to warn about.

Fix

• Emit a clear note when load recreates the database, showing id <old> → <new> and pointing users to reference managed databases by catalog (stable), not the create-time id.
• Document the same in the managed-database workflow (references/WORKFLOWS.md): auto-declaring a new table recreates the DB and changes its id; reference by catalog, or declare tables up front with databases create --table ….

No server change needed; this is a transparency fix for an inherent consequence of the recreate workaround.

Verification (production)

$ hotdata databases create --catalog probe_notice      # id A
$ hotdata databases load --catalog probe_notice --table t --file probe.parquet
note: table 't' was not declared — recreated database 'probe_notice' to add it
(id dbidybn82eo… → dbidsqfb9xo…). … reference them by catalog ('probe_notice'),
not the create-time id.
$ hotdata databases delete probe_notice                 # delete by catalog works
Database deleted.

cargo build/clippy/fmt clean; databases test suite green (23 passed).

[claude]

Focused transparency fix. The recreate-path note is correctly gated on the "not declared" branch, the id old→new values and catalog fallback match the adjacent synced-data block, and the style follows existing conventions. LGTM.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/databases.rs	0.00%	8 Missing ⚠️

📢 Thoughts on this report? Let us know!