fix(app-session): read gateway descriptor version 3

[nicolasmertens]

Problem

Current Grok Bot desktop builds write gateway-descriptor.json with "version": 3. Every command that needs the app session then fails:

$ gbot bots list --json
{"error":{"code":"render-failed","message":"Unsupported Grok Bot gateway descriptor version 3."}}

Seen on macOS with gbot 0.12.4.

What v3 looks like

Same wrapper layout as v2, plus a savedAtMs timestamp per entry:

{ "version": 3, "entries": { "<hash>": { "savedAtMs": 1791320229049, "encrypted": "..." } } }

The decrypted payload still carries baseUrl, token and headers, plus a new vncProxy block that the CLI doesn't need.

Change

• encryptedPayload accepts version 3 and reads it the same way as version 2.
• The multiple-entries AMBIGUOUS_ENTRIES safety check is unchanged (see Support explicit account/gateway-entry selection for multi-account Grok Bot desktop sessions #102).
• Tests: added "loads a version 3 descriptor" and "rejects a version 3 descriptor with ambiguous entries". The unsupported-version test now uses version 4.
• Added a changeset (patch) and rebuilt artifact/.

Verification

• npm test: 444 pass, 0 fail. npm run validate:artifact: passes.
• Against a live Grok Bot desktop session on macOS, the patched build returns the bot list; gbot doctor reports Grok Bot app session: usable.

🤖 Generated with Claude Code

https://claude.ai/code/session_01F7jcCQRFPBA9cNGeLvEoJi

[changeset-bot]

🦋 Changeset detected

Latest commit: e9ac663

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
grok-bot-cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR