Update to Qodo

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -4,7 +4,7 @@
 owner: Qodo
 metadata:
   vendor: qodo
-  version: "1.0.9"
+  version: "1.0.11"
   recommended: "true"
   package: "qodo"
   distribution: "marketplace"
@@ -15,68 +15,71 @@
 
 ## Description
 
-Install, connect and verify Qodo in this conversation. Plugin installation does not connect an account.
+Verify the available Qodo path. Skill installation does not prove account or tool access.
 
 ## Prerequisites
 
-A shell and browser sign-in. Never request or read credentials.
+A shell for CLI setup or a host-connected QAR MCP server. Never handle credentials.
 
 ## Instructions
 
+### Connected MCP path
+
+Inspect connected QAR tool schemas and annotations. With harmless input, call one
+read-only tool; catalog visibility does not prove read access. Check `isError` before
+`structuredContent`; an execution error is not readiness. A read cannot prove write
+authorization: report writes as unverified until a user-authorized action. Never make
+a test write. The host and QAR own MCP auth. Report missing tools, `MT-AUTH-FORBIDDEN`,
+and connection errors as MCP access issues; never ask for an API key. For MCP-only setup,
+report the verified scope and hand off here. Skip every CLI step below. Continue only if CLI access was
+requested or is needed for local collection, using the same deployment.
+
 Resolve `references/...` links relative to this installed `SKILL.md` directory.
 Runtime/login setup does not authorize enterprise installation or maintenance.
-For a separately requested enterprise install, disclose installations, packages and verified-source automatic
-maintenance before approval. Preserve opt-outs, edits, owners and optional-package choices.
+For requested enterprise installs, disclose packages and maintenance before approval;
+preserve opt-outs, edits, owners and optional-package choices.
 
 ### 1. Find or install the runtime
 
-Run:
+In PowerShell, resolve the verified native/Node invocation in [runtime.md](references/runtime.md)
+first; `qodo` below represents that invocation. On POSIX, probe PATH directly:
 
 ```sh
 qodo --version
 ```
 
-If missing, try `"${QODO_HOME:-$HOME/.qodo}/bin/qodo" --version` on POSIX.
-For PowerShell or a missing CLI, read [runtime.md](references/runtime.md).
-Follow that procedure and continue. Setup requests cover CLI installation, subject to host
-approvals and user restrictions. Plugin installation alone is not authorization.
+If missing on POSIX, try `"${QODO_HOME:-$HOME/.qodo}/bin/qodo" --version`.
+For a missing, old or unparseable runtime, follow the reference. Setup requests cover installation subject
+to host approvals; plugin installation alone does not. Retain the selected deployment.
 
-Keep the working executable as `<qodo>`. Require Qodo CLI **0.1.0-next.37 or newer**.
-If older or unparseable, follow the runtime reference before any authenticated command.
+Keep the executable as `<qodo>`. Require Qodo CLI **2.0.0 or newer** before authentication.
 
 ### 2. Connect
 
 Run:
 
 ```sh
-<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.9 --distribution marketplace --host codex
+<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.11 --distribution marketplace --host codex
 ```
 
-If successful, retain the verified identity and continue to step 3 without repeating it.
-For a failed check, read [authentication.md](references/authentication.md) to distinguish
-missing credentials, sandbox access, and other failures before choosing login.
-
-For Qodo Cloud, announce and run `<qodo> login` when signed out. For any customer deployment,
-read the authentication reference first: preserve its exact login endpoint and never guess
-or fall back to Cloud. Wait for login to finish, then rerun the identity command above.
-Browser opening alone is not success.
-
-Remember the execution context where identity or login worked. Use that context for later
-credential-dependent commands, requesting each required host approval; a diagnostic approval
-does not grant blanket permission. Do not repeat a known-failing sandbox probe after login.
-Stop on cancellation or denied permission.
+Reuse a successful identity check. On failure, read
+[authentication.md](references/authentication.md) before choosing login.
+
+For Cloud, run `<qodo> login` when signed out. For customer deployments, preserve the
+documented login endpoint; never fall back to Cloud. Wait for login, then recheck identity.
+
+Reuse the successful execution context, requesting each required host approval. A diagnostic
+approval is not blanket permission. Stop on cancellation or denied permission.
 
 ### 3. Verify tools
 
 Only after identity succeeds, run:
 
 ```sh
-<qodo> tools --refresh --json --skill qodo-setup --skill-version 1.0.9 --distribution marketplace --host codex
+<qodo> tools --refresh --json --skill qodo-setup --skill-version 1.0.11 --distribution marketplace --host codex
 ```
 
-Require a successful, nonempty usable catalog. Inspect status, errors and relevant tool names;
-do not dump every schema. When unblocking an existing task, check its required capability;
-an unrelated catalog does not establish access.
+Require a usable catalog and the task's capability; unrelated tools do not establish access.
 If refresh fails, report that sign-in succeeded but tools are unavailable, with the exact error
 and `<qodo> tools --refresh` as the retry. Do not log in again for a catalog failure.
 
@@ -94,7 +97,5 @@
 
 ## 4. Hand off
 
-For setup alone, confirm Qodo connection and catalog readiness and suggest one supported next action.
-When unblocking an authorized task, return to it after its prerequisites pass. Readiness does not
-prove retrieval, review, or write success. Name the deployment when useful. Do not start unrelated
-work or install optional Standards.
+Confirm Qodo connection and relevant tool readiness, then return to the authorized task.
+Readiness does not prove a later tool call succeeds. Do not install optional Standards.