Installation help — start here

[DivyamTalwar]

Installation is the step most likely to go wrong, and Orrery is deliberately unhelpful in one specific way: it refuses rather than guesses. That means a failed install usually produces an exact, quotable refusal. Bring it here.

Before you post, the quick checks:

bun run ci        # the full offline gate — calls no model, writes nothing outside a temp dir
bun run doctor    # read-only compatibility report for your host

Things that look broken and are not:

• tools-changed — the MCP tool surface no longer matches the content address you approved. This is the rug-pull alarm working. Post both digests; don't re-approve to make it go away.
• "destination is unmanaged" — something Orrery didn't write is sitting at a managed path. It will not clobber it.
• "consent token expired" — tokens are single-use, expire in 10 minutes, and don't survive a restart. Re-run the preview.
• A lane stopped because a model was unavailable — there is no fallback by design. An unavailable pin stops its lane rather than silently substituting a different model.

Codex users: the companion role TOMLs are yours, not the plugin's. Installing or updating the plugin does not register them — run the installer separately and start a fresh task so native discovery sees them.

Cursor users: Cursor 3.15.6 rejects a symlinked local plugin and can't resolve a bare bun from its plugin MCP process. Both are host defects and the canonical package is not bent around them — see docs/cursor-local-install.md for the guarded bridge.

When you post, include your host, your client version, bun --version, your OS, and the exact output. Redact absolute paths; never paste a credential or token.