docs: unify API query syntax with Spec canonical format

[Copilot]

Documentation for query syntax and IDataEngine contract diverged from the canonical @objectstack/spec schemas — using legacy filters/tuple/sort/group_by/aggregate naming instead of the actual QuerySchema and EngineQueryOptionsSchema definitions.

query-syntax.mdx — full rewrite

• All examples use where + $op object syntax, replacing tuple/三元组 format
• sort → orderBy, group_by → groupBy, aggregate → aggregations array, expand → Record<string, QueryAST>
• Interface definition matches actual QueryAST type
• Added coverage for search, joins, windowFunctions, cursor, distinct

data-engine.mdx — full rewrite

• Interface matches real IDataEngine: find/findOne/insert/update/delete/count/aggregate
• Option types match canonical schemas (EngineQueryOptions, EngineUpdateOptions, etc.)
• Documents optional capabilities: vectorFind, batch, execute

Legacy compatibility sections

Both docs now include explicit callouts: tuple/filters syntax is UI-builder input only — must be converted via parseFilterAST() before entering the protocol.

// Before (legacy — UI builder output only)
{ filters: [['status', '=', 'active'], ['amount', '>', 50000]], sort: [{ field: 'name', order: 'asc' }] }

// After (canonical — protocol format)
{ where: { status: 'active', amount: { $gt: 50000 } }, orderBy: [{ field: 'name', order: 'asc' }] }

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
objectstack-play	Ready	Preview, Comment	Mar 27, 2026 3:50am
spec	Ready	Preview, Comment	Mar 27, 2026 3:50am