fix(desktop): start fresh installs without legacy keychain errors

[leoisadev1]

A fresh Akeru Bot desktop install could prompt for the legacy t3code Safe Storage keychain item and then fail to load the primary environment because the bundled server looked for plugins one directory above the worktree.

The desktop catalog now skips safe-storage access when there is no catalog or legacy connection data, packaged Electron builds use the akeru-bot package identity, and the server resolves plugin catalogs from both the worktree and packaged desktop resource locations.

Verification: focused desktop/server tests pass (71 tests), desktop typecheck completes, the desktop build succeeds, and an isolated Electron launch reaches backend ready and main window created on the attached display.

Created with GPT-5.6 Sol in T3 Code.

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Sep 17, 2026 10:55pm UTC

[greptile-apps]

Confidence Score: 5/5

Safe to merge.

Summary

This PR improves fresh desktop startup by avoiding unnecessary safe-storage access, adopts Akeru’s packaged Electron identity, and resolves the plugin catalog across source, bundled-server, and packaged-resource layouts.

It also adds Changesets and focused coverage for the package identity and catalog resolution paths.

_{Reviews (3) · Last reviewed commit: "fix(server): prefer bundled catalog root..."}