fix(luna): the Explorer rail is added to the window, not taken out of the document

[oddharsh]

/garage/encoding declared 720px of prose and rendered 516px of it. The task pane is a 186px grid track plus a 14px gap living inside the window's max-width, so every page Explorer chrome reached quietly meant something different by the number its author picked.

The mechanism

Each page declares its measure once as --axp-maxw and consumes it, and one rule in luna.css grows a paned window by exactly one rail plus one gap:

.window:has(>.axp-tasks),.np-window:has(>.axp-tasks){
  --axp-rail:186px;--axp-rail-gap:14px;
  grid-template-columns:var(--axp-rail) minmax(0,1fr);column-gap:var(--axp-rail-gap);
  max-width:calc(var(--axp-maxw,720px) + var(--axp-rail) + var(--axp-rail-gap))}

The worker pages needed nothing, because lunaPage has emitted :root{--axp-maxw:${width}px} since it was written. The 23 static pages and lwe-base.css swap max-width: 720px for --axp-maxw: 720px; max-width: var(--axp-maxw), so no number is written twice and none can drift — which is why this needs no build tripwire. The 186/14 literals are tokenised for the same reason: the track and the compensation have to agree, and a paned window whose two numbers disagree is off by exactly the amount nobody notices.

Specificity carries it without touching cascade order: .window:has(>.axp-tasks) is 0,2,0 against each page's own .window at 0,1,0, so it wins wherever the page's style sits relative to luna.css.

It deletes a special case

.np-window.np-folder:has(>.axp-tasks){max-width:760px} was a hand-computed 560+200 for the /writing folder, with a comment explaining the arithmetic. writing.js declares 560 as the variable now and the generic rule lands on the same 760.

Measured, against the built tree at a 1280 viewport

page	before	after	content column
/garage/encoding	720	920	516 → 716
/lwe/dac	640	840
/lens, /photos	980	1180
/writing	760	760	unchanged

Homepage is untouched (it has no .window and takes no pane). Mobile stacking below 760px is unchanged, since the window is width:100% there and the cap never applies.

One cost, on the widest pages only

At 1280 the 1180-wide windows sit over the desktop icons, clearing them again above ~1340. /access already did this at 1440. Capping with min(…, 100vw - 190px) would hold an icon column open but fights maximize, so it is deliberately left alone.

Checks

pnpm run build clean · 206/206 contract tests · pnpm run routes:check 122 routes, 0 hard failures · perf-budget hard checks green.

🤖 Generated with Claude Code

[github-actions]

Wire-size diff vs merge base

111ac75 → dae34bf

Brotli q11, the quality the edge serves. Every number here is deterministic:
an unchanged file produces no row. Advisory — this check fails on nothing.

Client assets

Total Brotli: 60.92 KiB → 60.97 KiB (+0.05 KiB, +0.1%) across 12 files, 2 changed.

file	base	head	Δ
luna.css	8.84 KiB	8.88 KiB	+0.04 KiB (+0.4%)
lwe-base.css	1.30 KiB	1.31 KiB	+0.01 KiB (+0.7%)

Pages

Total Brotli: 471.25 KiB → 471.52 KiB (+0.27 KiB, +0.1%) across 46 files, 42 changed.

No single file moved by 0.13 KiB or more.

_{Plus 42 files under the 0.13 KiB floor, net +0.27 KiB — usually content-hash churn in /a/ references, counted in the total above.}

Worker bundle

268.66 KiB → 268.68 KiB gzip (+0.02 KiB, +0.0%)

Largest module deltas (raw bytes in bundle):

file	base	head	Δ
.build/holding/_worker.js/writing.js	15.63 KiB	15.66 KiB	+0.03 KiB (+0.2%)

Dictionary deltas (pd/)

134 → 134 deltas, 388.99 KiB → 390.71 KiB (+1.72 KiB).

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	aadhar-sh	ee4b26d	Aug 10 2026, 07:57 PM