[FIX] bare origin claude syncs workspace symlinks (plugins, sessions, …)

[gradyzhuo]

Summary

Bare claude on origin (CLAUDE_CONFIG_DIR unset) never ran the workspace linker, so ~/.claude's shareable dirs (plugins, sessions, shell-snapshots, session-env, …) stayed per-account real dirs instead of being shared into the workspace — only the legacy base-5 (projects/memory/agents/commands/todos) were linked. Named/pinned accounts (CLAUDE_CONFIG_DIR set) already worked; origin bare launches did not. This is why plugins never became a symlink on a second machine that launches origin directly.

• _prepare-claude-launch --links-only — runs the workspace linker but skips the .claude.json merge. Bare origin reads ~/.claude.json (home), not <accountDir>/.claude.json, so merging there would target the wrong file.
• Resolve the account-dir symlink up front — ~/.claude is a symlink to the origin account dir, and FileManager.contentsOfDirectory(at:) does not traverse a symlinked directory (POSIX EINVAL/ENOTDIR), which would otherwise silently link nothing.
• claude() wrapper — when CLAUDE_CONFIG_DIR is unset and ~/.claude/metadata.json exists, run _prepare-claude-launch --account-dir "$HOME/.claude" --links-only (best-effort; no _capture-claude-exit, since nothing is merged to reconcile).

Result: bare origin launches now share the same dirs as orrery use origin.

Test Plan

• --links-only syncs workspace symlinks without merging .claude.json
• --account-dir follows a symlinked account dir (the ~/.claude origin case)
• claude() wrapper links workspace for bare origin launch (CLAUDE_CONFIG_DIR unset)
• Full suite green (368/368); generated wrapper valid in bash -n and zsh -n
• End-to-end: links plugins (incl. nested content) through a ~/.claude-style symlink; idempotent on re-run
• Adversarial review found no launch-blocking issues

🤖 Generated with Claude Code