Update upcoming meeting alert to better display cascade information

Refactor upcoming meeting alert component to update the cascade prompt table structure and adjust end-to-end tests to reflect the changes in column count and content assertions.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 77cfe984-2c65-4152-bb7a-0df28274fe66
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Event-Id: 9509e0a2-e6ad-4b70-8d04-56b729a8f67c
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/c3c252e4-c83d-40ca-9fff-99a3ea60701e/77cfe984-2c65-4152-bb7a-0df28274fe66/8BABrKh
Replit-Helium-Checkpoint-Created: true

artifacts/tx-os/tests/executive-meetings-upcoming-alert.spec.mjs

@@ -1092,7 +1092,11 @@ test("Cascade prompt UI: Shift sends cascadeFollowing=true; Keep sends false", a
   // From → To). The leading "#" index column was dropped because the
   // dailyNumber already gives the user a stable identifier.
   const followerCells = followerRow.locator("td");
+  await expect(followerCells).toHaveCount(3);
   await expect(followerCells.nth(0)).toHaveText(String(follower.dailyNumber));
+  await expect(followerCells.nth(1)).toContainText(`${TEST_TAG} cascade-ui-follower`);
+  // #481: times render as localized 12-hour with AM/PM (EN) or ص/م (AR).
+  await expect(followerCells.nth(2)).toContainText(/AM|PM|ص|م/);
 
   // Intercept the mutation so we can read its JSON body without
   // letting it actually fire (which would side-effect every other