CI runs the app-target tests; retire the dead LoggingPill

.github/workflows/ci.yml

@@ -1,9 +1,26 @@
 name: CI
 on: [pull_request]
+permissions:
+  contents: read
 jobs:
   build-and-test:
     runs-on: macos-15
     steps:
       - uses: actions/checkout@v4
       - run: swift build --build-tests
       - run: swift test --filter MetaWearTests   # skip hardware tests in CI
+  # The app target's unit tests (coordinator E2E against the demo fleet,
+  # history grouping, foreign-log decisions, …) were invisible to CI —
+  # only the SPM suites ran. The app requires the iOS 26 SDK, hence the
+  # newer runner image.
+  app-tests:
+    runs-on: macos-26
+    steps:
+      - uses: actions/checkout@v4
+      - run: >
+          xcodebuild test
+          -project Apps/MetaWear/MetaWearApp.xcodeproj
+          -scheme MetaWearApp
+          -destination 'platform=iOS Simulator,name=iPhone 17'
+          -only-testing:MetaWearAppTests
+          CODE_SIGNING_ALLOWED=NO

Apps/MetaWear/MetaWear/App/RootView.swift

@@ -145,8 +145,8 @@ private struct ErrorAndOrphanAlerts: ViewModifier {
             // so the user can decide what to do with it. The alert only
             // fires when LOG_LENGTH > 0 *and* we have no matching local
             // pending session — the in-app logging flow has its own UI
-            // for sessions it already knows about (LoggingPill,
-            // DownloadView).
+            // for sessions it already knows about (the Logging
+            // screen's status row, DownloadView).
             .alert(
                 "Logging in progress",
                 isPresented: Binding(

Apps/MetaWear/MetaWear/Features/Logging/LogSessionView.swift

@@ -197,7 +197,7 @@ struct LogSessionView: View {
                 Task {
                     await viewModel?.start(selections)
                     // Refresh the AppStore's pending-sessions cache so the
-                    // global `LoggingPill` becomes visible immediately.
+                    // pending-log badges appear immediately.
                     appStore.refreshPendingLogSessions()
                 }
             }

Apps/MetaWear/MetaWear/ViewModels/LogSessionViewModel.swift

@@ -167,7 +167,7 @@ final class LogSessionViewModel {
         // Per-record try/catch — a single failed `stopOne` (BLE hiccup,
         // unexpected board state) used to abort the loop, leaving the
         // remaining records' `status` stuck at `.running` and the global
-        // `LoggingPill` ticking forever. We always flip the status to
+        // pending-log badges stuck forever. We always flip the status to
         // `.stopped` even when the BLE command threw, because:
         //   - the user explicitly asked the session to stop, and
         //   - the captured data is still on the board for download.