release(runtime): publish a coherent eval/interface/knowledge cohort

[drewstone]

Problem

The Intelligence product currently pins Runtime 0.103.1, Eval 0.125.0, Interface 0.33.0, and Knowledge 4.1.0. The registry’s independently newest releases cannot be installed together: Runtime 0.105.0 requires Eval >=0.126.6 <0.127.0, Interface >=0.32.0 <0.33.0, and Knowledge 5.0.1, while latest Eval/Interface/Knowledge are 0.129.0/0.34.0/6.0.0.

Updating the product package-by-package would create a broken dependency graph or force an unpublished local link.

Required outcome

Publish one tested Runtime cohort whose declared dependencies and peer ranges accept one exact released Eval, Interface, Knowledge, and Sandbox set. Release notes should name the compatible versions.

Adoption proof

A follow-up product PR updates the root overrides, direct package dependencies, lockfile, and relevant API integration checks together. It must install cleanly with registry packages only; no /tmp, workspace link, or local fork.

Non-goal

Do not add a network-dependent latest-version CI check. Compatibility belongs in the released package graph; product adoption stays an explicit, tested update.

[drewstone]

Fresh adoption check on 2026-07-26:

The Runtime 0.106 cohort cannot be published from Runtime alone. The newest public agent-profile-materialize is 0.8.0 and pins agent-interface 0.33.0. The product has local materializer 0.9.0 on agent-interface 0.34.0, but 0.9.0 is not published.

Release order needed:

1. publish agent-profile-materialize 0.9.0 with Interface 0.34.0;
2. test and publish Runtime against Eval 0.129.0, Interface 0.34.0, Knowledge 6.0.0, and Materialize 0.9.0;
3. update the product atomically from registry packages only.

Product tracking: https://github.com/tangle-network/agent-dev-container/issues/4183

[drewstone]

Audit against origin/main@15f1ee3e5caae0a953e92645748b30ae30a2b07f and published Runtime 0.109.0: keep open.

The release half is complete. Commit d55257374258ab71d0e0b8dea3e872b9391e9eb6 (PR #651) published Runtime 0.109.0; its four CI jobs passed, with 1,856 Runtime tests passing, 6 skipped, and 0 failed. A fresh empty npm project installed Runtime 0.109.0, Eval 0.135.1, Interface 0.36.0, Knowledge 6.1.10, and Sandbox 0.15.2 from https://registry.npmjs.org/; npm ls resolved one Interface version, the root, /kernel, /intelligence, and /knowledge imports loaded, and npm audit found 0 vulnerabilities across 32 dependencies.

The required product adoption is not recorded. tangle-network/agent-dev-container#4183 is still open with the coherent-cohort checkbox unchecked and no comments, and a repository PR search for 0.109.0 returned no adoption PR. The 0.109.0 changelog names Eval and Knowledge, while Interface and Sandbox compatibility appears only in docs/canonical-api.md and npm metadata. Close this after one product PR updates overrides, direct dependencies, lockfile, and integration checks together from registry packages only, and the release entry names the full tested set.

[drewstone]

Disposition after the final release cascade: keep open for the explicit product adoption.

The coherent published set now exists: Runtime 0.109.2, Eval 0.135.2, Interface 0.36.0, Knowledge 6.1.11, Materialize 0.9.2, Sandbox 0.15.2, and Bench 0.4.9. Agent App 0.44.52 is also live; both generated templates install Runtime 0.109.2 and Eval 0.135.2 from the registry, and the release run passed clean installs, typecheck, tests, Worker dry runs, exact archive inspection, and both npm publications.

The issue still requires adoption in the named product. Read-only check of tangle-network/agent-dev-container#4183 on 2026-07-29 shows it is open and its coherent-cohort checkbox remains unchecked. Agent App templates are useful downstream adoption, but they are not that product update. Close #623 only after the product updates its direct dependencies, overrides, lockfile, and integration checks together from registry packages.