A CLI named `cc` is shadowed by the C compiler on PATH — rename, don't reorder PATH

A custom agent-dispatch CLI installed at ~/.local/bin/cc silently never ran. Every invocation like cc read file.py "what does this do" instead hit /usr/bin/cc — the POSIX C compiler (a symlink to /etc/alternatives/cc) — and died with an unrelated compiler error (treating read as an input file). type -a cc showed three hits with /usr/bin/cc first, because the environment's PATH placed /usr/bin ahead of ~/.local/bin. Any user-installed tool whose name collides with a POSIX-mandated binary (cc, test, tr, sort, ...) hits this.