[anned20]

Summary

A network chip next to the Settings gear on the home screen: it shows the link type from webOS' connection manager, then probes a neutral host, because isInternetConnectionAvailable can report true with no uplink.

top chrome
├── #network-status   (home/network-status.ts)
│     start / stop / applyConfig / refresh
│     connection manager -> link type (wifi, ethernet, none)
│     probe -> internet (ok, none)     pause while inactive or saver
└── #app-settings-btn

Clicking the chip opens TV Settings on the network target, falling back to the plain launch that already existed. The chip is optional in Look → Clock & icons.

 config
+29: addNetworkStatus   # showNetworkStatus, defaults true

Call path added to the composition root:

 createApp
+  createNetworkStatus(el, {getConfig, isActive, onOpenNetworkSettings})
   createHomePaint
+  openTvSettings(target)
+    launchSystemApp(id, {target})

Focus changed only so UP from the input row still lands on Settings rather than the new chip; Left reaches the chip.

Evidence

• Before: no network indicator; isInternetConnectionAvailable trusted blindly.
  After: chip driven by a probe with a 10 s confirmation and a 60 s re-check.

npm run typecheck   # clean
npm test            # 53 files, 431 tests passed
  home/network-status.test.ts   298 lines, new
  config.test.ts                +29 migration covered
  settings-panel.test.ts        toggle round-trip covered

No screenshot: the chip needs a running TV or Simulator.

Merge Danger

Door: two-way — reverting drops the chip and leaves the extra optional config key, which normalize ignores.

A config schema bump to 29; the migration only fills a missing showNetworkStatus with true, so settings and restored backups from 28 and older keep working.

Blast Radius: home chrome and the focus row — the widget can be switched off, but by default every home screen gains a chip, and a failed probe turns it to "no internet" until one succeeds.