feat(cli): make edgee alias install PATH shims for non-interactive sh…

…ells

Shell aliases only fire in interactive shells. Tools like agent-deck
spawn Claude via `bash -c 'exec claude ...'` from a Go syscall, which
never sources rc files, so `edgee alias` did nothing for them and
Claude bypassed the gateway.

`edgee alias` now also writes executable shim scripts to
`~/.edgee/bin/{claude,codex,opencode}` and prepends that directory to
PATH in the managed rc block. Each shim strips its own dir from PATH
before `exec edgee launch <agent> "$@"` to prevent recursion, since
`resolve_binary("claude")` resolves through PATH on Unix.

Subtract logic in the rc block is now agent-set-aware: removing one
agent preserves the PATH-export and remaining aliases; removing the
last agent drops the entire block.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Replace image in README with updated asset

Updated image link in README and added a new image.

fix(launch): forward --help to underlying agent binary

Clap auto-generates --help / -h on every subcommand parser, so `edgee
launch claude --help` (and the `claude --help` shell alias) was showing
Edgee's subcommand help instead of forwarding --help to the real Claude
Code binary. Same for codex and opencode.

Disable the auto-help flag on the three launch Options structs so --help
falls through to the trailing_var_arg Vec and reaches the inner binary
via cmd.args(&opts.args). Top-level `edgee --help` and `edgee launch
--help` are unaffected.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chore: add claude md file

chore: bump edgee-compressor to 0.1.1 (#65)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Julianne H. <julianne@edgee.ai>

chore(compressor): add license, description, homepage and repository …

…fields (#64)

fix(launch): Windows binary resolution for claude, codex, and opencode (

#58)

* fix(launch): resolve CLI binaries on Windows via PATH+PATHEXT and npm fallback

On Windows, `Command::new("opencode")` (and claude/codex) can fail to
find npm-installed binaries because npm creates `.cmd` shims that aren't
always resolved by Rust's standard PATH lookup. This adds a shared
`resolve_binary()` helper that explicitly searches PATH with PATHEXT
extensions and falls back to the npm global prefix directory.

Also fixes OpenCode config file discovery on Windows by checking
USERPROFILE and APPDATA in addition to HOME.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix(launch): prefer PATHEXT extensions over bare binary on Windows

Nodist (and similar tools) create both an extensionless `opencode` file
and a working `opencode.cmd` shim in the same directory. The bare file
can be broken/incompatible while the .cmd wrapper works correctly.

Match Windows shell behavior by checking PATHEXT extensions first,
falling back to the bare name only if no extension match is found.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* refactor(launch): use which crate for Windows binary resolution

Replace hand-rolled PATH + PATHEXT lookup with the `which` crate.
Its GetBinaryTypeW-based executability check naturally rejects the
bare extensionless Nodist shim and falls through to the .cmd wrapper,
preserving the behavior added in 9166494. The npm global prefix
fallback is kept for cases where the binary isn't on PATH.

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(login): persist env-var URL overrides into profile on setup

feat(alias): add alias command to set up shell integration (#47)