ur-agent 1.69.0 → 1.72.0

package/CHANGELOG.md

@@ -1,19 +1,82 @@
 # Changelog
 
-## 1.69.0
+## 1.72.0
+
+- `AskUserQuestion` no longer rejects a well-formed question because the model
+  named the array something else. The question text accepted eight aliases
+  while the options array accepted exactly one key, and the options check ran
+  first — so a model that sent `choices` was told that *both* `question` and
+  `options` were missing, which is what the error reported. `choices`,
+  `values`, `items`, `alternatives`, `candidates` and `selections` are now
+  accepted, and per-question options that arrive as a JSON string are parsed,
+  which previously only happened for the single-question form.
+- Exiting plan mode no longer prints an error every time it is approved. The
+  tool stays advertised regardless of mode, so once the user accepts, the model
+  routinely calls it a second time against a session that is already out of
+  plan mode — and that was answered with "You are not in plan mode". The echo
+  is now a no-op that tells the model to continue, does not re-prompt for
+  approval, and does not rewrite the plan file with a stale copy. A call with
+  no approved exit behind it still fails, since that one is a real mistake.
+
+## 1.71.0
+
+- Consolidated every UR-branded link onto `ur.com`. 259 references across 106
+  files moved off the retired `ur.ai` and `ur.dev` hostnames. Subdomains and
+  paths are preserved exactly, so `docs.ur.dev/docs/en/sandboxing` became
+  `docs.ur.com/docs/en/sandboxing` and `ur.ai/settings/billing` became
+  `ur.com/settings/billing`. Nothing was flattened to a landing page.
+- Provider, registry and authentication endpoints are untouched, and the
+  rewrite asserts that rather than assuming it: `api.anthropic.com`,
+  `api.openai.com`, `platform.openai.com`, `developers.openai.com`,
+  `ollama.com`, `openrouter.ai`, `registry.npmjs.org`, `googleapis.com`,
+  `huggingface.co`, `modelcontextprotocol.io`, `json-schema.org` and
+  `github.com` all have identical occurrence counts before and after. Anyone
+  connecting to Claude, OpenAI, Ollama or any other provider reaches the same
+  host as before.
+- The substitution is anchored so it cannot match more than it means: a
+  preceding letter, digit or hyphen blocks it, which is what keeps
+  `ur-ai.staging.ant.dev` and hostnames such as `go.dev` and `react.dev`
+  intact. A pattern that matched too broadly is what shipped 1.61.2 through
+  1.64.0 uninstallable.
+- `tipsAreReal` now bans the retired hostnames instead of `ur.com`. It was
+  written when every UR domain was dead, so leaving it would have forbidden
+  links to the current site.
+- The auth token source discriminant follows the domain, from `ur.ai` to
+  `ur.com`. It is computed per session and never persisted, so no stored
+  credential carries the old value.
+
+## 1.70.0
 
 - Rolled the codebase back to the state shipped as 1.65.6. Everything released
   between 1.65.7 and 1.68.19 is withdrawn from this line. The version number
   moves forward rather than back so npm and existing installs upgrade cleanly.
-- No functional change relative to 1.65.6. Commit history for the withdrawn
-  releases is retained and any part of it can be reintroduced in a later
-  release.
+  Commit history for the withdrawn releases is retained and any part of it can
+  be reintroduced later. 1.69.0 was tagged as the rollback point and never
+  published.
+- The task-list gate now ships disabled. It refused the first `Write` of
+  ordinary one-file work often enough that the friction cost more than the
+  plans it produced, and the refusal itself provoked the retry loops 1.65.4 was
+  written to stop. The mechanism is unchanged and returns with
+  `tasks.requireBeforeChanges.enabled=true`.
+- The repeated-failure guard now ships disabled. It was introduced for a 4B
+  model that looped on an identical failing call; on a capable model it mostly
+  fires on legitimate retries and ends the turn. Callers that want loop
+  protection pass an enabled config.
+- Raised the subagent fan-out limits from depth 3 / 20 concurrent to depth 10 /
+  100, with hard ceilings of 64 and 1000. The governor now catches only a
+  runaway tree rather than ordinary fan-out; it is deliberately not removed,
+  because an unbounded tree wedges the host, which is the slowest possible
+  failure.
 - Fixed the packaged-CLI smoke check failing on npm 11 and later. It read the
   `npm pack --json` report as an array, but npm now returns an object keyed by
   package name, so a successful pack was reported as "npm pack did not report a
   tarball" and the release gate failed on every modern npm. Both shapes are now
   accepted. The check lives in `scripts/`, which is not published, so the
   released artifact is unaffected.
+- Unchanged: tool-call validation at the execution boundary still fails closed
+  on unknown tools, duplicate IDs and malformed inputs. It rejects only calls
+  that could not have succeeded, so disabling it would trade clear errors for
+  undefined execution rather than unlocking any capability.
 
 ## 1.65.6