Align client with spec API protocol and add metadata discovery methods

[Copilot]

Client's discovery interface used custom routes object incompatible with spec's GetDiscoveryResponseSchema. Missing metadata discovery methods exposed by server.

Changes

Discovery interface alignment

• Replace custom DiscoveryResult.routes with spec-compliant version, apiName, capabilities, endpoints
• Use GetDiscoveryResponse type from @objectstack/spec/api
• Remove dynamic route resolution; client now uses conventional paths (/api/v1/data, /api/v1/meta, /api/v1/ui)

Metadata discovery methods

• Add meta.getTypes() - list available metadata types
• Add meta.getItems(type) - list items of specific type
• Add meta.getItem(type, name) - get specific metadata item
• Deprecate meta.getObject() in favor of getItem('object', name)

Type exports

• Export GetDiscoveryResponse, GetMetaTypesResponse, GetMetaItemsResponse from spec

Before/After

// Before: Custom discovery format
const discovery = await client.connect();
// { routes: { data: '/api/v1/data', ... }, capabilities: { ... } }

// After: Spec-compliant format
const discovery = await client.connect();
// { version: 'v1', apiName: 'ObjectStack', capabilities: [...] }

// New: Metadata discovery
const types = await client.meta.getTypes();        // { types: ['object', 'plugin', ...] }
const items = await client.meta.getItems('object'); // { type: 'object', items: [...] }
const item = await client.meta.getItem('object', 'customer'); // object definition

Original prompt

按照最新的plugin-hono-server改动和spec api规范，调整 @objectstack/client

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
spec	Canceled		Feb 2, 2026 9:36am