@nylorun/runtime 0.37.0-beta → 0.39.0-beta

package/CHANGELOG.md

@@ -1,5 +1,96 @@
 # Changelog
 
+## 0.39.0-beta
+
+### Minor Changes
+
+- 67ed2ea: A version that sets `harness.memory.index: false` (`agent-folder/2`, ADR-100) gets no memory index
+  rendered: `turn.start.memory` comes without `index`. The harness may claim `engine.diagnostic`,
+  which the OpenAPI document lists.
+- 67ed2ea: An MCP server that failed at a session's first discovery is tried again at each later turn's first
+  segment, and joins the session's snapshot once it answers: its tools are offered from that turn on,
+  its diagnostic is replaced, and `mcp.discovered` names it again with `rejoined: true`. `session.mcp`
+  takes a later snapshot of servers the session lacks and merges them within `mcpSnapshotBytes`.
+- 67ed2ea: The memory index a session pinned is refreshed at its next turn's first segment (never mid-turn)
+  when another session of the Agent, or the API, wrote the Agent's memory since its last turn started:
+  `turn.start.memory.refresh` (Harness API), and our engine pins the index again (`runDurable`'s
+  `refreshPinned`). The Runtime keeps the newest memory version a turn saw on the session
+  (`Session.memoryIndex`, `memoryWritesSince`). A session's own writes leave its index as pinned.
+- 67ed2ea: A tool policy rule whose `agent` names the session's root agent (its manifest's name) also matches
+  the MCP and HTTP calls of the agents it uses as tools; a rule naming the subagent's id still matches
+  them. `PolicyCall.root` carries the root for a subagent's call. The `agent` selector's contract
+  comments say so.
+- 67ed2ea: A message's `removeTools` (Host feature `remove-tools`): the tools its turn may not use, by name. A
+  declared tool or an agent used as a tool by its name (in the agent and the agents it uses as tools),
+  an MCP server's tool as `<server>__<tool>`, a whole server by its name. The Runtime applies it to the
+  version the turn runs, after the turn's first segment re-pins the session to its Agent's version, so
+  a session that always sends it still moves to new versions; names that version lacks are ignored.
+  A message's turn manifest is validated again against the version a re-pin moves to; one that is no
+  variant of it keeps the turn on the version it pinned (`turn.version_kept`). A variant may narrow an
+  agent it uses as a tool (`isVariantOf`; `withoutTools` in `@nylorun/core/define`). An HTTP tool call
+  is checked against the turn's manifest. `session.input` and `session.inputParts` take
+  `removeTools`.
+- 67ed2ea: Secret routing: the agent folder names, the installation routes (Host feature `secret-routing`, no
+  protocol change). A `bearer` or `headers` secret slot (`runtime.json`, `runtime.secrets`) takes the
+  gateway's `toolPrefix`, with or without `via`, and a slot's value write
+  (`PUT /v1/agents/{id}/secrets/{name}` with `{ value }` or `{ headers }`) takes `via`, with the same
+  URL rules as a slot's. At each request the secret's `via` wins, else the slot's in the version the
+  Agent runs, else none (the slot's `url`); the slot's `toolPrefix` wins over the secret's and
+  applies only with a `via`; the slot's `url` still picks the credential, for MCP servers and HTTP
+  tools alike, and an HTTP tool whose URL has `{field}` parameters still fails behind a `via`. A
+  write whose `toolPrefix` differs from its slot's is accepted, with a warning in the log. A `via` a
+  write copied from its slot follows the slot when the Agent moves, and a fork keeps a secret's own
+  `via`. Secret views show the `via` and `toolPrefix` in force, never a value.
+  `client.agents.secrets.put` takes `{ value | headers, via?, toolPrefix? }` (`AgentSecretRouting`),
+  and `nylorun agents secrets put` takes `--via` and `--tool-prefix`, and a slot's JSON without a
+  `type`. The JSON Schemas that gained the slot's `toolPrefix` are published as
+  `agent-manifest/v8.2`, `runtime-manifest/v1.1` and `agent-folder/v1/runtime.1`, which `nylorun init`
+  maps; the old `$schema` URLs are still read.
+- 67ed2ea: A session records the model its turns call and why (`SessionModelRecord`): `model` on `GET
+/v1/sessions/{id}` is `{provider, model, source: "manifest" | "session" | "tenant", reason?,
+requested?}`, with the fallback's `reason` (`provider_not_connected`, `not_in_catalog`,
+  `invalid_model`) and the model `requested` by the manifest or the session. It is set when the
+  session opens, chooses or clears its model, and again at each segment's start, and each change
+  writes the new `session.model` event with the `previous` record. `SessionView.model` in
+  `@nylorun/agents`.
+
+### Patch Changes
+
+- Pin core to the tested release.
+- Pin harness to the tested release.
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies [67ed2ea]
+- Updated dependencies
+  - @nylorun/core@0.34.0-beta
+  - @nylorun/harness@0.31.0-beta
+
+## 0.38.0-beta
+
+### Minor Changes
+
+- 63a6217: An image can carry the Runtime's engine (ADR-99). A pod of an image the Tenant lists in
+  `engine.images` (`PUT /v1/tenant/sandbox`) runs the engine under `/opt/nylorun` with nothing copied
+  in: the sandboxes service's new `entrypoint: "builtin"`, without the `nylo-copy` init container and
+  the `/nylo` volume. Such an engine reports its Runtime version at join (header
+  `nylorun-image-engine`), the Agent's record keeps it beside its pinned image digest, and a pod runs
+  it only while it is the Runtime's own version; otherwise the engine is copied in as for any image.
+  New column `agents.engine_image` (migration 0042).
+
+### Patch Changes
+
+- Pin core to the tested release.
+- Pin harness to the tested release.
+- Updated dependencies [63a6217]
+- Updated dependencies
+  - @nylorun/core@0.33.0-beta
+  - @nylorun/harness@0.30.1-beta
+
 ## 0.37.0-beta
 
 ### Minor Changes