fix(runtime): provision sys_metadata table in per-project kernels

The artifact-kernel-factory was passing 'registerSystemObjects: false' to
MetadataPlugin, claiming the control plane owned metadata storage. But
ADR-0005's overlay flow (saveMetaItem in objectql/protocol.ts) writes
customization overlay rows to sys_metadata on the same engine the
protocol is attached to — for per-project kernels that's the project DB.

Result: any PUT /api/v1/meta/{view,dashboard}/... against a cloud
project deployment errored with 'no such table: sys_metadata', e.g.
when a user clicked 'Create View' in Studio:

  {
    "error": "Failed to persist customization overlay to sys_metadata:
              SQLITE_UNKNOWN: SQLite error: no such table: sys_metadata.
              In-memory registry was updated but will be lost on restart.",
    "code": "overlay_persistence_failed"
  }

Flip to true so ObjectQLPlugin.syncRegisteredSchemas provisions the
sys_metadata + sys_metadata_history tables on first cold-start. Both
are project-scoped (project_id column is set on every write), so
multi-project DBs and shared DBs remain correctly isolated.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: hotlong

packages/runtime/src/cloud/artifact-kernel-factory.ts

@@ -17,7 +17,11 @@
  *                              as the `'cloud'` datasource so AuthPlugin's
  *                              identity manifest resolves locally.
  *   • ObjectQLPlugin
- *   • MetadataPlugin (no system-object registration)
+ *   • MetadataPlugin (registers `sys_metadata` + `sys_metadata_history` on
+ *                     the project DB — required by ADR-0005: customization
+ *                     overlays such as user-created views/dashboards are
+ *                     persisted by ObjectStackProtocolImplementation on the
+ *                     per-project engine, so the table must exist there).
  *   • AuthPlugin    — per-project, derives an HKDF secret from
  *                     `OS_AUTH_SECRET` + projectId. Each project owns its
  *                     own `sys_user/sys_session/...` tables in its own
@@ -128,7 +132,15 @@ export class ArtifactKernelFactory implements ProjectKernelFactory {
             watch: false,
             projectId: projectId,
             organizationId: project.organization_id,
-            registerSystemObjects: false,
+            // ADR-0005: customization overlays (user-created views, dashboards,
+            // edited objects, ...) are persisted by
+            // ObjectStackProtocolImplementation.saveMetaItem on whichever
+            // engine the protocol is attached to. For per-project kernels that
+            // means the project's own DB, so the sys_metadata + history tables
+            // MUST be provisioned here. The previous `false` setting caused
+            // "no such table: sys_metadata" errors on any PUT /api/v1/meta/*
+            // call (e.g. Studio "Create View") against a project deployment.
+            registerSystemObjects: true,
         }));
 
         // Per-project AuthPlugin — only when an OS_AUTH_SECRET base is