docs: v0.140.0 Direction-2 waiter — REPORT + CONTEXT (live: 240s no-annotation hold, 0.047s wake, restart no-storm)

CONTEXT.md

@@ -7,7 +7,23 @@
 >
 > Ask Claude Code: "Please update CONTEXT.md with what we did today"
 
-Last updated: 2026-07-16 (v0.139.0 — immediate out-of-cycle hub report, Direction 1)
+Last updated: 2026-07-16 (v0.140.0 — Direction-2 immediate-sync wait channel; the immediate-sync arc is COMPLETE for the controller plane)
+
+> **2026-07-16 — v0.140.0: Direction-2 immediate-sync (hub→box) SHIPPED.** The reverse of v0.139.0:
+> an OPERATOR action on the hub now reaches the box in seconds. `report.Waiter`
+> (`internal/report/waiter.go`) holds a hanging `GET {hub}/api/v1/wait?gen=N` (same hub URL+key as
+> the pusher — no new config keys) against hub ≥ v0.58.0's in-memory operator-intent generation
+> counter; on a generation CHANGE it fires the v0.139.0 `report.Trigger` and nothing else, so the
+> report ACK delivers everything through the UNCHANGED machinery (the box pulls even the wake-up).
+> No overall client timeout (held GET); first-observation records-not-fires (no restart echo);
+> same-gen timeout fires nothing; errors incl. a 404 from a pre-v0.58.0 hub back off 5s→5min while
+> the 15-min cycle reconciles. Gated on the SAME `hubPusher!=nil && Hub.Enabled` as the trigger.
+> Copy soften: backups_remote/escrow "néhány **másodperc**, legfeljebb 15 perc" (15-min bound stays
+> as the honest worst case). Red-proof: baseline-branch-off → first-obs fires (reverted). Agent-plane
+> poke is PARKED in the OOB arc (spike P4). Deployed to 9201; live-validated (hold + immediacy).
+> Detail: `CHANGELOG.md` v0.140.0, `controller/README.md` §9, `REPORT.md`.
+
+Last updated (prior): 2026-07-16 (v0.139.0 — immediate out-of-cycle hub report, Direction 1)
 
 > **2026-07-16 — v0.139.0: immediate out-of-cycle hub report on user actions (Direction 1
 > SHIPPED; Direction 2 pending SPIKE-immediate-sync-transport).** Viktor's ruling: user actions