Verify multi-app code locations deployment

## Pre-requisites
- Coolify should have auto-deployed after git push
- Wait 2-3 minutes for deployment to complete

## Step 1: Access Dagster UI
1. Navigate to https://dagster.data.jettaintelligence.com/dagster
2. Login via Jetta SSO if prompted
3. Verify the main Dagster UI loads without errors

## Step 2: Verify Code Locations
1. Click on "Deployment" in the left sidebar (or look at top nav)
2. Verify **4 code locations** are listed:
   - `sable` - should show LOADED status
   - `meridian` - should show LOADED status
   - `market_data` - should show LOADED status
   - `jetta_data_orch_legacy` - should show LOADED status
3. If any show ERROR, note the error message

## Step 3: Verify Sable Assets
1. Click on "Assets" in the left sidebar
2. Filter by code location: select "sable"
3. Verify these assets exist:
   - `pnl_silver` (group: sable_pnl)
   - `pnl_gold` (group: sable_pnl)
4. Click on `pnl_silver` and verify:
   - Tags include: app=sable, domain=pnl, layer=silver
   - Compute kind shows "dbt"

## Step 4: Verify Sable Sensor
1. Click on "Automation" or "Sensors" in the sidebar
2. Look for `pending_job_sensor` in the sable code location
3. Verify the sensor is visible (may be stopped by default)
4. Check description mentions "process_job records"

## Step 5: Verify Jobs Have Failure Hooks
1. Click on "Jobs" in the sidebar
2. Look for these jobs in jetta_data_orch_legacy:
   - `daily_fred_refresh`
   - `daily_intrinio_refresh`
   - `weekly_fundamentals_refresh`
   - `full_data_refresh`
3. Click on any job and verify it has hooks configured
   (may show in job details or config)

## Step 6: Check for Errors
1. Click on "Runs" in the sidebar
2. Check if there are any recent failed runs
3. Look at the Dagster logs for any startup errors

1. Dagster UI loads successfully after SSO login
2. All 4 code locations show "LOADED" status with no errors
3. Sable code location contains pnl_silver and pnl_gold assets in sable_pnl group
4. pending_job_sensor is visible in the Sable code location
5. All scheduled jobs exist and have failure hooks attached
6. No startup errors or code location loading failures