saravanakumardb1 e0a904c7ea fix(cosmos): support composite indexes; add fleet_jobs (priorityOrder, createdAt) ... Azure Cosmos cannot serve a multi-field ORDER BY without a matching composite index (the local emulator is lenient, real Cosmos returns HTTP 400). The fleet listJobs() query orders by (priorityOrder, createdAt), which broke GET /api/fleet/metrics and /api/fleet/jobs on real Cosmos. - ContainerConfig gains an optional `compositeIndexes` field - container init applies it on create AND reconciles it onto existing containers (createIfNotExists never updates an existing index policy) - fleet_jobs declares the (priorityOrder ASC, createdAt ASC) composite index Verified live against Azure Cosmos: both endpoints now return 200. Generated with [Devin](https://cli.devin.ai/docs) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-05-30 23:07:06 -07:00
..
__tests__	feat: add package tests (58 new) + @bytelyst/fastify-core package	2026-02-12 22:17:17 -08:00
client.ts	fix(common): configure ESLint 9 and fix lint issues	2026-02-12 16:37:30 -08:00
containers.ts	fix(cosmos): support composite indexes; add fleet_jobs (priorityOrder, createdAt)	2026-05-30 23:07:06 -07:00
index.ts	fix(cosmos): support composite indexes; add fleet_jobs (priorityOrder, createdAt)	2026-05-30 23:07:06 -07:00
types.ts	fix(cosmos): support composite indexes; add fleet_jobs (priorityOrder, createdAt)	2026-05-30 23:07:06 -07:00