refactor(features): drop unnecessary resident tiles; manifest is the only truth
Removes resident: true from features whose home tiles do not need a
persistent background renderer at startup, and deletes the
EAGER_TILE_IDS plumbing that hard-coded entities as eager from
main.ts.
Why:
- Several feature manifests declared resident: true purely so a UI
tile would be ready on first open, not because they had any
startup side-effects or background work. Each one cost a
BrowserWindow at boot and showed up as "hidden" in the Windows
feature, confusing the user.
- EAGER_TILE_IDS was a side-channel that could mark a tile eager
even when its manifest said otherwise. The manifest should be the
only declaration of resident vs lazy.
Changes:
- Drop resident: true from hello-world, lex, lists, widget-demo
manifests. Their commands or home tiles open on demand and have
no startup pubsub work.
- Kept resident on entities (page:content-ready listener),
websearch (page:loaded for OpenSearch discovery), tag-actions
(RPC handler for tag-actions:get-all published by groups,
search, tags, pagestream).
- Remove EAGER_TILE_IDS constant and its pass-through from
main.ts -> feature-startup -> tile-loader -> tile-compat.
shouldLazyLoad is now just !residentEntry.