fix: pass absolute time range to queryMetricsMeta

When --period specifies an absolute range (e.g. 2026-04-01..2026-05-01),
timeRangeToApiParams returns {start, end} with no statsPeriod. Previously
only statsPeriod was forwarded to queryMetricsMeta, causing it to silently
fall back to 7d and potentially miss the target metric.

Author: MathurAditya724

src/commands/explore.ts

@@ -702,7 +702,7 @@ export const exploreCommand = buildListCommand("explore", {
         },
         () =>
           queryMetricsMeta(org, {
-            statsPeriod: metaParams.statsPeriod,
+            ...metaParams,
             project,
           })
       );

src/lib/api/discover.ts

@@ -103,6 +103,8 @@ export async function queryMetricsMeta(
   orgSlug: string,
   options?: {
     statsPeriod?: string;
+    start?: string;
+    end?: string;
     project?: string;
   }
 ): Promise<MetricMeta[]> {
@@ -116,7 +118,12 @@ export async function queryMetricsMeta(
       fields: ["metric.name", "metric.type", "metric.unit"],
       dataset: "metricsEnhanced",
       query,
-      statsPeriod: options?.statsPeriod ?? "7d",
+      statsPeriod:
+        options?.start || options?.end
+          ? undefined
+          : (options?.statsPeriod ?? "7d"),
+      start: options?.start,
+      end: options?.end,
       limit: 100,
     },
     100