Add live dashboard with SSE job events

Expose /jobs, /dedup, and /events routes backed by a new EventBus that
broadcasts job lifecycle and per-job progress over SSE. Serve a static
dashboard from front/ that lists pending and in-progress jobs, streams
agent activity, and shows completed reviews.

Also add migrate-apply/migrate-generate scripts that load .env, update
the Containerfile to ship the front assets and use the apply script, and
refresh the roadmap.

README.md

@@ -109,16 +109,18 @@ The database schema is versioned with [Toasty](https://github.com/tokio-rs/toast
 After changing a model in `crates/steep-server/src/schemas/`, generate a migration:
 
 ```sh
-cargo run -p steep-server -- migration generate --name describe_change
+./scripts/migrate-generate.sh describe_change
 ```
 
 Apply the pending migrations **before starting the service** — the server does not migrate at boot:
 
 ```sh
-cargo run -p steep-server -- migration apply
+./scripts/migrate-apply.sh
 ```
 
-The `Containerfile` does this at startup: its entrypoint runs `steep-server migration apply` before exec'ing the server. The CLI reads the migration files from `MIGRATIONS_DIR` (defaults to the crate's `toasty/` directory; the image sets it to `/app/toasty`).
+Both scripts load the `.env` file at the project root (so `DATABASE_URL` is picked up). Generation runs through `cargo run -p steep-server --`; applying uses the compiled `steep-server` binary when present (as in the image), falling back to `cargo run` otherwise.
+
+The `Containerfile` does this at startup: its entrypoint runs `scripts/migrate-apply.sh` before exec'ing the server. The CLI reads the migration files from `MIGRATIONS_DIR` (defaults to the crate's `toasty/` directory; the image sets it to `/app/toasty`).
 
 Other subcommands: `migration snapshot`, `migration drop`, `migration reset`. They read `DATABASE_URL`.