fix: move loadStatusConfig outside telemetry callback to restore context scope

After rebasing, the dataset management code references context.deployedState
outside the withCommandRunTelemetry callback where context was defined.
Move loadStatusConfig() before the callback so context is accessible in both
the telemetry wrapper and the dataset enrichment logic.

Author: Hweinstock

src/cli/commands/status/command.tsx

@@ -1,9 +1,9 @@
 import { ValidationError, serializeResult } from '../../../lib';
 import { getErrorMessage } from '../../errors';
-import { withCommandRunTelemetry } from '../../telemetry/cli-command-run.js';
-import { FilterState, FilterType, standardize } from '../../telemetry/schemas/common-shapes.js';
 import { getDatasetStatus } from '../../operations/dataset';
 import type { DatasetStatusResult } from '../../operations/dataset';
+import { withCommandRunTelemetry } from '../../telemetry/cli-command-run.js';
+import { FilterState, FilterType, standardize } from '../../telemetry/schemas/common-shapes.js';
 import { COMMAND_DESCRIPTIONS } from '../../tui/copy';
 import { requireProject } from '../../tui/guards';
 import type { ResourceStatusEntry } from './action';
@@ -137,8 +137,8 @@ export const registerStatus = (program: Command) => {
         }
 
         // Default path: show all resource types with deployment state
+        const context = await loadStatusConfig();
         const result = await withCommandRunTelemetry('status', telemetryAttrs, async () => {
-          const context = await loadStatusConfig();
           return handleProjectStatus(context, { targetName: cliOptions.target });
         });