Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/host/src/components/SourceOverlay.tsx`:
- Line 28: SOURCE_LABELS[entry.status] can be undefined for unknown status
values causing an empty label; update the rendering in SourceOverlay (where
entry?: CacheStatusRemoteEntry is used) to use the same fallback pattern as
DevToolsPanel.tsx by replacing bare SOURCE_LABELS[entry.status] with
SOURCE_LABELS[entry.status] ?? entry.status (and ensure you handle optional
entry before accessing entry.status).

In `@vendor/mf-core`:
- Line 1: The vendor/mf-core submodule pointer references commit
84fef6b237652a855ab6cfa48768ffe343720ff1 which cannot be fetched; verify that
this commit exists in the upstream repo and that the submodule remote URL is
correct in .gitmodules, then update and reinitialize the submodule: run git
submodule sync && git submodule update --init --recursive (or fetch the missing
commit from upstream), and if the commit is invalid replace the pointer by
checking out a valid upstream commit for vendor/mf-core and update the
superproject commit (git add vendor/mf-core; git commit) so the PR references a
reachable commit.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/host/src/App.tsx`:
- Around line 93-97: The current calls to checkForUpdates() and clearCache()
swallow errors in their .catch(() => {}) handlers; update both call sites (the
useEffect that invokes checkForUpdates and the handleClearCache callback that
calls clearCache) to handle failures instead of silencing them: catch the error,
log it (e.g., console.error or your app logger), and surface user-facing
feedback (toast/notification or alert) so users and devs see the failure; keep
the async calls but replace empty .catch handlers with a handler that accepts
the error and performs logging plus a UI notification.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/host/src/App.tsx`:
- Around line 92-98: The handlers handleCheckUpdates and handleClearCache
currently swallow errors with .catch(() => {}); update both to log the caught
error instead of ignoring it by calling your logger (or console.error) inside
the catch and include a descriptive message and the error object (e.g., "Failed
to check for updates" with err) so failures are visible for users/operators;
apply this change to the promises returned by checkForUpdates and clearCache
within the useCallback wrappers.