Fix this issue: No input sanitization on path-segment parameters groupName/assetType. Slashes or encoded chars could cause routing issues. Add encodeURIComponent in endpoint builders.

Location: src/renderer/lib/api-client/endpoints.ts (lines 557)
Problem: groupName and assetType are interpolated directly into URL path segments without encoding. Group names containing slashes, spaces, or special chars will break routing or hit wrong endpoints.
Current behavior: URL path is malformed. The slash in the group name creates extra path segments, causing 404 or routing to unintended endpoints.
Expected: All path parameters should be wrapped in encodeURIComponent() to safely handle special characters.
Steps to reproduce: Create a version group with name 'my model/v2'. Then call ListVersions('model', 'my model/v2'). The URL becomes `.../versions/model/my model/v2` which routes to the wrong endpoint.

Provide a code fix.

Fix this issue: Migration uses sqlite_master, breaking Postgres. AGENTS.md says both SQLite and Postgres are supported. Use dialect-agnostic table existence check via sa.inspect.

Location: api/alembic/versions/a3d2e5f8c901_create_asset_versions_table.py (lines 27)
Problem: The Alembic migration hard-codes a SQLite-only system table query (sqlite_master) to check if the table exists, which fails on Postgres deployments.
Current behavior: Migration fails with a SQL error on Postgres: relation 'sqlite_master' does not exist.
Expected: Migration should run successfully on both SQLite and Postgres using dialect-agnostic introspection.
Steps to reproduce: Run `alembic upgrade head` against a PostgreSQL database. The query `SELECT name FROM sqlite_master WHERE type='table' AND name=:name` will raise an error because sqlite_master doesn't exist in Postgres.

Provide a code fix.

Fix this issue: Endpoint URL params not encoded in Resolve builder. Tag/version values with special chars corrupt query string. Use encodeURIComponent on param values.

Location: src/renderer/lib/api-client/endpoints.ts (lines 577)
Problem: The Resolve endpoint builder interpolates tag and version values directly into query string parameters without encoding. Tags containing '&' or '=' could corrupt the URL.
Current behavior: Query string corruption: extra parameters injected into the URL, potentially causing wrong behavior on the backend.
Expected: Use encodeURIComponent() for tag and version values: `tag=${encodeURIComponent(tag)}`.
Steps to reproduce: Call Endpoints.AssetVersions.Resolve('model', 'group', 'tag=evil&admin=true'). The resulting URL has injected query parameters.

Provide a code fix.

Fix this issue: DatasetCard versionGroups prop is untyped (no TypeScript interface). Props are all untyped in this component. Add explicit prop types for versionGroups.

Location: src/renderer/components/Data/DatasetCard.tsx (lines 35)
Problem: The DatasetCard component destructures props without TypeScript interface. The new versionGroups prop defaults to [] but has no type annotation, violating AGENTS.md strict typing rule.
Current behavior: No compile-time type checking on versionGroups prop. Passing wrong shape data won't be caught at build time.
Expected: AGENTS.md says 'Avoid any. Define interfaces for all props and API responses to ensure type safety.' A Props interface should be defined.
Steps to reproduce: Review DatasetCard.tsx:35-40. All props including the new versionGroups are untyped destructured parameters.

Provide a code fix.

Fix this issue: Duplicate index definitions between ORM model and migration. Same indexes defined in __table_args__ and migration. Remove from one location to avoid conflicts.

Location: api/transformerlab/shared/models/models.py (lines 314)
Problem: Index 'idx_asset_versions_group', 'idx_asset_versions_tag', and 'idx_asset_versions_asset_id' are defined in both the Alembic migration and the ORM __table_args__. Additionally, the migration creates extra single-column indexes (ix_asset_versions_asset_type, etc.) that overlap with columns already having index=True in the ORM model.
Current behavior: Redundant index definitions that could cause conflicts during autogeneration of future migrations, or errors if Alembic tries to create indexes that already exist.
Expected: Indexes should be defined in one authoritative place (preferably the ORM model) and the migration should be auto-generated from it.
Steps to reproduce: Compare indexes in the migration (lines 47-58) with __table_args__ in models.py (lines 314-318) and column-level index=True attributes (lines 301-308).

Provide a code fix.

Fix this issue: Silent failure on version group augmentation in model and data list. Bare except catches all errors and only prints. Add proper logging instead of print.

Location: api/transformerlab/routers/model.py (lines 833)
Problem: Both model_local_list and dataset_list catch all exceptions from version group augmentation with a broad `except Exception` and only print a warning. Database connection failures, import errors, or schema mismatches are silently swallowed.
Current behavior: Version group data silently missing from responses. Only a print statement indicates the failure. No structured logging for monitoring/alerting.
Expected: Use the application logger (not print) at WARNING level, and consider whether some errors (like DB connection failures) should propagate.
Steps to reproduce: Break the asset_versions table (e.g., drop it). Call GET /model/list. The warning is printed to stdout but no error is visible to API callers or monitoring.

Provide a code fix.