feat: add deterministic office robot jobs

ARENA.md

@@ -1,7 +1,7 @@
 # Tera Arena environments
 
 `@lumbridge/tera/arena` is Tera's renderer-independent RL boundary. It imports
-no Three.js scene, canvas, DOM input, network client, or asset code. The four
+no Three.js scene, canvas, DOM input, network client, or asset code. The five
 shipped environments wrap the same fixed-step controllers and plans used by the
 interactive client:
 
@@ -9,6 +9,7 @@ interactive client:
 |---|---|---|---|
 | `drive-101-v1` | `VehicleController` + California transport pack | complete a short US-101 or I-5 route leg | guardrail contact |
 | `office-nav-v1` | `Plan(FRONTIER_VALLEY)` + `createWalker` | reach a collision-clear office waypoint | repeated collision stall |
+| `office-jobs-v1` | `Plan` + `robotRoutes` + `robotActivity` | complete an authored simulated patrol/delivery/inspection job | collision stall or repeated invalid interaction |
 | `crow-nav-v1` | `ActorController` in crow flight mode | reach a 3D waypoint | altitude/horizontal envelope contact |
 | `california-flight-v1` | `AircraftController` | reach a geographic/altitude waypoint | California flight-envelope contact |
 
@@ -85,6 +86,11 @@ The tests execute every train and dev scenario at two seeds and require:
 These are smoke-proof baselines, not optimal policies. They exist to make reward
 regressions and impossible tasks fail in CI before any training budget is spent.
 
+`office-jobs-v1` observes only current job facts and the current route waypoint;
+future seeded schedule entries are not leaked. SF and LA definitions are
+explicit same-floor scenarios tied to resolved room/prop anchors. They are
+demonstration data and never claim to describe live staff or company operations.
+
 ## Adding an environment
 
 Keep the environment under `src/arena/`, wrap an existing renderer-neutral