build(uno): Uno.Sdk 7.0 with Uno.Extensions 8.0.0-dev.83 and a Shell navigation root

[kazo0]

Rebased onto master after #73 squash-merged (GitHub reported the stacked branch as conflicting and ran no CI). Moves the app to Uno Platform 7.0: global.json to Uno.Sdk 7.0.0-dev.73 (the latest 7.0 dev build on nuget.org), Uno.Extensions pinned to 8.0.0-dev.83 ahead of the Sdk, and a Shell navigation root. Every head builds, every page renders, 110 unit tests pass.

What this does

• Drops the UnoThemeVersion / UnoToolkitVersion pins from Directory.Packages.props (they only existed to stay on the pre-7.0 servicing lines). The Sdk's groups resolve to Uno.WinUI 7.0.0-dev.2270, Themes 9.0.0-dev.41, Toolkit 11.0.0-dev.140. The Uno.Fonts.Roboto 2.10.0-dev.12 pin from feat(reading): larger default text, a Text Size setting and fixed tab labels #73 stays: the 7.0 Sdk still pins fonts at dev.9.
• Pins UnoExtensionsVersion to 8.0.0-dev.83 (chore: Rebuild against current Uno 7.0 Core (7.0.0-dev.2162) unoplatform/uno.extensions#3223, the rebuild against the current 7.0 core). The Sdk still carries 8.0.0-dev.76, built against an older core; its Navigation.UI / Reactive.UI referenced types 7.0 no longer has (UNOB0020, "will fail at runtime"). Drop the pin once an Sdk carries dev.83 or later.
• Fixes web-deploy.yml's "Verify profile-guided AOT" step: Uno 7.0 writes uno-config.js at the wwwroot root, not under package_<hash>/ (the web preview job failed on that ls). Checked against a local Release publish: runtime mode InterpreterAndAOT, profiled AOT on, 117 assemblies compiled against aot.profile, dotnet.native.wasm 22.4 MB. _headers needs no change: the file is not fingerprinted and keeps the Pages default of revalidating.
• Adds Views/Shell.xaml, the template-style navigation root (a UserControl around one ContentControl, exposed through IContentControlProvider), and OnLaunched now calls NavigateAsync<Shell>(). Routes, pages and view-models are unchanged: the default Main route navigates MainPage into the shell through a FrameView, and MainPage's TabBar regions attach under that navigator.

What 7.0 needed in the app

• Application.Resuming / EnteredBackground are gone. App.xaml.cs and NotificationService.Android.cs use the static Windows.ApplicationModel.Core.CoreApplication events, which Uno.UI 7.0 raises.
• Android host: Uno.UI.Runtime.Android.NativeApplication is abstract and builds the host in CreateHost() (UnoPlatformHostBuilder.Create().App(() => new App()).UseAndroid().Build()); ApplicationActivity moved to the same namespace.
• UnoSplashScreenColor → UnoSplashScreenBackgroundColor (UNOB0028).
• Android minSdk 21 → 24. The 7.0 AndroidX graph needs 23 (androidx.tracing, AMM0000) and the Sdk defaults to 24. The deliberate Xamarin-era 21 pin (spec 009) cannot survive 7.0; spec 009 and AGENTS.md are updated. This is a product call.
• Uno.UI.Toolkit.ElevatedView (the settings dropdown from feat(reading): larger default text, a Text Size setting and fixed tab labels #73) is Uno.UI.Xaml.Controls.ElevatedView: 7.0 renamed the Uno.UI.Toolkit assembly to Uno.UI.Extras and moved its types with no forwarders.
• Microsoft.Extensions.Configuration.* 10.0.12 to match the Sdk's graph (NU1605 otherwise).
• A Page can no longer be the shell (see below).

Why the pages were blank, and why dev.83 alone was not enough

Two causes, found one under the other.

1. Uno.Extensions 8.0.0-dev.76 vs the 7.0 core — the UNOB0020 warnings above. 8.0.0-dev.83 removes them on every head.
2. NavigateAsync<MainPage>() with a Page as the shell. The navigation host casts the shell to ContentControl to make it the root region, and falls back to the Toolkit's root-view initializer otherwise. Up to 6.x Uno's UserControl, and so Page, derived from ContentControl, so MainPage itself was the root region and the app worked. Uno 7.0 aligns UserControl with WinUI (: Control; checked in the Uno.UI metadata, 6.8 vs 7.0.0-dev.2270): the cast yields null, the fallback is a LoadingView that never enters the visual tree, and the root navigator's Main request parks forever ("Region '' has no children to forward request to … Parking navigation 'Main'"). Nothing was logged because the navigation engine logs only through the host's own logger factory, which this app never configured (trace it with ConfigureLogging on the IHostBuilder, not through InitializeLogging). The fix is the template's shell shape, a ContentControl exposed through IContentControlProvider. The maintainers already track the silent failure as BC14 in Uno 7.0 retarget: follow-ups for the public Uno.Sdk and release day unoplatform/uno.extensions#3186 ("needs a runtime-verified fix plus a regression test"); this app's runtime confirmation of it is filed as [Navigation] NavigateAsync<TShell>() with a Page/UserControl shell is a silent blank screen on Uno 7.0 (BC14 in #3186) unoplatform/uno.extensions#3225 and linked from that bullet.

Verification

• UNOB0020 gone from the iOS and Android builds; desktop, Android, iOS simulator and WebAssembly heads build.
• iOS simulator (iPhone 17 Pro): the Reflection page renders. Web head driven headlessly: all three tabs render at phone width, the side rail at 1024 wide, dark theme too.
• Navigation trace on the web head: Main → FrameView → MainPage, Reflection → DailyReflectionPage, then SoberTime / Settings on tab taps; no parked root request, no "initial navigation returned null".
• 52 presentation + 58 services unit tests pass; XamlStyler, dotnet format whitespace and style pass.
• After switching Sdk, rm -rf DailyReflection/obj DailyReflection/bin (a stale 6.x Uno.dll next to 7.0's Uno.WinRT.dll crashes the iOS registrar with "Cannot register two managed types … VideoSurface").

🤖 Generated with Claude Code

https://claude.ai/code/session_01Qakj5qRUPLXR5HdMmDnBfZ

[github-actions]

🌐 Web preview deployed

https://f6bc770f.dailyreflection.pages.dev

Built from 9ff74dd. Updates on every push.