feat: Integrate platform-objects and update references in studio and tests

Author: hotlong

apps/studio/package.json

@@ -35,6 +35,7 @@
     "@objectstack/hono": "workspace:*",
     "@objectstack/metadata": "workspace:*",
     "@objectstack/objectql": "workspace:*",
+    "@objectstack/platform-objects": "workspace:*",
     "@objectstack/plugin-audit": "workspace:*",
     "@objectstack/plugin-auth": "workspace:*",
     "@objectstack/plugin-msw": "workspace:*",

apps/studio/src/mocks/createKernel.ts

@@ -11,15 +11,14 @@ import { MetadataPlugin } from '@objectstack/metadata';
 import { AIServicePlugin } from '@objectstack/service-ai';
 import { FeedServicePlugin } from '@objectstack/service-feed';
 
-// System object definitions — resolved via Vite aliases to plugin source (no runtime deps)
 import {
     SysUser, SysSession, SysAccount, SysVerification,
     SysOrganization, SysMember, SysInvitation,
     SysTeam, SysTeamMember,
     SysApiKey, SysTwoFactor,
-} from '@objectstack/plugin-auth/objects';
-import { SysRole, SysPermissionSet } from '@objectstack/plugin-security/objects';
-import { SysAuditLog } from '@objectstack/plugin-audit/objects';
+} from '@objectstack/platform-objects/identity';
+import { SysRole, SysPermissionSet } from '@objectstack/platform-objects/security';
+import { SysAuditLog } from '@objectstack/platform-objects/audit';
 
 /** All system objects from auth, security, and audit plugins */
 const SYSTEM_OBJECTS = [

apps/studio/vite.config.ts

@@ -17,10 +17,6 @@ export default defineConfig({
       'react': path.resolve(__dirname, './node_modules/react'),
       'react-dom': path.resolve(__dirname, './node_modules/react-dom'),
       '@': path.resolve(__dirname, './src'),
-      // System object definitions — resolve to plugin source (no runtime deps)
-      '@objectstack/plugin-auth/objects': path.resolve(__dirname, '../../packages/plugins/plugin-auth/src/objects/index.ts'),
-      '@objectstack/plugin-security/objects': path.resolve(__dirname, '../../packages/plugins/plugin-security/src/objects/index.ts'),
-      '@objectstack/plugin-audit/objects': path.resolve(__dirname, '../../packages/plugins/plugin-audit/src/objects/index.ts'),
       'node:fs/promises': path.resolve(__dirname, './mocks/node-polyfills.ts'),
       'node:fs': path.resolve(__dirname, './mocks/node-polyfills.ts'),
       'node:events': path.resolve(__dirname, './mocks/node-polyfills.ts'),

apps/studio/vitest.config.ts

@@ -7,10 +7,6 @@ import react from '@vitejs/plugin-react';
 import { TanStackRouterVite } from '@tanstack/router-plugin/vite';
 import path from 'path';
 
-// NOTE: Keep the resolve.alias block in sync with vite.config.ts.
-// Studio depends on package subpaths (e.g. `@objectstack/plugin-auth/objects`)
-// that are not declared in those packages' exports maps; we alias them to
-// source files here so both `vite dev/build` and `vitest` can resolve them.
 const polyfillPath = path.resolve(__dirname, './mocks/node-polyfills.ts');
 
 export default defineConfig({
@@ -43,10 +39,6 @@ export default defineConfig({
       'react': path.resolve(__dirname, './node_modules/react'),
       'react-dom': path.resolve(__dirname, './node_modules/react-dom'),
       '@': path.resolve(__dirname, './src'),
-      // System object definitions — resolve to plugin source (no runtime deps)
-      '@objectstack/plugin-auth/objects': path.resolve(__dirname, '../../packages/plugins/plugin-auth/src/objects/index.ts'),
-      '@objectstack/plugin-security/objects': path.resolve(__dirname, '../../packages/plugins/plugin-security/src/objects/index.ts'),
-      '@objectstack/plugin-audit/objects': path.resolve(__dirname, '../../packages/plugins/plugin-audit/src/objects/index.ts'),
       // Node built-ins stubbed for browser-like test env
       'node:fs/promises': polyfillPath,
       'node:fs': polyfillPath,

content/docs/concepts/north-star.mdx

@@ -528,7 +528,7 @@ without explicit project-level buy-in.
 
 - <AlertTriangle className="inline" /> **JSON is not an authoring form.** Phase 1 authors produce metadata via TypeScript and the CLI. If you find yourself editing JSON payloads directly in `sys_metadata`, you are patching around a missing CLI affordance.
 - <AlertTriangle className="inline" /> **TS is not a wire form.** ObjectOS runtimes never consume `.ts` files directly. The only runtime inputs are a compiled `dist/objectstack.json` or the control plane's Artifact API response (also JSON).
-- <AlertTriangle className="inline" /> **No bypassing Zod for TS <-> JSON conversion.** Any hand-rolled serializer will diverge from the schema on the Nth protocol bump and silently corrupt data. `z.toJSONSchema()` + `schema.parse()` **is** the contract.
+- <AlertTriangle className="inline" /> **No bypassing Zod for TS-to-JSON conversion.** Any hand-rolled serializer will diverge from the schema on the Nth protocol bump and silently corrupt data. `z.toJSONSchema()` + `schema.parse()` **is** the contract.
 
 ### Prior anti-patterns (still in force)
 

packages/objectql/src/plugin.integration.test.ts

@@ -880,7 +880,7 @@ describe('ObjectQLPlugin - Metadata Service Integration', () => {
       // Assert — sys_metadata should have been queried
       const metaQuery = findCalls.find((c) => c.object === 'sys_metadata');
       expect(metaQuery).toBeDefined();
-      expect(metaQuery!.query.where).toEqual({ state: 'active' });
+      expect(metaQuery!.query.where).toEqual({ state: 'active', env_id: null });
 
       // Assert — items should be restored into the registry
       const registry = (kernel.getService('objectql') as any).registry;

packages/objectql/src/protocol-meta.test.ts

@@ -172,7 +172,7 @@ describe('ObjectStackProtocolImplementation - Metadata Persistence', () => {
 
             expect(result.item).toEqual(sampleApp);
             expect(mockEngine.findOne).toHaveBeenCalledWith('sys_metadata', {
-                where: { type: 'app', name: 'test_app', state: 'active' }
+                where: { type: 'app', name: 'test_app', state: 'active', env_id: null }
             });
         });
 
@@ -272,7 +272,7 @@ describe('ObjectStackProtocolImplementation - Metadata Persistence', () => {
             // DB *is* queried (always-merge semantics) so seeded metadata
             // surfaces even when the registry already has unrelated items.
             expect(mockEngine.find).toHaveBeenCalledWith('sys_metadata', {
-                where: { type: 'app', state: 'active' }
+                where: { type: 'app', state: 'active', env_id: null }
             });
         });
 
@@ -291,7 +291,7 @@ describe('ObjectStackProtocolImplementation - Metadata Persistence', () => {
             expect(result.items).toHaveLength(1);
             expect(result.items[0]).toEqual(sampleApp);
             expect(mockEngine.find).toHaveBeenCalledWith('sys_metadata', {
-                where: { type: 'app', state: 'active' }
+                where: { type: 'app', state: 'active', env_id: null }
             });
         });
 
@@ -370,7 +370,7 @@ describe('ObjectStackProtocolImplementation - Metadata Persistence', () => {
             await protocol.loadMetaFromDb();
 
             expect(mockEngine.find).toHaveBeenCalledWith('sys_metadata', {
-                where: { state: 'active' }
+                where: { state: 'active', env_id: null }
             });
         });