ur-agent 1.84.5 → 1.84.7

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog
 
+## 1.84.7
+
+- Replaced NVIDIA's three-model one-shot allowlist with a generated catalog
+  built from the current official LLM, retrieval, visual, multimodal,
+  healthcare, route-optimization, and climate OpenAPI references. The current
+  artifact contains 35 positive agent contracts and 92 exact task contracts;
+  task discovery no longer loses dedicated APIs merely because NVIDIA's chat
+  `/v1/models` inventory omits them. Broken, staging-only, status-only,
+  download-only, and undocumented operations stay hidden.
+- Added real execution for every generated task contract. `NvidiaNimTask` can
+  describe required fields, validate documented request shapes, apply standard
+  prompt/image/query/passages conveniences, send advanced exact JSON, bind
+  local files through JSON pointers, upload and clean up NVIDIA Assets, poll
+  asynchronous requests, and save binary or large JSON output. Requests route
+  to the model's documented `integrate`, `ai`, `health`, `optimize`, or
+  `climate` endpoint with the configured NVIDIA key.
+- Updated `/model`, provider doctor, tests, public docs, the static docs site,
+  and technical references to distinguish live agent inventory from official
+  task contracts and to show what each specialized model is for before use.
+
+## 1.84.6
+
+- Made NVIDIA hosted model selection contract-driven. The authenticated live
+  catalog is now intersected with a reviewed positive list of multi-turn,
+  tool-capable agent contracts, so download-only cards, utility endpoints,
+  single-use functions, and unknown models cannot become the ongoing agent.
+  Custom enterprise/self-hosted NIM gateways continue to use their own saved
+  endpoint and live catalog.
+- Added complete NVIDIA one-shot workflows without replacing the conversation
+  model. `/model` labels eligible FLUX.1 Schnell, Stable Video Diffusion, and
+  PaliGemma entries with their purpose; UR reuses the configured NVIDIA key,
+  dispatches to each exact documented `ai.api.nvidia.com` endpoint, polls
+  asynchronous jobs, and saves JPEG/MP4 artifacts under
+  `.ur/artifacts/nvidia/`. A one-shot entry appears only when the connected
+  account returns it and UR has a complete adapter.
+- Kept NVIDIA media tasks portable across every enclosing agent provider.
+  Generated binary data is decoded locally and the tool result contains only
+  the artifact path or analysis text, avoiding provider-invalid image content
+  inside `tool_result`. Definitive account/function 404s are reported without
+  exposing NVIDIA's internal identifiers and remove the rejected model from
+  the current catalog until refresh.
+- Made structured clarification menus the mandatory path for every real
+  question with concrete choices. Plain text remains available for genuinely
+  open-ended questions, while legitimate menus larger than eight options are
+  preserved instead of failing schema validation. Public, configuration,
+  troubleshooting, validation, and technical documentation now describe the
+  same executable behavior.
+
 ## 1.84.5
 
 - Fixed a provider-wide multi-turn tool-history failure. Some

package/README.md

@@ -405,13 +405,30 @@ In the interactive app, `/model` is a two-step, provider-first picker:
    `static` (predefined), or `unavailable` after a failed discovery with no
    fallback. Local/server providers (Ollama, LM Studio,
    llama.cpp, vLLM, Unsloth) and OpenAI-compatible endpoints are discovered live. Hosted NVIDIA NIM
-   uses its documented `/v1/models` response directly and removes non-agent utility
-   endpoints before presenting a model; the separate NVCF deployment inventory does not narrow it. API
+   intersects its authenticated `/v1/models` response with UR's audited positive
+   agent contracts, so presence in NVIDIA's mixed inventory never makes an
+   embedding, parser, VLM, generator, or download-only card an ongoing chat model.
+   The separate NVCF deployment inventory does not narrow the hosted list. API
    providers use live discovery from their `/models` endpoint once a key is
    connected (with a curated fallback list before that). Subscription CLIs show
    their curated model list because the official CLIs expose no models API. The
    generic `subscription` entry is an internal placeholder hidden from listings.
 
+   NVIDIA is split into two visibly labelled modes. `AGENT` models own the
+   ongoing tool-calling conversation. `ONE-SHOT` models run one specialized
+   job and never replace that agent. The latter come from a checked-in catalog
+   generated from NVIDIA's current public OpenAPI indexes, not from the chat-only
+   `/v1/models` feed. This release implements 92 exact task contracts spanning
+   text/image/video/3D generation, visual analysis, embeddings, reranking,
+   parsing, safety, translation, biology, molecular modeling, medical imaging,
+   route optimization, and climate simulation. Broken, staging-only,
+   status-only, download-only, and undocumented operations stay absent.
+   Focusing a task model shows what it is for; Enter remembers it for the next
+   matching NVIDIA task. UR validates its documented schema, routes to the exact
+   `integrate`, `ai`, `health`, `optimize`, or `climate` host, uploads large or
+   UUID-based files with NVIDIA Assets, polls asynchronous work, and writes
+   binary/large JSON results under `.ur/artifacts/nvidia/`.
+
    In the model catalog, use **Up/Down** to browse. For graded models, the effort row updates to
    the focused model's capability-backed selectors; use **Left/Right** to cycle
    only values UR can map to provider-native levels before pressing Enter. For
@@ -478,8 +495,12 @@ identity line in the system prompt reflects it too:
   `x-api-key` + `anthropic-version` on `/v1/messages`, OpenAI `Bearer` on
   `/v1/chat/completions` by default or `/v1/responses` when explicitly
   selected, Gemini `x-goog-api-key` on `:generateContent`, OpenRouter on its
-  OpenAI-compatible chat endpoint, and NVIDIA NIM on its official hosted or
-  user-selected OpenAI-compatible endpoint.
+  OpenAI-compatible chat endpoint, and NVIDIA NIM agent models on their exact
+  documented hosted chat endpoint or a user-selected compatible NIM gateway.
+  NVIDIA one-shot models use their documented model endpoint across NVIDIA's
+  AI, retrieval, health, optimization, and climate APIs with the same stored
+  `NVIDIA_API_KEY`; asynchronous jobs are polled through NVIDIA's request ID
+  until completion or user cancellation.
 - **Local/server** providers call the configured endpoint (`/v1/chat/completions`
   for LM Studio/llama.cpp/vLLM/Unsloth; the native API for Ollama). Unsloth is
   provider-only: UR never starts, installs, updates, trains, or loads models in