[Parity]: [P3] Verify bomb-threat event details against the 1994 original

Imported from the engineering backlog (_bmad-output/implementation-artifacts/backlog.md, story bomb-threat-parity).
Priority P3 (do-first order) | Severity: low | Status: idea | Epic: SimTower parity | Type: review-deferral | Recorded: 2026-07-08

Divergence from the 1994 original

Owner asked 2026-07-08 "do we have this?" -- YES we do (src/engine/EventSystem.ts bombThreat: pay ransom vs. Security search; detonates ~5 floors + fine if no Security). But parameters differ from 1994 and are worth a parity pass: 1994 fires the blackmail at ~2 stars (owner's screenshot), demands $200,000, and gives a live "explodes at 3 o'clock" deadline with Pay Them / Find the Bomb; ours gates at 4 stars and up, demands $300,000, and resolves on the daily roll (no in-day timed deadline). Decide which are canon vs our deliberate tuning (the 4-star gate may be intentional difficulty pacing) and align the ransom / star-gate / timed-deadline for Classic. Low priority; the event exists and works.

Start in src/engine/EventSystem.ts at the bombThreat event and inspect its current star gate, ransom, and resolution flow. Compare those details with the 1994 original, decide which differences are intentional tuning versus parity gaps, and align Classic behavior with the documented decision, including the timed deadline if required.