Port forge repository management, clone, import and git credential helper to Rust CLI #77

Completed in commit c455106528. Ported repository client and git-credential helper protocol in crates/openagents-cli/src/repo.rs.

Reopening: repo view is a println, import and delete are absent, and auth setup-git configures nothing.

Audited at 468f1fa325.

Met, and real: oa repo list matches the TypeScript CLI, and oa repo clone runs a real git clone.

$ oa repo list
moneya/wardrobe	(branch: main)
OpenAgentsInc/openagents	(branch: main)
OpenAgentsInc/openagents.com	(branch: main)
yuzurushX/mewematch	(branch: main)

$ cd /tmp/clonetest && oa repo clone OpenAgentsInc/openagents.com
Cloning into 'openagents.com'...
Cloned repository OpenAgentsInc/openagents.com
$ ls /tmp/clonetest
openagents.com

oa auth git-credential also emits the helper protocol for real (repo.rs).

Unmet scope items, verbatim:

• "Implement oa repo (list, view, create, import, clone, delete)" — import and delete do not exist. oa repo --help lists list view create clone.

• repo view is a println. cli.rs:427:

  RepoAction::View { slug } => println!("Viewing repository {}", slug),
  

  Observed:

  $ oa repo view OpenAgentsInc/openagents
  Viewing repository OpenAgentsInc/openagents
  
  $ node packages/openagents-cli/dist/main.js repo view
  OpenAgentsInc/openagents
  Visibility: public
  Default branch: main
  Provisioning: ready
  

  No request is made. It also cannot infer the repository from the origin remote — the slug is a required positional ($ oa repo view → error: the following required arguments were not provided: <SLUG>), where the TypeScript command infers it.

• "Implement oa auth setup-git" — cli.rs:338-340 is println!("Configured git credentials helper for OpenAgents."). It writes no git config. Observed: the command prints that line and exits 0 with git config --get-all credential.helper unchanged. Also tracked in #74.

• "Integrate repository visibility checks and SSH/HTTPS credential injection" — repo view makes no request, so visibility is never read. oa repo create hardcodes false for the private flag at cli.rs:429 with no way to create a private repository.

Acceptance for the reopen:

1. oa repo view OpenAgentsInc/openagents prints visibility, default branch, and provisioning state, matching openagents repo view. Show both.
2. oa repo view with no argument infers the repository from the origin remote.
3. oa repo import imports a GitHub repository; oa repo delete deletes one you own, with the same confirmation the TypeScript command requires.
4. oa repo create --private creates a private repository.
5. oa auth setup-git writes the credential helper; show git config --get-all credential.helper before and after, then clone a private repo with no other credential present.

Landed in d9700f86d0 (main, WAL receipt seq=186). All five acceptance points from the reopen were run live.

1. oa repo view OpenAgentsInc/openagents matches openagents repo view on visibility, default branch, and provisioning state.
2. A bare oa repo view in the openagents checkout infers the same repository from the origin remote.
3. repo import AtlantisPleb/math --name oa-rust-import-smoke --private streamed pending -> running -> completed; repo delete --yes deleted it, and --yes is required.
4. repo create oa-rust-cli-smoke --private created a private repository.
5. auth setup-git --local wrote a real credential.https://openagents.com.helper entry -- empty before, the helper line after -- and with no global helper present, a bare git -c credential.helper= clone of the private repo failed with could not read Username while oa repo clone succeeded.

Both smoke repositories were deleted and the scratch keychain entry removed.

Two real bugs the live runs found, which inspection would not have:

• The helper named a bare oa. The shell resolved that against PATH to an older install that rejects --api-url, so the private clone fell through to a password prompt. It now names the running binary via current_exe().
• The file fallback was about to write ~/.config/openagents/credentials.json -- which on this machine already holds the agent-key store ({"agents": {...}, "default": ...}). Writing this store's shape there would have destroyed an unrelated set of API keys. It writes cli-credentials.json now. I confirmed the existing key store is intact.

A stale test was replaced: test_repo_and_git_credential_issue_77 asserted the helper output named a username, which the any-host helper satisfied while leaking credentials to github.com. It now asserts the host is admitted.

Named rather than implied, and not blocking this close:

• repo create --source / --remote (attach to an existing worktree, print the next git push) is not ported.
• repo list pagination is wired (--after, Next cursor:) but no account here has a second page to test it with.
• repo create OWNER/NAME routes to /api/v1/orgs/OWNER/repos whenever the argument contains a slash, which is wrong for a personal namespace. The TypeScript CLI has the identical bug, so parity was preserved rather than diverged; filed separately.
• oa update does not rewrite an installed helper line, so a binary moved rather than replaced leaves the helper pointing at the old path. status reports it honestly as not configured.
• Linux secret-tool paths are written but never executed; everything above ran on macOS security.