fix: studio CI test failures - fix simulateBrowser mock handlers

[Copilot]

Summary

Fixes all 9 failing tests in @objectstack/studio#test (CI run #24456193896) by correcting the simulateBrowser MSW mock handlers in apps/studio/src/mocks/simulateBrowser.ts.

Root Causes & Fixes

1. Data endpoint ignored query parameters (4 test failures)

Tests: api.test.ts (3 tests), api-discovery.test.ts (1 test)

The GET /data/:object handler called ql.find(params.object) without passing any query options. The client sends top, skip, sort, select, and filter parameters, but all were ignored — returning all records instead of the filtered/paginated subset.

Fix: Added parseQueryOptions() helper that parses URL search params into ObjectQL EngineQueryOptions (limit, offset, orderBy, fields, where), and passes them to ql.find().

2. Metadata types endpoint missing runtime types (2 test failures)

Tests: verify-metadata.test.ts — "should include agent/tool in metadata types"

The GET /meta handler used ql.registry.getRegisteredTypes() which only returns SchemaRegistry types (package, data, app, object), missing runtime types (agent, tool, etc.) registered by AIServicePlugin via MetadataService.

Fix: Now uses protocol.getMetaTypes() which merges both SchemaRegistry and MetadataService types.

3. Metadata items endpoint only queried SchemaRegistry (2 test failures)

Tests: verify-metadata.test.ts — "should list registered agents/tools"

The GET /meta/:type handler used ql.registry.listItems(type) which only returns SchemaRegistry items. Agents and tools are registered in MetadataService, not SchemaRegistry.

Fix: Now uses protocol.getMetaItems({ type }) which queries both registries.

4. Object list endpoint returned wrong format (1 test failure)

Test: verify-metadata.test.ts — "should fetch list of objects"

The GET /meta/object handler returned ql.getObjects() (which doesn't exist, defaulting to {}) instead of the spec-compliant { type: 'object', items: [...] } format.

Fix: Now uses protocol.getMetaItems({ type: 'object' }) which returns the correct format.

Verification

• ✅ All 56 studio tests pass (8/8 test files)
• ✅ Full monorepo test suite passes (85/85 tasks)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
objectstack-demo	Ready	Preview, Comment	Apr 15, 2026 1:51pm
spec	Ready	Preview, Comment	Apr 15, 2026 1:51pm

[Copilot]

Pull request overview

Fixes Studio CI failures by making the simulateBrowser MSW mock behave closer to the real ObjectStack HTTP API, especially for queryable data endpoints and protocol-compliant metadata endpoints.

Changes:

• Added query-string parsing for GET /api/v1/data/:object and passed the parsed options into ql.find(...).
• Switched metadata mocks (/api/v1/meta*) to use the protocol service (getMetaTypes/getMetaItems/getMetaItem) so runtime-registered metadata types/items are included.
• Documented the fix in the Studio changelog.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
apps/studio/src/mocks/simulateBrowser.ts	Adds parseQueryOptions() and updates MSW handlers to use query options for data find and protocol-backed metadata endpoints.
apps/studio/CHANGELOG.md	Adds a patch note describing the simulateBrowser mock handler fixes.

[Copilot]

parseQueryOptions() maps the sort query param to query.orderBy as a string array when the value is comma-separated (e.g. "-created_at"). EngineQueryOptions.orderBy is an array of SortNode objects ({ field, order }), and the in-memory driver’s applySort() ignores string items, so sorting won’t be applied for the common sort=-field form sent by ObjectStackClient.data.find(). Convert string tokens into SortNode objects (handle leading '-' for desc) instead of returning raw strings.

Suggested change

	try { query.orderBy = JSON.parse(val); } catch {
	query.orderBy = val.split(',').map((s: string) => s.trim());
	try {
	query.orderBy = JSON.parse(val);
	} catch {
	query.orderBy = val
	.split(',')
	.map((s: string) => s.trim())
	.filter(Boolean)
	.map((token: string) => ({
	field: token.startsWith('-') ? token.slice(1) : token,
	order: token.startsWith('-') ? 'desc' : 'asc',
	}));

[Copilot]

filter is JSON-parsed and merged into where via Object.assign(where, JSON.parse(val)). When the client sends an AST/array filter (it serializes arrays into the filter param), this produces a { "0": ..., "1": ... } object rather than a valid where condition, so filtering will silently fail. If the parsed value is an array (or already a FilterCondition shape), assign it to query.where directly rather than merging into an object.

[Copilot]

ObjectStackClient.data.find() can send aggregations (JSON) and groupBy (comma-separated) query params, but parseQueryOptions() currently treats unknown params as field filters and puts them into where. This breaks aggregation queries by turning control params into WHERE conditions. Add explicit parsing/forwarding for these keys (or explicitly ignore them) so they don’t end up in where.