Make harbor auth login the only auth path; snapshot the account at setup

[walkerhughes]

Scopes authentication to the logged-in user and drops the .env credential path added in #2. Net 108 lines removed.

Authentication

harbor auth login mints a key scoped to the logged-in user and stores it in ~/.harbor/credentials.json, which harbor reads on its own. That made most of the previous machinery redundant.

Removed:

• load_dotenv in server.py. Harbor already resolves credentials, so the loader duplicated work for a path we no longer want. server.py is back to 30 lines of glue.
• tests/unit/test_server.py, which only covered that loader.
• The HARBOR_API_KEY passthrough in .mcp.json. HARBOR_MCP_ENABLE_WRITES stays: it is a local toggle, not a credential.

HARBOR_API_KEY still works as an override because harbor itself checks it first. It is now documented as a CI and scripting path rather than an interactive one.

CI is unaffected. The test suite launches the server via sys.executable -m harbor_mcp.server and inherits the process environment, so it never goes through .mcp.json.

Setup skill rewrite

Step 1 is now harbor auth status, replacing four separate bash probes (harbor on PATH, credentials.json present, .env present, key line inside .env).

Two details worth calling out:

• harbor auth status exits 0 whether or not the user is authenticated, so the skill branches on the output string, not the exit code. Keying off $? would report everyone as authenticated.
• whoami is retained as the validator. harbor auth status only reads a local file, so it reports Logged in for a key that has since been revoked or expired. Status proves a credential exists; whoami proves it is live.

The skill falls back to uv run --project ${CLAUDE_PLUGIN_ROOT} harbor auth login, since harbor ships inside the plugin's own environment. Users no longer need a global harbor install to authenticate, so this removes a prerequisite rather than adding one.

Account snapshot

After auth succeeds, setup calls list_jobs once and summarizes into the conversation: total count, the few most recent, anything running or errored.

Deliberately not cached to disk. Reading a cache file costs the agent exactly one tool call, the same as calling list_jobs, so a cache saves nothing on latency or tokens while returning stale data as job statuses flip and costs accrue. The measured payload is 1412 chars for 5 rows, so on-demand is cheap. The transcript is the cache, and it is session-scoped and never misleadingly stale.

check_task_published and resolve_dataset both require an explicit org and name, so there is nothing to enumerate for the registry; the skill skips them.

Verification

Check	Result
Lint	ruff check and format clean
Unit suite	69 passed
harbor auth status, authenticated	Logged in as walkerhughes (API key sk-harbor-mdAIchfaDmNc…)
harbor auth status, empty HOME	Not authenticated. Run \harbor auth login`.` (exit 0 in both cases)
Step 1 fallback, harbor absent from PATH	Resolves via the plugin venv
Plugin launch with HARBOR_API_KEY unset	whoami returns key_source: "file", no key in payload
list_jobs through the plugin	20 of 55 jobs returned

Also splits the two /plugin commands in the READMEs onto separate blocks. Pasting them together lands both lines in the marketplace prompt's input field and fails with a confusing shorthand error.