[dgesteves]

The polish left from the review of #200. Site only, no changeset. Roadmap item: os-200-polish.

What was wrong

• Copy link in Safari. When the code had just changed, copyLink waited for linkHash() and then called navigator.clipboard.writeText. Safari refuses a clipboard write that starts after the click handler has awaited something. A failed write was also silent: the rejection handler was () => undefined.
• A layout shift when a shared link opens. While the code from a #code= link was being checked, the "Apply N fixes" row went away (fixable was [] while stale), then came back with the result. At 1440 px the row sits on its own line under the heading, so the findings list moved from y 509 to 468 and back. That is two layout shifts of 0.0199 each, CLS 0.0399.
• Tests. The touch-target test in site/test/small-screens.test.ts repeated the one in site/test/polish.test.ts.
• ROADMAP.md was out of date. Every line under "In review" (fix: per-user temp cache, quoted repository text, and linear color rule #199, feat(site): shareable playground links, no layout shift from the font swaps, a 44 px Ask target #200, feat(config): an app's config builds on its design-system package's, and so does the root's #202, docs(readme): add a compatibility section, and say installed apps read a dist-only package's type declarations #203, docs: support tiers for every client setup, and a four-week integration freeze #204) and under "Merged, in the next release" (fix(tokens): read wrapped theme colors, import order, the v3 radius scale and an app's own stylesheet #201) has merged, and the open pull requests were not listed.

What changed

• site/components/playground.tsx
  • A new copyText(text: Promise<string>) starts the write as part of the click. The link goes in as a promise inside a ClipboardItem, the same way copyMarkdown in page-actions.tsx does it. Where there is no ClipboardItem, it falls back to writeText. copyLink builds the URL inside that promise and updates the address bar there, as before.
  • When the write fails, the existing live region next to the button says "Could not copy. The link is in the address bar." It is cleared after 1.6 s, like the success message.
  • The row moved into a small ApplyAll component. While the edited code is checked again, it keeps the last result's counts, faded, with its button disabled. This is what each finding's own "Apply fix" button below already does. It no longer goes away and comes back. Once the new result is in, it shows the new counts, or goes away if no finding has a fix.
• site/test/small-screens.test.ts: removed the duplicate touch targets block and the imports only it used.
• site/test/polish.test.ts: added components/ask.tsx to the files checked for the tap class. I also added components/site-menu.tsx, which only the removed test checked, so the menu button keeps its check.
• ROADMAP.md, the two status sections only. I checked each line against GitHub's merge dates, gh release list and CHANGELOG.md:
  • fix(tokens): read wrapped theme colors, import order, the v3 radius scale and an app's own stylesheet #201 shipped in 0.9.1, feat(config): an app's config builds on its design-system package's, and so does the root's #202 in 0.10.0 (both released 2026-10-23) and fix: per-user temp cache, quoted repository text, and linear color rule #199 in 0.10.1 (released 2026-10-27). They leave the roadmap: the file says what shipped is in the changelog.
  • feat(site): shareable playground links, no layout shift from the font swaps, a 44 px Ask target #200, docs(readme): add a compatibility section, and say installed apps read a dist-only package's type declarations #203 and docs: support tiers for every client setup, and a four-week integration freeze #204 merged without changesets. They are website and docs changes, live since they merged.
  • Main is the 0.10.1 release with no pending changesets, so "Merged, in the next release" now says nothing is waiting for a release, and names the three live changes with their links.
  • "In review" now lists the open pull requests docs: make the setup prompt, FAQ, plugin README and bench text match what onsystem does #241 (docs) and fix(server): retry failed loads, reload JS configs, answer per path when --root holds projects #242 (MCP server). I left out this pull request and the dependency bumps.
  • Under Next, Docs and examples, a new line: "Open in playground" links on the examples of /rules/<id> pages. It needs the playground's linkHash moved into site/lib/. Nothing else in the file changed.

A side effect of keeping the row: after "Apply all", the pressed button stays visible but disabled until the check returns, then goes away. Before, it went away at once. Focus still moves to the summary, as before. The findings list changes at that same moment anyway, because the fixed findings drop out of it.

How it was tested

New file site/test/playground-share.test.ts, 4 tests. All 4 fail on main, where neither copyText nor ApplyAll exists, and pass on this branch:

• The clipboard write starts before the link's promise resolves, and the copied text is the URL.
• Without ClipboardItem it falls back to writeText. It rejects when the browser refuses the write, and when there is no clipboard at all.
• The row's text is the same stale and fresh, and the button is disabled only when stale.
• There is no row when no finding has a fix.

CLS while opening a #code= link (the first draft plus one comment line). I measured it with a Playwright PerformanceObserver (layout-shift, inputs excluded) in Chromium at 1440 x 900, against next start on a local production build, 5 runs each:

	Run 1	Run 2	Run 3	Run 4	Run 5
main	0.0399	0.0399	0.0399	0.0001	0.0399
this branch	0.0029	0.0029	0.0001	0.0029	0.0029

At 375 px, the branch measured 0.0000 in 5 runs. What is left at 1440 px (two shifts of 0.0014) is not the row. The status in the editor bar changes width (the error and warning count, then "Checking…"), so it moves sideways, and the error marks in the code are redrawn. The 0.0001 is the page heading moving 3 px. WebKit does not report layout-shift entries, so there are no WebKit CLS numbers.

Copy link, in Playwright Chromium (clipboard read back) and WebKit (live region read). Each was tested with the link ready and with a click straight after an edit, with link compression slowed by 300 ms so the click lands first. Both cases copy the right URL on this branch. With the clipboard write made to fail, main's live region stays empty and this branch announces the failure, in both engines. Playwright's WebKit does not enforce Safari's rule about writes after an await, since main copies there too. So the Safari fix rests on the ClipboardItem pattern page-actions.tsx already uses, and on the test that the write starts during the click.

I also checked in Chromium at 1440 px and WebKit at 375 px: while typing, the row stays disabled and faded; after the check, it is enabled again. After Apply all, focus moves to the summary and the row goes away once no fix is left.

Gate:

• pnpm install --frozen-lockfile --prefer-offline: ok
• pnpm format:check, pnpm lint, pnpm typecheck: clean
• pnpm test: 102 files and 1290 tests passed, 1 file and 3 tests skipped
• pnpm build: ok, publint found no issues
• pnpm --filter site generate, test, typecheck, lint, build: ok. The site tests ran 21 files and 288 tests.

Not in this PR

• The editor bar's status changing width while a check runs, the last 0.0014 shifts above.