VSKI v0.7.1

Dashboard: database-scoped collections (web UI)

The standalone dashboard now works with the per-database collection registry introduced in v0.7.0. Browsing a collection that lives outside the default database previously failed with {"error":"Collection not found"} - every dashboard request resolved in default, where the collection does not exist.

• Sidebar collection links carry their database (/collections/<name>?db=<dbName>), so the same bare name in two databases is addressable and never ambiguous.
• Collection pages resolve the database from the link (falling back to the default db when the URL is unqualified) and issue every records operation - list, create, update, delete, bulk - through the db-scoped SDK namespace.
• Collection settings (schema/indexes/views/rules editor) and the API Rules page PATCH the collection through its own database; relation pickers load their options from the same db.
• System collections (_api_keys, _sql_snippets, …) keep resolving from any namespace, unchanged.

SDK (TS/JS) v2.0.4

Published to the package registry. client.db(name) now also exposes the settings namespace (client.db(name).settings.collections.*) so registry operations resolve within the named database; records namespaces were already scoped. This is the version the dashboard ships against.

Compatibility

No API or storage changes - v0.7.1 is the dashboard + SDK companion release for the v0.7.0 per-database registry.