fix: restore job filters by resolving tags once

src/jobs/jobs.service.ts

@@ -305,7 +305,9 @@ export class JobsService {
       ]);
       const configs = new JobFilterConfigsEntity({
         ...(await this.addTeamRange(values)),
-        tags: popularTags.map(tag => tag.name),
+        // The scoped values already contain valid tags. Popularity only narrows
+        // their ordering/selection and must not take down every filter on failure.
+        ...(popularTags ? { tags: popularTags.map(tag => tag.name) } : {}),
       }).getProperties();
       await this.cacheManager?.set(
         cacheKey,

src/postgres/tag.repository.ts

@@ -295,20 +295,23 @@ export class TagRepository {
           GROUP BY tag_slug
           HAVING count(DISTINCT job.job_node_id) >= 1
             AND count(DISTINCT job.job_node_id) < $1
+        ), canonical_tags AS MATERIALIZED (
+          -- Resolve each tag once. A lateral ORDER BY id / LIMIT lookup can
+          -- scan the graph primary key separately for every popular tag.
+          SELECT DISTINCT ON (node.properties ->> 'normalizedName')
+            node.id,
+            node.properties,
+            node.properties ->> 'normalizedName' AS tag_slug
+          FROM graph_nodes node
+          WHERE node.label = 'Tag'
+          ORDER BY node.properties ->> 'normalizedName', node.id
         ), ranked AS MATERIALIZED (
           SELECT
             tag.id AS canonical_id,
             tag.properties,
             popularity.job_count
           FROM popularity
-          JOIN LATERAL (
-            SELECT node.id, node.properties
-            FROM graph_nodes node
-            WHERE node.label = 'Tag'
-              AND node.properties ->> 'normalizedName' = popularity.tag_slug
-            ORDER BY node.id
-            LIMIT 1
-          ) tag ON true
+          JOIN canonical_tags tag ON tag.tag_slug = popularity.tag_slug
         )
         SELECT properties
         FROM ranked