#36551 cloud receiver: log whether a policy read grants local admission (admit_until) and how long it took

The Cloud receiver's journal could not show whether local admission (#36014, cmux-platform#827) was granted. kept the current policy is logged only when a read gets no answer under admit_until, and an answered read said nothing about it. On a prod machine on 2026-11-05 the only line was receiver policy read took 6970 ms ..., which left admission unconfirmed.

An answered policy read now logs whether admit_until is present and how long the read took:

cmux link: receiver policy read took 212 ms; admit_until present (600 s of local admission)
cmux link: receiver policy read took 212 ms; admit_until absent (no local admission)

It is written on the first read and whenever admission appears or ends, never once per read; the lease is about 30 s.

Tests: link::native_process 9 pass (2 new); clippy -p cmux-tui --all-targets -D warnings clean.

Changelog

• Cloud machine logs say whether the receiver's policy grants local admission, and how long the read took.

🤖 Generated with Claude Code

Agent session: agent session

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Cloud receiver journal lines now show whether a policy read granted local admission—previously only unanswered reads logged kept the current policy, and answered reads said nothing about admit_until. An answered read now logs whether admit_until is present and how long the read took, written on the first read and whenever admission appears or ends, not once per read.