Append-only log of shared-surface changes — anything in a backend or the
shared core that another backend/platform consumes and could be affected by
(the shared symbol map, core View/Layout types, the view-host, cross-cutting
behavior). Backend-only internals that can't regress another platform don't
belong here — keep those in the backend's own docs/issues.
Every SwiftOpenUI backend agent clones this repo, so this is the discovery point for "did someone change something under me?" Newest entries on top. One entry per shared change; always say who to ping if it regresses your backend.
## YYYY-MM-DD — <platform/agent> — <summary>
- Shared surface: <what shared/core file or type changed>
- Impact: <who consumes it / could regress; verification if known>
- Ping: <owner/agent>
- Refs: <commits / issue docs>
- Shared surface:
SwiftOpenUISymbols/SFSymbolCompatibility.swift+MaterialSymbolsCodepoints.swift— addedcircle.dotted → radio_button_unchecked(0xE836). Additive; no existing mapping changed. - Impact: every backend resolves
circle.dottednow (macOS uses native SF Symbols → no-op). Verified benign on macOS; net positive on GTK4 (theSyncAction.ignorebadge now resolves to a real Material glyph instead of a missing symbol). - Awareness (not a shared-code change): the Win32 child-
@Statereconciliation gap (docs/issues/win32-conditional-view-rebuild.md) is a shared view-host problem — GTK4 independently hits the same OutlineGroup-expansion-resets-on-ancestor-rebuild failure. Likely one fix at the shared view-host layer (ID-keyed child-state persistence) retires the workarounds on both Win32 and GTK4. Reconcile the two designs before either backend invests further. - Ping: Win32 agent (symbol map); Win32 + Linux agents (reconciliation).
- Refs: SwiftOpenUI
629323a;docs/issues/win32-outlinegroup-dropdown-followups.md.