Found by sweeping every deployed app for imports not reachable from the root's declared dependency closure — the thing `pgh publish` actually stages. pds/bin/pds-serve.js does `await import('favela-community')` for the feed-registry reactor. It was declared only in pds/package.json, so like atproto-did-peer before it, it falls outside the staged closure. Confirmed absent from the DEPLOYED tree on stortron — neither node_modules/ nor pds/node_modules/ has it. The failure mode is WORSE than 0.9.34's, not better. That one crashed loudly on a top-level import. This is a DYNAMIC import inside a try/catch, gated on cfg.feedRegistries — so it would not crash. The import would fail, the catch would swallow it, and the feed-registry reactor would silently never run while the membrane looked healthy. NOT currently firing: prod logs `"feedRegistries":[]`, so the gate is closed and the import is never reached. Latent, not active — it bites the first time someone configures a feed registry. NOT DEPLOYED. The feature is off, so there is no urgency, and I have already taken this membrane down once today. It rides with the next deploy. Remaining sweep findings, all lower severity (they DO ship today, via a declared dep's closure, but by luck rather than declaration): favela-web bare-fs, bare-url, bare-path, bare-os favela-node bare-fs hyper-proto-peer flat-tree, protomux, multiformats pear-git-v3 hypercore, autobase pgh, pgh-sidecar, hypernote and hypermosh-shell are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>