feat: self-healing symlinks, project bindings, prompt-indicator, logs (0.22.0)

[Shahinyanm]

Ships the reviewable, verified subset of the shell-UX work from #22. Each feature was rebuilt on current master and checked against real profiles on a live machine.

What's in

Self-healing symlinks. sync / aimux rebuild now prunes a profile's stale links — a symlink pointing at a source entry that no longer exists, or at an entry that has since become private. Before this they piled up silently and aimux doctor could only report them; you had to delete them by hand.

Project → profile bindings. An optional bindings list in config.yaml maps a directory pattern to a profile, so entering a project selects the right subscription. * and ** are supported — use ~/work/** to include subdirectories, since a bare ~/work matches only that directory. Relative patterns anchor to $HOME, never process.cwd(), so a binding means the same directory wherever aimux is run from.

aimux prompt-indicator (alias prompt) — prints the active profile for a shell prompt or Starship. --format '[aimux: %s]' wraps it; every %s is substituted and the name is inserted literally.

aimux logs [session] — view or grep a session transcript (--last, -g <query>) for both claude and codex formats. Colors go only to a TTY, so piping to a file or grep gives clean text; NO_COLOR is respected.

Bug fixed along the way

aimux doctor reported a healthy codex profile as broken. codex's plugins link is adapter-managed (created by extraLinks) and deliberately outside the codex share allowlist, but the prune loop matched it anyway. Result: every sync unlinked and recreated it — a spurious repaired plugins on every aimux run <codex-profile> — and the health sweep listed the same entry as both a conflict and valid. Adapter-managed links are now exempt from both sweeps.

Deliberately left out of #22, and why

• SQLite WAL pragma — a no-op. The session-index DB is a symlink to the source DB that codex already keeps in WAL, and the code shelled out to an undeclared sqlite3 binary whose absence was indistinguishable from success (spawnSync returns {error} rather than throwing, and the result was never checked).
• claude attach — no such subcommand exists (checked against claude 2.1.217). The TUI made it the default action for Enter on a live background session, so the most common interaction returned exit code 1.
• Rate-limit auto-failover — it decided a rate limit had occurred by substring-matching the model's own reply for "429" / "rate limit" / "overloaded", with no loop bound and no CLI filter on the target profile. Asking about HTTP 429 handling would bounce a session between subscriptions indefinitely, each hop a billed turn. This needs a redesign against the real stream protocol, not a patch.

Also note: #22 could not be built at all — src/core/index.ts exported ./logs.js, but logs.ts was never committed (it existed only as an untracked file locally, which is why tests looked green). Those files are included here.

Verification

• 305 tests pass, tsc clean. The codex plugins regression test was confirmed to fail without the fix (expected [ 'plugins' ] to not include 'plugins') and pass with it.
• The bindings test caught a real mistake in my first attempt: expandHome() already resolves a bare relative path against the cwd, so the initial isAbsolute guard never fired. Fixed by testing the raw pattern.
• On real profiles: aimux doctor now reports all four healthy — the self-healing pruned two genuinely dangling links (plans, tasks) that had been stale since April. aimux rebuild of a codex profile is idempotent (repaired: 0 on repeat runs). aimux logs --last | grep emits zero escape codes.

Bumps 0.21.1 → 0.22.0.