feat(highlights): add channelDigests query

[idoshamun]

What

Adds a top-level read-only channelDigests GraphQL query that returns all enabled channel digests, resolved through GraphORM on the read replica and ordered by channel ASC, key ASC.

Changes

• src/schema/highlights.ts — New ChannelDigest GraphQL type (key, channel, frequency, enabled, resolved source) and the channelDigests: [ChannelDigest!]! query. Resolver mirrors the existing channelConfigurations style and filters to enabled = true at the DB level.
• src/graphorm/index.ts — Added a ChannelDigest GraphORM mapping. Extracted the shared source custom relation into a channelDigestSourceField constant reused by both ChannelDigest and the existing ChannelDigestConfiguration mappings to avoid duplication.
• __tests__/highlights.ts — Integration tests covering ordering across channels, resolved source, disabled-digest exclusion, and the empty-result case.

Key decisions

• Dedicated ChannelDigest type rather than reusing ChannelDigestConfiguration (which lacks channel/key and is shaped as a nested config sub-object).
• Minimal field set — excludes internal tuning fields (minHighlightScore, sentimentGroupIds, includeSentiment, targetAudience); these can be added later without a breaking change.
• Public, enabled-only, no args — matches channelConfigurations (no @auth). An includeDisabled arg can be added later if a client needs it.
• No DB migration, entity, or worker changes — purely additive GraphQL read.

Closes ENG-1633

---

Created by Huginn 🐦‍⬛

[pulumi]

🍹 The Update (preview) for dailydotdev/api/prod (at 858b298) was successful.

✨ Neo Code Review

Routine deployment of a new GraphQL query (`channelDigestConfigurations`) with a full image rollout and standard migration job rotation. ✅ Low Risk — confirm the underlying `ChannelDigest` table/entity is already present or a migration is included.

This is a routine application deployment rolling out commit feae556d (previously 8c1734aa). The PR adds a new channelDigestConfigurations GraphQL query that returns enabled ChannelDigest records ordered by channel and key, along with associated tests and AGENTS.md documentation guidance.

All deployment and cron job updates are purely image tag bumps to the new commit SHA. The migration jobs (both DB and Clickhouse) are replaced by new ones named with the new commit hash — this is the standard pattern for one-shot migration Jobs in this stack.

🔵 Info — The new vpc-native-api-db-migration-feae556d Job will run TypeORM migrations on deploy. The PR diff doesn't show migration files, so verify that the ChannelDigest entity and GQLChannelDigestConfiguration type already exist in the schema/database before merge, or that a migration is bundled in this commit.

Resource Changes

    Name                                                       Type                           Operation
+   vpc-native-api-clickhouse-migration-feae556d               kubernetes:batch/v1:Job        create
~   vpc-native-update-tag-materialized-views-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-update-highlighted-views-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-channel-highlights-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-expire-super-agent-trial-cron                   kubernetes:batch/v1:CronJob    update
~   vpc-native-hourly-notification-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-user-companies-cron                kubernetes:batch/v1:CronJob    update
~   vpc-native-deployment                                      kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-zombie-opportunities-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-daily-digest-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-channel-digests-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-generic-referral-reminder-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-update-current-streak-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-update-tags-str-cron                            kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-clickhouse-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-worker-job-deployment                           kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-stale-user-transactions-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-user-posts-analytics-refresh-cron               kubernetes:batch/v1:CronJob    update
~   vpc-native-rotate-daily-quests-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-private-deployment                              kubernetes:apps/v1:Deployment  update
~   vpc-native-materialize-yearly-best-post-archives-cron      kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-history-day-clickhouse-cron      kubernetes:batch/v1:CronJob    update
~   vpc-native-rotate-weekly-quests-cron                       kubernetes:batch/v1:CronJob    update
~   vpc-native-validate-active-users-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-analytics-clickhouse-cron          kubernetes:batch/v1:CronJob    update
~   vpc-native-user-profile-analytics-history-clickhouse-cron  kubernetes:batch/v1:CronJob    update
~   vpc-native-update-views-cron                               kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-images-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-expired-better-auth-sessions-cron         kubernetes:batch/v1:CronJob    update
~   vpc-native-channel-highlights-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-gifted-plus-cron                          kubernetes:batch/v1:CronJob    update
~   vpc-native-calculate-top-readers-cron                      kubernetes:batch/v1:CronJob    update
~   vpc-native-temporal-deployment                             kubernetes:apps/v1:Deployment  update
~   vpc-native-update-trending-cron                            kubernetes:batch/v1:CronJob    update
-   vpc-native-api-clickhouse-migration-8c1734aa               kubernetes:batch/v1:Job        delete
~   vpc-native-clean-zombie-users-cron                         kubernetes:batch/v1:CronJob    update
~   vpc-native-check-analytics-report-cron                     kubernetes:batch/v1:CronJob    update
~   vpc-native-generate-search-invites-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-sync-subscription-with-cio-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-deployment                  kubernetes:apps/v1:Deployment  update
... and 13 other changes

[idoshamun]

Why do we need both ChannelDigestConfiguration and ChannelDigest? Seems like duplicates. We can just reuse the existing one

[idoshamun]

Good catch — they were indeed duplicates, both mapped from: 'ChannelDigest'. Consolidated into the single entity-aligned ChannelDigest type and pointed channelConfigurations.digest at it, dropping ChannelDigestConfiguration entirely (1fd09b4).

[idoshamun]

Update: rather than renaming the existing type, kept ChannelDigestConfiguration (and all existing names) exactly as-is and exposed the new query as channelDigestConfigurations: [ChannelDigestConfiguration!]!, reusing that type. src/graphorm/index.ts is now unchanged from base — the diff is purely the additive query + resolver + tests (858b298).