Fix query tests after schema migration to object-based filter syntax

[Copilot]

Query schema evolved from array-based to object-based filter syntax (MongoDB-style operators), but tests still used old array format causing 40+ validation failures.

Changes

Removed obsolete schema references

• Deleted imports and tests for FilterOperator and LogicOperator (removed from schema)

Migrated join ON clauses (35 instances)

// Before
on: ['order.customer_id', '=', 'c.id']

// After  
on: { 'order.customer_id': { $eq: { $field: 'c.id' } } }

// Complex conditions
on: { $and: [
  { 'order.customer_id': { $eq: { $field: 'c.id' } } },
  { 'order.status': 'active' }
] }

Migrated HAVING clauses (8 instances)

// Before
having: ['order_count', '>', 5]

// After
having: { order_count: { $gt: 5 } }

Fixed field name

• sort → orderBy (schema property)

Result: 105/105 query tests passing

Original prompt

引用: https://github.com/objectstack-ai/spec/actions/runs/21327218395/job/61386508022#step:8:1

---

💬 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	Review	Updated (UTC)
spec	Ready	Preview, Comment	Jan 25, 2026 5:15am

[Copilot]

Pull request overview

This PR updates the query tests to align with the new object-based filter DSL and the current QuerySchema (notably orderBy and FilterConditionSchema-based joins and havings), resolving the validation failures introduced by the schema migration.

Changes:

• Removed obsolete tests and imports for the now-absent FilterOperator and LogicOperator enums.
• Migrated all join on clauses from array-based syntax to FilterConditionSchema object syntax, including support for $and and $field references.
• Migrated all having clauses from array-based comparison tuples to object-based filter conditions and updated tests to use orderBy instead of sort where applicable.