Add diagnostic logging for AI metadata visibility issue in Vercel deployment

[Claude]

After Vercel deployment, Studio sidebar shows incomplete AI metadata (missing agents/tools). Root cause unknown—could be service registry callback failure, metadata service unavailability, or timing issues during bootstrap.

Changes

• protocol.ts: Added console logging in getMetaTypes() and getMetaItems() to trace:

  • Services registry availability and size
  • Metadata service accessibility and method presence
  • Runtime types/items retrieval from metadata service
  • Final merged result counts

• plugin.ts: Fixed ObjectStackProtocolImplementation initialization to include missing feed service callback (3rd constructor parameter)

Diagnostic Flow

// protocol.ts - Now logs each step
async getMetaTypes() {
  const services = this.getServicesRegistry?.();
  console.log('[Protocol] services available:', !!services, 'size:', services?.size);
  
  const metadataService = services?.get('metadata');
  console.log('[Protocol] metadata service:', !!metadataService);
  
  if (metadataService?.getRegisteredTypes) {
    const runtimeTypes = await metadataService.getRegisteredTypes();
    console.log('[Protocol] runtime types:', runtimeTypes);
  }
}

This will expose whether the issue is in service registry access, metadata service registration, or the metadata itself. Once Vercel logs are available, a targeted fix can be implemented.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectstack-play	Ready	Preview, Comment	Apr 11, 2026 5:17am
spec	Ready	Preview, Comment	Apr 11, 2026 5:17am