Fix TypeScript build errors in ObjectQL API usage and chart types

[Copilot]

Description

CI build failed with TypeScript errors in support and UI packages. Root causes: incorrect ObjectQL API namespace usage (pre-migration patterns), invalid sort parameter format, missing null guards on optional hook context, and non-spec-compliant chart types.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• CI/CD update

Related Issues

CI Failure: https://github.com/objectstack-ai/hotcrm/actions/runs/21545139473/job/62085377886#step:7:1

Changes Made

ObjectQL API Namespace Corrections (10 occurrences)

// Before: Direct method access (deprecated)
await ctx.db.update('Case', id, data);
await ctx.db.create('SLAMilestone', data);

// After: Namespaced doc operations
await ctx.db.doc.update('Case', id, data);
await ctx.db.doc.create('SLAMilestone', data);

Sort Parameter Type Alignment (3 occurrences)

// Before: Tuple array format (type mismatch)
sort: [['Priority', 'asc']]

// After: Simple field name per ObjectQLFindOptions
sort: 'Priority'

Null Safety for Hook Context (2 occurrences)

// Before: Unsafe access to optional ctx.old
if (oldArticle.Status !== article.Status)

// After: Null guard
if (oldArticle && oldArticle.Status !== article.Status)

Chart Type Spec Compliance (2 occurrences)

// 'list' not in ChartTypeSchema enum - use 'table'
type: 'table'  // was: 'list'

Testing

• Unit tests pass (npm test)
• Linting passes (npm run lint)
• Build succeeds (npm run build)
• Manual testing completed
• New tests added (if applicable)

Screenshots

N/A - Build fix only

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Notes

All changes align with @objectstack/spec v0.7.2 protocol requirements. No behavioral changes - purely type safety and API compliance fixes.

Original prompt

引用: https://github.com/objectstack-ai/hotcrm/actions/runs/21545139473/job/62085377886#step:7:1

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
hotcrm	Ready	Preview, Comment	Jan 31, 2026 1:35pm

[Copilot]

Pull request overview

This PR fixes TypeScript build errors caused by incorrect ObjectQL API usage, invalid sort parameter formats, missing null guards, and non-compliant chart types. The changes align with @objectstack/spec v0.7.2 protocol requirements and are purely type safety and API compliance fixes with no behavioral changes.

Changes:

• Updated ObjectQL API calls to use namespaced ctx.db.doc.* methods instead of deprecated direct methods
• Converted sort parameters from tuple array format to simple field names per ObjectQLFindOptions schema
• Added null safety guards for optional ctx.old context in hook handlers
• Changed chart type from non-spec-compliant 'list' to 'table'

Reviewed changes

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

File	Description
packages/support/src/hooks/case.hook.ts	Fixed ObjectQL API namespace (7 db.doc.update calls, 1 db.doc.create call) and converted 3 sort parameters from tuple arrays to simple strings
packages/support/src/hooks/knowledge.hook.ts	Added null guards for ctx.old access and fixed 1 ObjectQL db.doc.update call
packages/ui/src/dashboard/sales_intelligence.dashboard.ts	Changed 2 widget types from 'list' to 'table' for spec compliance