[fizzy-macos]

Part of fizzyedit/work#636

Goal

Smooth rounded edges at scale 1 without changing 2x (work#636, steps 1 and 2).

What changed and why

• Glass shader: at scale <= 1.25 the coverage ramp is 1.4 px (cov = clamp(0.5 - D/aa, 0, 1)), the rim line is widened to about 1.5 px, and the window hairline ramp is 0.7 px. Scale >= 1.5 keeps the old expressions. LiquidField.sample mirrors the coverage (edgeRamp).
• core/dialogs.zig: rounded fills use fade 1.5 at scale <= 1.25 (edgeFade), 1 otherwise.

How it was verified

• Unit tests: LiquidField coverage at 1x vs 2x, and edgeFade. scripts/zb build test, check-web and test-sdk-version ran with no errors printed.
• Not run: test-integration.

Not done / follow-ups

• Compiled shader outputs (spv/dxil/msl/glsl) are NOT regenerated: shadercross is not installed here. The Shaders workflow uploads the compiled-shaders artifact; commit it before merge.
• No 1x before/after captures or edge-error numbers (no windows allowed on this Mac): needs the QA loop.
• Step 3 (opt-in 2x render) not done; wait for the captures to show whether it is needed.

Changes (3 files, +47/-11)

 backend/src/glass/LiquidField.zig                  | 22 ++++++++++++++++++++-
 .../src/glass/shaders/liquid_glass.fragment.hlsl   | 13 ++++++++----
 core/dialogs.zig                                   | 23 ++++++++++++++++------
 3 files changed, 47 insertions(+), 11 deletions(-)

Gates: not run yet

Gates not run yet; scripts/agent-finish 636 replaces this with their output.

[fizzy-pm]

PM note: how this PR will be handled

What it is for: glass: smooth-edges-1x
Issue #636: glass and rounded shapes: smooth edges at scale 1 (wider coverage ramp, minimum rim width, optional 2x render)
Done when (from the issue): a 1x capture before and after in the PR body for the glass card corner, a bar, a pill and the rim, with the edge-error numbers; the 2x capture unchanged (pixel diff 0); no brighter seams (the reason for antialias:false).

Rules that apply: none special.
Reviews needed: 1, from any other team or kind.
Needs the maintainer's explicit yes before merge: no

Things to watch (checked by rule):

• the body names its work issue (Part of fizzyedit/work#N)
• size within 800 lines outside tests and docs (58)
• a gates section with what was run

What happens next:

1. Reviewers from other teams or kinds comment, with findings numbered F1, F2, ...
2. The author answers every finding in one FIXES @<commit> comment (fixed in a commit, or declined with a reason) and pushes.
3. Reviewers re-review the new commit on their own.
4. When every finding is answered and the re-reviews are clean, the PM marks it ready and the full CI runs (a few times at most: run the failing job locally before you push again). Only when CI passes does the PM look, and the PM gives the final okay.

A living status comment below is kept current. Nothing here is a merge decision.

[fizzy-pm]

Where this PR stands

Stage: In review
Next: Reviewers should review this commit (1 more kind needed)

What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):

• The body names its basis (Part of fizzyedit/work#N or a plan step)
• Within the size limit: 58 of 800 lines outside tests and docs
• The body shows which gates the author ran
• No open findings at this commit
• Every earlier finding was answered in a FIXES comment
• Clean reviews at this commit from 1 kind: none yet (has 0)
• Marked ready, which starts the full CI (the PM does this the moment the items above are met)
• The full CI passes at this commit
• The PM's final okay (pm-approval)

Reviews at the current commit (3c50725):

None yet.

Updated 2026-10-28 15:57 UTC by the PM. This comment is edited in place.