Put the Cloud sidebar on the right sidebar's chrome columns

[teamleaderleo]

This is #15881 re-landed on an origin branch so it can produce the evidence the call needs. On a
fork, pr-media.yml returns at once for anything but a same-repository pull request and ci.yml's
ui-tests job refuses a fork on its first step, so #15881 could never attach the tour frames that a
design call is judged on. The commits are unchanged: head 5f480d560ee90ab1a42131759b0ad7dd2f5538fd, the same tree #15881 carries.
Close #15881 in favor of this one.

Tour frames follow once the Cloud-sidebar scenario lands (#15923).

This re-lands #15307 on a clean branch because one commit there was authored by a bot address that CLA Assistant cannot accept. The code is unchanged apart from catching up to main.

Part of the Cloud right sidebar audit (manaflow-ai/cmuxterm-hq#853).

The Cloud surfaces live inside the right sidebar but cannot import the app target that owns RightSidebarChromeMetrics, so each of them carries its own copy of the sidebar's numbers. The copies drifted:

• The Cloud banners (free-access, tunnel, operation activity) sit on a 12pt outer horizontal inset. The chrome bar they sit under, the Cloud header, takes 8 on both edges, and so does the Feed control bar. So the Cloud surfaces visibly step in from the sidebar they are part of. (The sidebar's own header bars, the mode bar and the Vault bars, ask for a narrower 4/6; the Cloud header does not, and this PR does not move it.)
• Two of those banners use a 5pt vertical inset against the sidebar's 4, and the machines-unavailable notice uses 6. That notice draws a tinted background, so its height visibly changes.
• The Cloud tree reserves a 12pt trailing column against the 8 the Cloud header above it uses. Machine rows stop short of the header's refresh and + buttons, and titles truncate 4pt earlier than they need to. The row hover buttons and the header's buttons are the same control, so they should stop on the same column.

CloudSidebarChromeMetrics states those numbers once for the package. CloudTreeLayoutMetricsTests runs in the app target, where both types are visible, and fails if the copy ever disagrees with the original, so this cannot drift again silently.

It also removes the drift that this change would otherwise have introduced: CloudTreeLayoutMetrics.referenceInset and the spacing lab's referenceInset each restated 12 independently of CloudTreeRowGrid.trailingPadding. The outline document and the hosted row content compute their trailing reservation separately, so had only one moved, titles would truncate before the space they were given ran out. Both now follow the row grid.

Not in this PR. The operation activity row keeps its 8pt vertical padding: it carries a progress indicator rather than a line of text, so shortening it is a look, not a mismatch. The bigger Cloud alignment questions are taste calls and went to cmux#13742 with before/after shots instead: the tree reserves a disclosure-caret column before its icon (level 0 icon at x=26, text at x=46) so it structurally cannot sit on the shared content column of 12/30 without giving that column up, and section headers render with no icon slot so they sit on a different text column from their children.

Changelog

Fixed: Cloud sidebar banners and machine rows now line up with the rest of the right sidebar's columns instead of stepping in from them.

Verification

Red and green from the same focused command, cmuxTests/CloudTreeLayoutMetricsTests:

• red: 9764d00afbf (the pin, before the surfaces move onto it)
• green: 8fb16647b0c, run also covering CloudTreeCompactLayoutTests, CloudSidebarAttentionLayoutTests, CloudSidebarPinGeometryTests, CloudSidebarScaleTests

Those two SHAs are on #15307, where the runs happened. They are not on this branch. The replayed equivalents here are c6c6a800ba6 (the red pin) and 13c8d3b1d67 (the fix), whose contents are byte-identical to the originals.

python3 scripts/verify-local.py passes 5/5 selected checks on this branch. An earlier version of this description said it was blocked in this session; that was a missing TMPDIR directory, not a sandbox limit.

Before/after frames to follow.

A review subagent then found two bugs in the replayed work: the tree had been put on the wrong trailing column (6 rather than the header's 8), and the fleet status row was described as aligned but never was. Both are fixed in 5f480d560ee, with the details in a comment on this PR. What no test covers: nothing measures a rendered view's inset, so the banner, notice, error row and status row changes are pinned only by the metric they read.

🤖 Generated with Claude Code

---

Summary by cubic

Aligns the Cloud sidebar surfaces with the right sidebar's chrome columns instead of drifting from them. The Cloud package cannot import the app target that owns RightSidebarChromeMetrics, so its surfaces each carried hardcoded copies (12pt outer insets, 5pt verticals, a 12pt tree trailing column) that had drifted from the sidebar's 8pt/4pt chrome, making Cloud banners and rows visibly step in from the sidebar they sit under.

• Adds CloudSidebarChromeMetrics to state the sidebar's numbers once for the package, and points the Cloud banners, notices, status rows, and tree trailing column at it instead of literals.
• Defaults CloudTreeLayoutMetrics.referenceInset and the spacing lab's referenceInset to CloudTreeRowGrid.trailingPadding so the outline document and hosted rows cannot drift apart.
• App-target Cloud views read RightSidebarChromeMetrics directly rather than the package's copy.
• Pins the package copy to the original in CloudTreeLayoutMetricsTests, which runs where both types are visible, so the copy cannot drift silently again.
• The operation activity row keeps its 8pt vertical padding deliberately: it carries a progress indicator, not text, so shortening it is a look rather than a mismatch.

^{Written for commit c5628c0. Summary will update on new commits.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[coderabbitai]

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[teamleaderleo]

Caught up to main at e709b69 (the newest main commit with green fast guards; one newer main commit was still pending when the catch-up ran) in merge commit 8d1afbb.

There were no file conflicts. The catch-up also brings in dogfood/scenarios/cloud-sidebar-audit-tour.json, so this PR can produce the before/after tour frames. GitHub now reports the PR mergeable, and CI has completed successfully.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[github-actions]

Merge receipt for c5628c074d, merged 2026-09-30 20:06:57 UTC

• Not verified at merge: ci-status (failure), CI fast guards (failure), Fast static checks (failure), guards (19) (failure)
• Verified: CI timing, GhosttyKit release check, Testbox broker trust boundary, tests, Web complexity, web-validation
• Skipped by policy: browser, Claude wrapper regressions, Dogfood build #​${{ github.event.pull_request.number }}, full-suite-coverage, linux-preflight, macos, macOS admission gate, remote-daemon, suite-coverage, ui-tests, web, web-build, and 2 more
• Full suite: runs on main after merge.

Labeled merged-unverified: if main breaks near this merge, look here first.