Verify Dagster multi-app code locations deployment

## Step 1: Access Dagster UI
1. Open https://dagster.data.jettaintelligence.com/dagster
2. Login via Jetta SSO when prompted
3. Confirm Dagster UI loads without errors

## Step 2: Verify Code Locations (Critical)
1. Click "Deployment" in the left sidebar
2. Verify exactly **4 code locations** are listed:
   - `sable` - status should be LOADED
   - `meridian` - status should be LOADED
   - `market_data` - status should be LOADED
   - `jetta_data_orch_legacy` - status should be LOADED
3. If any show ERROR status, expand to see error message and record it

## Step 3: Verify Sable Assets
1. Click "Assets" in left sidebar
2. Filter by code location "sable" (if filter available)
3. Confirm these assets exist:
   - `pnl_silver` (in group "sable_pnl")
   - `pnl_gold` (in group "sable_pnl")
4. Click on `pnl_silver` asset
5. Verify metadata shows:
   - Compute kind: "dbt"
   - Tags include: app=sable, layer=silver

## Step 4: Verify Sable Sensor
1. Click "Automation" or "Sensors" in sidebar
2. Find `pending_job_sensor` in sable code location
3. Confirm sensor is visible (it may be stopped/off by default - that's OK)
4. Check description mentions polling for pending process_job records

## Step 5: Verify Legacy Jobs Exist
1. Click "Jobs" in sidebar
2. In jetta_data_orch_legacy, confirm these jobs exist:
   - `daily_fred_refresh`
   - `daily_intrinio_refresh`
   - `weekly_fundamentals_refresh`
   - `full_data_refresh`

## Step 6: Check for Startup Errors
1. Click "Runs" in sidebar
2. Look for any recent failed runs with startup-related errors
3. Check if there are code location loading errors in run logs

1. Dagster UI loads successfully after SSO login
2. All 4 code locations show LOADED status (no errors)
3. Sable code location contains pnl_silver and pnl_gold assets with correct tags
4. pending_job_sensor is visible in Sable code location
5. All 4 legacy jobs exist in jetta_data_orch_legacy
6. No code location loading errors or startup failures