melchizedek-agents 1.0.1 → 1.0.3

package/CHANGELOG.md

@@ -6,6 +6,84 @@ the starter pack and the templates), not the repo's full history.
 
 ## Unreleased
 
+## 1.0.3 — 2026-10-09
+
+Dependency updates and one packaging fix. No export, bin, YAML key or
+adapter behaviour changes; no source file under `lib/` changes.
+
+### Fixed
+
+- **`config/agents/syndicate.schema.json` ships in the package.** The
+  shipped `config/agents/syndicateSchema.yaml` names it in its
+  `yaml-language-server` modeline, and `melchizedek-init` locates the
+  package root by it; it was missing from `files`, so editors could not
+  resolve the schema and, in an installed package, `melchizedek-init`
+  stopped with "config/agents/ not found next to this package".
+  `tests/packageSurface.test.ts` now checks that `files` ships it and
+  every shipped modeline's target.
+
+### Changed — dependencies
+
+- `@anthropic-ai/sdk` ^0.129.0 → ^0.131.0. Additive (Admin and Managed
+  Agents endpoints). The SDK now marks `claude-sonnet-4-5` and
+  `claude-sonnet-4-5-20250929` deprecated (end of life 2026-11-30) and
+  logs a `console.warn` when a request names them; no shipped syndicate
+  uses either id.
+- `openai` ^7.23.0 → ^7.28.0. Additive (Agents, Realtime, Responses
+  WebSocket features). The client now keeps a base URL's query string
+  when joining endpoints; this reaches the GPT adapter only when
+  an `OPENAI_BASE_URL` carries a query (the Azure and xAI base URLs carry none;
+  the Kimi, Ollama and gateway adapters do not use the SDK).
+- `@modelcontextprotocol/sdk` ^1.29.0 → ^1.32.1 (lock 1.31.0 → 1.32.1).
+  The SDK's HTTP client transports now follow redirects only within the
+  endpoint's origin unless `redirectPolicy: 'follow'` is set. The MCP
+  client's own fetch (`mcpFetch`, `lib/net/redirects.ts`) already follows
+  every hop itself under `MCP_REDIRECTS`, so the SDK sees the final
+  response and redirect behaviour is unchanged.
+- `@google/genai` 2.25.0 → 2.27.0, still pinned exact. Additive
+  (`continuation_token` in GenerateContent and Interactions, new model
+  enum values).
+- `@types/node` ^22 → ^25 (dev only). `engines.node` stays `>=22.6.0`; the
+  source type-checks against both the Node 22 and Node 25 types.
+- Dockerfile base image `node:22-slim` → `node:25-slim`, pinned by digest.
+
+## 1.0.2 — 2026-10-09
+
+A test and documentation patch. Nothing a consumer imports, configures or
+runs changes behaviour, and no YAML key is added, removed or renamed.
+
+### Fixed
+
+- **`npm test`, and so `npm publish`, pass again from 2026-10-09.** The
+  harness-example parity test (`tests/skillHarness.test.ts`) compared a
+  native run against a recording made on 2026-10-08, and the
+  `{{current_date}}` the example's instruction resolves moved with the
+  clock, so from 2026-10-09 the comparison failed. The test now pins
+  `current_date` to the recording's date.
+- **The SIGTERM test holds under load.** `tests/serverShutdown.test.ts`
+  waits up to 30 seconds for the server to start, polls for readiness to
+  fail after the signal instead of checking once after a fixed 300 ms,
+  and runs with a 3-second delay and a 6-second grace budget, so a busy
+  machine no longer fails it on timing.
+
+### Changed
+
+- **Wording only: the shipped files describe the engine, not ADK.** The
+  example syndicates' comments (`critic.yaml`, `scribe.yaml`,
+  `research.yaml`, `image_production.yaml`, `librarian.yaml`,
+  `weather.yaml`, `pipeline.yaml`), `config/agents/syndicateSchema.yaml`,
+  `DOCUMENTATION.md` and the `melchizedek-author` skill no longer describe
+  Google ADK as running or enforcing anything; ADK appears only as history
+  or as the origin of a key's spelling. The rule that an `outputSchema`
+  belongs on a leaf is stated as what it is: the engine accepts the schema
+  on an agent that delegates, and that agent then answers with the JSON
+  instead of relaying a subagent's answer. The same wording reaches the
+  schema descriptions in `lib/syndicateSchema.ts` and the generated
+  `config/agents/syndicate.schema.json` (`outputSchema`, the root agent,
+  the workflow `retry` defaults, `retries`), and the reserved-name message
+  for an agent called `user`. No key, default or behaviour changes;
+  `thinkingBudget` and the other older spellings are still accepted.
+
 ## 1.0.1 — 2026-10-08
 
 ### Fixed

package/DOCUMENTATION.md

@@ -141,7 +141,7 @@ Field reference:
 | `yaml_reference` | subagent | Mount another syndicate file as a nested subagent. |
 | `a2a_agent_url` | subagent | A REMOTE agent over A2A (§6): the orchestrator delegates to it with one `request` argument; in plan-dispatch it can be a route. No `model`/`instruction` — the remote agent has its own. Credentials come from `A2A_AGENT_TOKENS`, never YAML. |
 | `max_steps` | root | Cap on model calls per turn, counted across every agent the turn reaches (orchestrator, subagents, nested syndicates). Exceeding it fails the turn with `STEP_LIMIT`. |
-| `includeContents` / `outputKey` / `globalInstruction` / `disallowTransferToParent` / `disallowTransferToPeers` | agent | Passed through to the agent (the names are ADK's `LlmAgent` fields). `includeContents: none` makes an agent see only the current message. |
+| `includeContents` / `outputKey` / `globalInstruction` / `disallowTransferToParent` / `disallowTransferToPeers` | agent | Passed through to the agent (spelled after ADK's `LlmAgent` fields). `includeContents: none` makes an agent see only the current message. |
 | `fallback_model` | any agent | A model, ideally on another provider, that answers when this agent's model fails provider-side (5xx, 429, a connection reset, after its own retries) before producing any output, or while that provider's circuit is open: after `MODEL_BREAKER_THRESHOLD` consecutive provider failures (default 5; 0 disables) the provider is skipped for `MODEL_BREAKER_COOLDOWN_MS` (default 30 s). A 4xx and a canceled turn are never redirected, and a stream that already produced text is never replayed elsewhere ([ADR 0044](./wiki/decisions/0044-fallback-model-and-circuit-breaker.md)). |
 | `mcp_tools` | subagent | The MCP server's tools this agent may use; any other tool the server lists is not exposed. On a dispatch route `require_approval` may name them ([ADR 0041](./wiki/decisions/0041-tool-vendors-get-least-privilege.md)). |
 | `mcp_server_url` | subagent | Discover this subagent's tools from a remote MCP server at load time (§3). SSRF-guarded; `ALLOW_PRIVATE_MCP=true` permits localhost for development. |
@@ -178,7 +178,7 @@ function, and every adapter recognises it by marker
 | `google_search` | Gemini built-in | Live web search — Gemini agents only (legacy alias; use `web_search`). |
 | `preload_memory` | Instruction tool | Silently injects similarity-matched facts into every request's instruction (ambient recall). The model never calls it. |
 | `load_memory` | Contract | Explicit tool call to search the fact store (deliberate recall). Both memory tools read the caller's own silo only and send the model what ADK's tools of the same names sent ([ADR 0059](./wiki/decisions/0059-memory-on-the-engines-own-interfaces.md)). |
-| `generate_image` | Contract | Calls the Gemini image model directly, saves the result under `outputs/`, returns the path. A function tool because binary `inlineData` cannot survive the AgentTool text boundary. |
+| `generate_image` | Contract | Calls the Gemini image model directly, saves the result under `outputs/`, returns the path. A function tool because binary `inlineData` cannot survive delegation, where a subagent returns only its final text. |
 | `inspect_image` | Contract | **Blind visual inventory** of a file under `outputs/`: subjects with exact counts, composition, light, palette, medium cues, artifacts — zero quality judgments. Its signature accepts *only* a file path, so an orchestrator cannot leak expectations into the observation (see `image_production.yaml`). |
 | `task_add` / `task_list` / `task_get` / `task_update` | Contract | A to-do list and job queue. Default: a single-user JSON file (`MELCHIZEDEK_TASKS_FILE`, default `outputs/tasks.json`), so every caller of a shared endpoint shares one list. With `DATABASE_URL` (migration 0009) each caller has its own list, scoped by the caller's scope key, and any number of workers take jobs safely. |
 | `ask_user` | Contract, long-running | Asks the person one question (optionally with `options`) and ends the turn `input-required`; the next message on the conversation is the call's result. Orchestrator or plan-dispatch route only (§6, Questions). |
@@ -575,7 +575,7 @@ Model floor: agent transfer (subagent delegation) requires
 `gemini-3.8-flash` or newer — older flash models reject it with
 `[400] Tool call context circulation is not enabled`. For `ollama/*`
 agents the equivalent floor is tool-calling support in the model
-itself; delegation is exercised through AgentTool function calls.
+itself; delegation runs through ordinary function calls to the subagent tools.
 
 ## 6. A2A service mode
 
@@ -1055,7 +1055,7 @@ user:
 
 | | DELEGATE (default) | PLAN-DISPATCH (`dispatch:` present) |
 |---|---|---|
-| Subagents are | `AgentTool`s on the orchestrator | plain configs the server selects from |
+| Subagents are | tools on the orchestrator | plain configs the server selects from |
 | Orchestrator holds | subagent tools, no `outputSchema` | an `outputSchema`, no subagent tools |
 | Routing decision is | implicit in which tool it calls | an explicit value in code |
 | The final answer comes from | the orchestrator re-emitting the answer | **the specialist itself** |
@@ -1089,9 +1089,11 @@ emitted the bare tool name in place of a 2,599-character answer.
 Plan-dispatch has no relay turn to fail, and the classifier's output
 shrinks from a whole relayed answer to ~15 tokens of JSON.
 
-**Why the classifier is tool-less.** Structured output does not combine
-with delegation on one agent (see `config/agents/examples/critic.yaml`,
-whose header tells how an orchestrator holding both deadlocked on ADK).
+**Why the classifier is tool-less.** An agent that holds an
+`outputSchema` answers with that JSON and nothing else, so the schema sits
+on a leaf that delegates nothing (see `config/agents/examples/critic.yaml`,
+whose header also tells how an orchestrator holding both deadlocked on
+ADK before 1.0.0).
 That constraint shapes the method: the classifier is a leaf, and the
 hand-off happens in code, where it can be logged, traced, and streamed
 to the user as progress.
@@ -1100,8 +1102,8 @@ to the user as progress.
 one transcript accumulates across routes and long-term memory ingests
 real answers instead of a relay copy of them. Sharing the session is
 necessary but not sufficient: a stored event is rendered by comparing
-`event.author` against the agent now running (ADK's rule, which the native
-loop keeps), and under plan-dispatch
+`event.author` against the agent now running (the rule ADK had, which the
+engine's loop keeps), and under plan-dispatch
 every route is its own root agent, so the whole history fails that
 comparison and `convertForeignEvent` rewrites it to `role: "user"`
 prefixed "For context:". A route reading the raw shared session

package/config/agents/examples/critic.yaml

@@ -1,15 +1,20 @@
 # tier: gemini  — needs only GOOGLE_GENAI_API_KEY; `npm run doctor` shows what each key unlocks.
 syndicate_name: "Critic Review Workflow"
 
-# WHY this structure: The ADK enforces that outputSchema cannot co-exist with
-# agent transfer (AgentTool) on the same agent. If the orchestrator has both,
-# the ADK deadlocks it. Solution: the orchestrator is a plain sequencer that
-# routes Drafter → Critic, and the CriticAgent (a leaf with no tools/transfers)
-# owns the outputSchema for structured JSON production.
+# WHY this structure: an agent with an outputSchema answers in that schema and
+# nothing else. On an orchestrator that delegates, the engine (on most
+# models) adds a set_model_response tool beside the subagent tools and the
+# turn ends on the JSON it receives (lib/runtime/native/request.ts), so the
+# user would get the review object instead of the answer; under Google ADK,
+# before 1.0.0, an orchestrator holding both deadlocked. Solution: the
+# orchestrator is a plain sequencer that routes Drafter → Critic, and the
+# CriticAgent (a leaf with no tools and no subagents) owns the outputSchema
+# for structured JSON production.
 #
 # WHY multi-turn internal looping:
-#   The ADK's runAsync keeps executing within a single user turn as long as the
-#   orchestrator continues to call tools rather than producing a final response.
+#   The engine's agent loop keeps executing within a single user turn as long
+#   as the orchestrator continues to call tools rather than producing a final
+#   response (lib/runtime/native/agentLoop.ts, capped by max_steps).
 #   By instructing the orchestrator to inspect the CriticAgent's confidence score
 #   and re-delegate when it's below a threshold, the syndicate autonomously
 #   refines answers through multiple Drafter→Critic passes — all within one

package/config/agents/examples/image_production.yaml

@@ -16,8 +16,8 @@ memory_system: "session-only"
 #   path — the spec physically cannot reach the inventory, so expectation bias
 #   is blocked by the tool signature, not by good intentions. SpecAuditor is a
 #   text-only leaf that receives spec + inventory but never the image, and
-#   holds the outputSchema (same ADK constraint as critic.yaml: schema-holders
-#   get no transfer powers). Perception, judgment, and decision are three
+#   holds the outputSchema (the same rule as critic.yaml: the schema-holder
+#   is a leaf that delegates nothing). Perception, judgment, and decision are three
 #   different minds.
 #
 # WHY the instruction maps payload fields to tool parameters by name

package/config/agents/examples/librarian.yaml

@@ -7,7 +7,7 @@
 # subagent declares NO tools of its own — its entire capability
 # arrives at runtime from an MCP server (mcp_server_url below).
 # The framework dials the server, asks "what tools do you offer?",
-# and wraps each answer as a live ADK tool (lib/tools/mcpToolFactory.ts).
+# and wraps each answer as a live engine tool (lib/tools/mcpToolFactory.ts).
 #
 # That is the point of MCP: the agent's reach is no longer fixed
 # at design time. Point the same agent at a different server and

package/config/agents/examples/pipeline.yaml

@@ -9,7 +9,7 @@
 # what they produce, edit it, ask the person, then publish". A
 # `workflow:` block says exactly that: the agents below are the
 # nodes of a graph, and `edges` says what runs after what
-# (lib/workflow.ts; ADK's Workflow underneath).
+# (lib/workflow.ts; the engine's own scheduler, lib/workflow/, runs it).
 #
 #   START → Planner ─(article)→ Writer ──┐
 #                    │                  ├→ Both → Editor → Confirm → Publisher

package/config/agents/examples/research.yaml

@@ -12,8 +12,9 @@
 # SHAPE: plan-dispatch (lib/dispatch.ts). A small triage model names one of
 # three routes, and that route's output IS the answer. Each route HOLDS its
 # own tools instead of delegating to researcher subagents. That choice is
-# deliberate: ADK's AgentTool returns only a subagent's final text, so tool
-# output from a delegated subagent never reaches the outer stream, and the
+# deliberate: the engine's subagent tool returns only a subagent's final text
+# (lib/runtime/native/delegate.ts), so tool output from a delegated subagent
+# never reaches the outer stream, and the
 # `science` guard below checks the answer against exactly that output. When
 # the answering route makes the calls itself, every identifier it cites is
 # on its own stream. It also means an A2A client sees each tool call live.

package/config/agents/examples/scribe.yaml

@@ -36,10 +36,11 @@
 # the two lists lived apart they drifted, and drafts failed rules the
 # writer had never been given. Edit the rule in one place.
 #
-# WHY the orchestrator has no outputSchema: the ADK does not let
-# an agent hold both an outputSchema and AgentTools, so the JSON
-# contract sits on the Auditor (the leaf) and the Scribe returns
-# plain text. See critic.yaml for the same constraint.
+# WHY the orchestrator has no outputSchema: an agent that holds
+# one answers in that JSON and nothing else, and the Scribe's answer
+# is the document. So the JSON contract sits on the Auditor (the
+# leaf) and the Scribe returns plain text. See critic.yaml for the
+# same rule.
 #
 # Run it:  npm run syndicate:scribe
 #          npm run syndicate:scribe -- "$(cat brief.md)"     # one shot

package/config/agents/examples/weather.yaml

@@ -7,7 +7,8 @@
 # that uses it. No tool code: the `openapi:` list below points at two
 # spec files, and every operation in them becomes a tool, its
 # parameters the tool's arguments and its summary the description the
-# model reads (lib/tools/openapiTools.ts; ADK's OpenAPIToolset).
+# model reads (lib/tools/openapiTools.ts, the engine's own parser and
+# caller, by the rules ADK's OpenAPIToolset had).
 #
 # The specs are hand-written subsets of Open-Meteo's free, keyless
 # APIs (specs/): find a place, then forecast its weather. Swap in