The phone can reach the plan, read the disclosure, and see the room

Three things, all on the door people actually open. office.lumbridgecorp.com is
a link you send somebody, and a link somebody is sent is opened on a phone.

**The plan had no way in.** The stylesheet builds it a whole bottom-sheet layout
below 600px — full width above the rail, 38dvh tall, hover-only text dropped —
and the only thing that could open it was the `M` key, which on a phone is not a
control that is hard to find but a control that does not exist. The comment
above that layout says "it is still behind `M`, so it costs nothing until it is
asked for", and on a phone it could not be asked for. So there is a button, in
the one cluster a thumb reaches, at every width rather than only the narrow ones
— a control only a keyboard can reach is a control some people do not have, and
that is as true at 1920 as at 390. It is glyph-only, because the `M` hint beside
it already carries the word and two controls labelled "plan" in one bar is one
too many, and it carries `aria-pressed` for the same reason the chapter buttons
do: a toggle that does not look like its state is a button that appears to do
nothing on every second press.

**The disclosure was behind a hamburger.** "Sample occupancy — these people are
invented" lived on `#office-badge` inside `#panel`, and on a phone `#panel` is a
sheet that starts closed. The one sentence standing between twenty-five invented
people at real desks and a screenshot presented as a staff list was hidden, on
the device most likely to take the screenshot. It moves to `#source`, which is
where this page already says what on screen is and is not real, is fixed and
always drawn, and which the phone stylesheet itself calls "the one caption that
is never allowed to be dropped for space". It replaces the city's liveness line
while you are inside rather than joining it, because the markers, the sky and
the traffic are facts about a board behind you — and "live data" printed over
invented colleagues is the exact species of lie that wording was rewritten to
stop telling. It also needed a rule of its own: `.source` on a phone is one
nowrap ellipsised line, which rendered this as "sample occupancy · these people
…", a truncation that removes the only word that mattered. A disclosure cut off
mid-clause is worse than none, because it looks like a caption somebody bothered
to write and nobody goes looking for the rest.

**The room did not fit.** `camera.fov` is vertical, so visible width is
`distance * tan(fov/2) * aspect`, and a phone held upright has an aspect near 0.5
against the 16:9 those viewpoints were framed by eye against. At the same
distance that is a third of the width: the arrival shot put a thirty-four-metre
floor plate off the corner of the screen under a frame full of empty sky. The
pack was not wrong and the renderer was not wrong — the number meant something
else on that screen. `poseFor` now preserves the width the author framed, which
is the thing they were choosing; "everything in this building is somewhere in
this frame" is a statement about width, and the extra height a tall screen throws
in costs nothing. It only ever pushes back, never pulls in, so a window wider
than 16:9 is untouched.

The correction scales the whole offset from the target and not the ground
distance alone, and that is the entire fix rather than a refinement. Multiplying
only the distance does not step back from a shot, it flattens it: 32 m out and
14 m up became ninety-odd metres out and still fourteen up, a near-horizontal
squint at the edge of a floor plate stranded near the horizon. I built that
first and it was worse than the bug.

Checked on an iPhone 13 viewport and at 1920x1080 and 1440x900. Phone: the whole
floor centred at the authored angle with people at the benches, the disclosure
on two lines and complete, the button tapped open and the plan sheet up with
eight rooms named. Desktop 16:9 is pixel-identical — the correction is exactly 1
there — and the console is clean on all three.

index.html

@@ -472,6 +472,10 @@
       @media (hover: hover) {
         .help:hover { background: rgba(255, 255, 255, 0.16); color: var(--ink); }
       }
+      /* A toggle has to look like its state, or it is a button that appears to do
+         nothing on every second press. Same treatment the chapter and city
+         buttons take, for the same reason and from the same attribute. */
+      .help[aria-pressed="true"] { background: rgba(242, 177, 52, 0.2); color: var(--amber-ink); }
 
       /* ---- Bottom left: where the numbers came from -------------------------
          Shown only when the data is live — see `renderSource` in main.ts for why
@@ -684,6 +688,9 @@
         /* No keyboard, so no key hints — and with them gone the card around
            them is a full-width bar of glass holding one button. On a phone the
            hint *is* the `?` button. */
+        /* The key hints go because there is no keyboard. The plan button is not
+           one of them and is not a `span`, so it stays — which is the whole
+           reason it exists. */
         .hint span { display: none; }
         .hint {
           align-self: flex-end;
@@ -707,6 +714,16 @@
           overflow: hidden;
           text-overflow: ellipsis;
         }
+        /* Except when it is carrying the office's disclosure, which is a
+           sentence and not a label. "sample occupancy · these people …" is a
+           truncation that removes the only word that mattered, and a disclosure
+           cut off mid-clause is worse than none at all — it looks like a caption
+           somebody bothered to write, so nobody goes looking for the rest. It
+           gets the width and the second line. */
+        body.sample-occupancy .source {
+          max-width: calc(100vw - var(--s3) * 2);
+          white-space: normal;
+        }
 
         /* The plan, as a bottom sheet. At 11.5rem in a corner it ate a fifth of
            a 375px map and its own affordances were about six pixels across —