swarm-ui: PWA follow-ups from review

- manifest.webmanifest: mara — "name should be hyperhive", was
  "hyperhive swarm".
- sw.js: argus — cache-write path didn't check response.ok before
  caching; an error response would get served back as if it were the
  real asset on the next offline/failed fetch.

frontend/packages/swarm-ui/src/manifest.webmanifest

@@ -1,5 +1,5 @@
 {
-  "name": "hyperhive swarm",
+  "name": "hyperhive",
   "short_name": "swarm",
   "description": "Swarm-level operator UI — agent roster, hives, jobs, issues across the swarm.",
   "start_url": "/",

frontend/packages/swarm-ui/src/sw.js

@@ -100,8 +100,14 @@ self.addEventListener("fetch", (event) => {
   event.respondWith(
     fetch(event.request)
       .then((response) => {
-        const copy = response.clone();
-        caches.open(CACHE_NAME).then((cache) => cache.put(event.request, copy));
+        // Only a genuinely good response is worth caching — an error
+        // response (a 404/500, or a proxy hiccup wearing a 2xx-adjacent
+        // status) would otherwise get served back as if it were the real
+        // asset on the next offline/failed fetch.
+        if (response.ok) {
+          const copy = response.clone();
+          caches.open(CACHE_NAME).then((cache) => cache.put(event.request, copy));
+        }
         return response;
       })
       .catch(() => caches.match(event.request)),