ur-agent 1.78.13 → 1.79.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,49 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.79.0
4
+
5
+ - Plugin discovery now searches managed, personal, workspace, implicit,
6
+ built-in, session, and installed catalogs with deterministic relevance,
7
+ provenance, capability/status filters, secret-redacted source metadata,
8
+ exact detail views, graceful per-catalog failure handling, and structured
9
+ JSON through `ur plugin search` and `ur plugin show`.
10
+ - Research is now evidence-backed rather than a notes-only surface. `ur
11
+ research` creates durable workspaces, records sanitized sources and atomic
12
+ findings, tracks open questions and contested evidence, requires citations,
13
+ warns when high-confidence claims lack independent corroboration, and emits
14
+ verified Markdown reports. The bundled `research-pro` workflow steers the
15
+ agent through current primary-source research and disconfirming evidence.
16
+ - Coding change planning now combines TypeScript compiler-resolved callers,
17
+ import-graph blast radius, definitions, focused tests, related docs/config,
18
+ risk reasons, and detected verification scripts through `ur repo-edit
19
+ impact`. Read-only caller/unused results retain exact references, and
20
+ imported-alias caller resolution now compares both sides of the binding.
21
+ - `ur design3d` adds reproducible Blender Python, OpenSCAD, and Autodesk 3ds
22
+ Max MAXScript projects plus an explicitly reviewed, shell-free adapter for
23
+ Maya, FreeCAD, Houdini, Cinema 4D, Rhino, and other DCC/CAD applications.
24
+ It discovers installed apps, validates workspace-confined manifests, plans
25
+ fixed argv, gates custom execution, builds with bounded time/output, inspects
26
+ GLB/glTF/STL/OBJ/BLEND/MAX assets, and uses the Khronos glTF Validator when
27
+ installed. The bundled `dcc-design` workflow adds unit, scale, parametric,
28
+ interoperability, manufacturing, and native-application verification rules.
29
+
30
+ ## 1.78.14
31
+
32
+ - Interactive prompts no longer create the synthetic `Planning requested work`
33
+ task before the model understands the request. The task surface stays quiet
34
+ for conversation, one-step changes, acknowledgements, and small corrections;
35
+ concrete task boards remain available for multi-step, dependent, delegated,
36
+ or explicitly tracked work. Existing explicit tasks still survive
37
+ interruptions, while legacy automatic placeholders are hidden immediately
38
+ and removed at the next generation boundary without reusing their IDs.
39
+ - Task guidance no longer demands one task for every actionable message. Large
40
+ prompts still decompose into bounded outcome-based tasks, and follow-ups
41
+ update relevant tracked work instead of copying the user's reply into a new
42
+ task title.
43
+ - Security dependency floors now include patched `fast-uri`, `hono`,
44
+ `ip-address`, `undici`, `@hono/node-server`, and MCP SDK releases after new
45
+ registry advisories made the prior lockfile fail the release audit.
46
+
3
47
  ## 1.78.13
4
48
 
5
49
  - The release workflow now publishes its downloaded tarball with an explicit
package/README.md CHANGED
@@ -46,7 +46,15 @@ handing work off to other tools or agents when needed.
46
46
  `ur workspace`, `ur test-first`, `ur ci-loop`, `ur bg`, `ur workflow`,
47
47
  `ur crew`, and `ur automation` for structured work beyond a single chat turn.
48
48
  - **Reliable repo editing.** Use `ur repo-edit` for indexed search,
49
- AST-aware rename plans, patch previews, and rollback-safe multi-file apply.
49
+ compiler/graph change-impact maps, AST-aware rename plans, patch previews,
50
+ and rollback-safe multi-file apply.
51
+ - **Evidence-backed research.** Use `ur research` to persist sanitized sources,
52
+ cited findings, open questions, independent-corroboration checks, and
53
+ reviewable Markdown reports instead of relying on an unstructured note list.
54
+ - **Professional 3D workflows.** Use `ur design3d` for scriptable Blender,
55
+ OpenSCAD, Autodesk 3ds Max, and reviewed custom DCC/CAD app pipelines with
56
+ real-world units, dry-run argv, bounded builds, format inspection, and glTF
57
+ validation.
50
58
  - **Permission and context control.** Use `ur safety` and `ur context-pack` to
51
59
  inspect command risk, initialize project safety policy, summarize repository
52
60
  architecture, and preserve task decisions, constraints, commands, diffs,
@@ -403,7 +411,9 @@ as first-class subcommands in the shipped CLI.
403
411
  | `ur crew` | Run dependency-aware worker subagents over a shared task board; independent tasks fan out, while bounded retries require isolated worktrees. |
404
412
  | `ur pattern` | Run multi-agent collaboration patterns (PEER, DOE, concurrent, handoff, debate, parallel); `--execute` runs them as a workflow. |
405
413
  | `ur goal` | Track long-horizon objectives that persist across sessions. |
406
- | `ur repo-edit` | Build a repo edit index, plan AST-aware renames, preview patches, and apply with rollback. |
414
+ | `ur repo-edit` | Build a repo edit index, map symbol/file blast radius and verification targets, plan AST-aware edits, preview patches, and apply with rollback. |
415
+ | `ur research` | Create source-backed research workspaces, add cited findings/open questions, verify corroboration, and emit Markdown reports. |
416
+ | `ur design3d` | Discover 3D apps and create, plan, build, inspect, or validate Blender, OpenSCAD, 3ds Max, and custom DCC/CAD projects. |
407
417
  | `ur code-index` | Build, query, or watch a local semantic code index using Ollama embeddings; `ur code-index repo` adds files/symbols/calls/tests/docs/configs. |
408
418
  | `ur semantic-memory` | Build and search a project-local memory index. |
409
419
  | `ur memory retention` | Configure and apply local memory retention policies (TTL, max entries, decay). |
@@ -538,6 +548,9 @@ validator, and Markdown language-adapter metadata.
538
548
 
539
549
  ```sh
540
550
  ur plugin list
551
+ ur plugin search git
552
+ ur plugin search --capability skills --json
553
+ ur plugin show github@ur-plugins-official
541
554
  ur plugin doctor
542
555
  ur plugin install engineering-discipline@ur-plugins-official
543
556
  ur plugin install hello@ur-plugins-official
@@ -545,9 +558,15 @@ ur plugin update <plugin>
545
558
  ur plugin disable <plugin>
546
559
  ```
547
560
 
548
- `ur plugin doctor` validates every installed, project, and bundled plugin
549
- manifest and reports its declared components and capability surface, so you can
550
- review what a plugin touches before enabling it.
561
+ `ur plugin search` discovers plugins across managed, personal, workspace,
562
+ implicit, built-in, and session catalogs. Results use deterministic relevance
563
+ ranking, show catalog/source provenance and installation state, support
564
+ capability/marketplace/installed filters, and remain available as structured
565
+ JSON for scripts. `ur plugin show` prints one plugin's complete discovery
566
+ metadata and an exact install command. `ur plugin doctor` validates every
567
+ installed, project, and bundled plugin manifest and reports its declared
568
+ components and capability surface, so you can review what a plugin touches
569
+ before enabling it.
551
570
 
552
571
  The npm package includes `README.md`, `QUALITY.md`, `docs/`, `documentation/`,
553
572
  and `plugins/`, so the npm package page and installed artifact both carry the
@@ -606,6 +625,17 @@ ur desktop-qa validate .ur/desktop-qa/fixtures/smoke.json
606
625
  ur automation create nightly --schedule "0 9 * * 1-5" --prompt "Review open tasks"
607
626
  ur repo-edit preview rename oldName --to newName
608
627
  ur repo-edit apply rename oldName --to newName --check "bun test"
628
+ ur repo-edit impact checkoutTotal --depth 5
629
+ ur research init agent-landscape --question "Which capabilities shipped in 2026?"
630
+ ur research source agent-landscape --url https://example.com/spec --title "Primary specification"
631
+ ur research finding agent-landscape --text "The feature shipped." --cite S1,S2 --confidence high
632
+ ur research verify agent-landscape
633
+ ur research report agent-landscape --out docs/research/agent-landscape.md
634
+ ur design3d doctor
635
+ ur design3d init product-shot --engine blender --units mm --format glb
636
+ ur design3d init studio-scene --engine 3dsmax --units cm --format max
637
+ ur design3d build design3d/product-shot --dry-run
638
+ ur design3d validate design3d/product-shot
609
639
  ur code-index search "where is the rate limiter configured"
610
640
  ur code-index repo build
611
641
  ur code-index repo search "rate limiter"
package/RELEASE.md CHANGED
@@ -90,15 +90,31 @@ GitHub Actions publishes the exact tarball that passes the release workflow.
90
90
  Do not run `npm publish` separately and do not create a tag before the release
91
91
  commit is on the remote branch.
92
92
 
93
- The repository secret `NPM_TOKEN` must be configured before tagging a version
94
- that is not already published. The workflow checks this before it creates the
95
- GitHub Release, preventing a partial GitHub-only release from being reported as
96
- successful. Treat a failed credential preflight as a release blocker; configure
97
- the secret and re-run the same immutable tag rather than publishing manually.
93
+ Configure npm trusted publishing for package `ur-agent` before tagging a version
94
+ that is not already published. In npm package settings, select GitHub Actions
95
+ with owner `Maitham16`, repository `UR`, workflow `release.yml`, no environment,
96
+ and allow `npm publish`. The publish job uses GitHub OIDC (`id-token: write`), so
97
+ it needs no long-lived `NPM_TOKEN` and cannot stall on interactive 2FA. The
98
+ GitHub Release waits for npm publication, preventing a registry authentication
99
+ failure from creating a new partial GitHub-only release. Treat a failed publish
100
+ as a release blocker; fix trusted-publisher configuration and dispatch the same
101
+ immutable tag rather than publishing manually.
98
102
  The npm publish step uses `./dist-release/<tarball>.tgz`: the explicit relative
99
103
  path marker prevents npm from interpreting the artifact name as GitHub
100
104
  `owner/repository` shorthand.
101
105
 
106
+ If an immutable tag failed only during publication, fix the trusted-publisher
107
+ configuration and retry that tag through the default branch workflow:
108
+
109
+ ```bash
110
+ gh workflow run release.yml -f tag=v$(node -p "require('./package.json').version")
111
+ ```
112
+
113
+ Do not move or recreate the tag. Once OIDC publication succeeds, the workflow
114
+ updates or creates the matching GitHub Release from the verified tarball.
115
+ After a successful migration, remove the obsolete `NPM_TOKEN` repository secret
116
+ and revoke that npm token so CI has no dormant long-lived publish credential.
117
+
102
118
  Only after every check passes, commit the complete release and push it:
103
119
 
104
120
  ```bash