v0.1.41

Highlights

Uno integration: a real entry point

Registering Pysar in an Uno application is now a single call on Application, and it works the same
way from every head (WebAssembly, Desktop, Android, iOS, WinAppSDK) — OnLaunched is the one place
they all run through.

protected override void OnLaunched(LaunchActivatedEventArgs args)
{
    this.UsePysar(typeof(App).Assembly, pysar => pysar
        .AddFont("Fonts/Ubuntu-Regular.ttf", "Ubuntu")
        .AddFont("Fonts/Ubuntu-Bold.ttf", "Ubuntu", FontStyle.Bold));
}

• ApplicationExtensions.UsePysar(...) and UsePysarAsync(...) — the latter preloads
  ms-appx:/// assets for applications that ship them as Content rather than EmbeddedResource.
• assetAssembly is required: on the WebAssembly head the entry assembly is the head project, not
  the application project the assets are packaged into.
• Registration moved into UnoRegistration; PysarUno now exposes PlatformHandler /
  ExportService and resets the export service on re-registration.

Ctrl+wheel and trackpad pinch zoom the report, not the page (browser head)

ReportView has always zoomed on Ctrl+wheel and marked the event handled, but on a browser head
that changed nothing visible: "handled" is a managed routing flag, while page zoom is a DOM default
action that only preventDefault on a non-passive listener stops. The reader got a scaled page and
a report that never moved — and the trackpad pinch went with it, since Chrome and Safari deliver it
as a wheel event with ctrlKey set.

UsePysar now installs a small embedded script, imported from a data URL, so a consuming
application adds one call and no files. Opt out with suppressBrowserZoom: false to keep the
browser's own zoom as an accessibility affordance.

Suppression covers the whole Uno canvas: Uno draws the entire application into a single canvas, so
the DOM cannot tell the report from the toolbar beside it. Anything on the page outside that canvas
keeps the browser's zoom.

Measure probe caching

New MeasureContext and LayoutEngine.ProbeSizeAsync cache probe measurements, and
GridLayoutMeasurer / StackLayoutMeasurer now measure through probes instead of re-measuring the
same subtree repeatedly — a large drop in repeat measures on nested layouts.

A readable diagnostic for the SkiaSharp native/managed split on WebAssembly

An Uno browser head pulls SkiaSharp.NativeAssets.WebAssembly through
Uno.WinUI.Runtime.Skia.WebAssembly.Browser, which asks for the 3.119 line, while Pysar renders
through 4.151. NuGet resolves one managed SkiaSharp and one native archive, and the two no longer
agree.

Every other platform reports that split as a startup exception with a message of its own.
WebAssembly links the native side statically at build time, so it surfaces instead as a wall of
wasm-ld: undefined symbol: sk_* lines naming entry points the application never wrote, with
nothing pointing at the version that caused them.

The check now ships as buildTransitive, so it reaches consumers who referenced Pysar.Uno or
Pysar.Blazor rather than Pysar itself — those are the ones who end up on a browser head.
Declaring a dependency on the native package would fix it silently, but it is a 67 MB download
charged to every WPF, console and Uno desktop consumer that will never link a wasm binary.

Breaking changes

• PysarUno.Use(...) and PysarUno.UseAsync(...) are removed. Use Application.UsePysar(...) /
  UsePysarAsync(...) instead.

Other

• Docs updated: root README.md, src/Pysar.Uno/README.md, docs/quick-start.md.
• New AGENTS.md; added opencode.json.
• Tests: UnoRegistrationTests, MeasureProbeCachingTests, and a new PackageLayoutTests
  assertion for the buildTransitive payload.

Full Changelog: v0.1.38...v0.1.42