Every release, cut in the open.

Minor Changes

• —

  1df23b1: SupervisorAgentConfig accepts resumeHandler and verificationGate.

  The supervisor's existing tool-review pipeline (drainQuery's runToolReview phase) was reachable only by callers that constructed drainQuery arguments by hand — SupervisorAgent.run ignored them entirely and always fell back to autoApproveHandler. Hosts that wanted "Ask before acting" semantics had no way to plug in.

  SupervisorAgent.run now forwards both fields verbatim to drainQuery when the caller supplies them. Behaviour is unchanged for callers that omit them — the SDK still defaults to auto-approve.

  Migration:

  new SupervisorAgent({...}).run(input, {
    ...config,
    // surface tool_review_requested events to the user; resolve when
    // they approve / modify / reject.
    resumeHandler: async ({ runId, toolCalls, ... }) => {
      return await waitForUserDecision(runId, toolCalls)
    },
    // optionally pre-classify tools so trivial reads bypass review.
    verificationGate: { enabled: true, rules: [...] },
  })
  

Patch Changes

• —

  ffe516c: Probe layer (typed observation + narrow veto) over AgentBus + RunEvent stream — ses_007 phases 0–3.

  Public surface additions:

  • —Typed probe observation. probe.on(kind | kind[], handler, opts?) registers a typed handler scoped to one or more event kinds. probe.onAny(handler, opts?) is the catch-all tier preserving legacy AgentBus.on semantics. Options: { where, priority, name, override }. Events are frozen at the registry boundary; throws are isolated per probe.
  • —Narrow veto on tool execution. probe.veto('tool_executing', handler, opts?) registers a veto handler. Handler returns 'allow' | 'deny' | { action: 'deny', reason }. VetoableEventKind = 'tool_executing' in v1 (additive minor adds more kinds later). First-deny wins by ascending priority; subsequent veto handlers still fire for audit. Tool executor short-circuits before tools.execute(...) on deny: returns a synthetic tool failure carrying ProbeVetoError.message so the LLM sees a normal tool-call failure with the probe name + reason.
  • —5 new bus event variants. provider_call_start, provider_call_completed, provider_call_failed, vault_lookup, sandbox_decision. Joined to the existing AgentBusEvent discriminated union. Snake_case real discriminants — no rename pass on existing events.
  • —Opt-in instrumentation wrappers. wrapProviderWithProbes(provider, opts?) returns an LLMProvider that emits provider_call_* around every chat/chatStream call (correlated by a pcall_${string} callId, with optional usage telemetry). wrapVaultWithProbes(vault, opts?) emits vault_lookup on every retrieve(); the secret value is never included in the event payload (covered by a "no leakage" test).
  • —First-time public exposure of bus event types. AgentBusEvent, AgentBusEventListener, CircuitBreakerSnapshot, FileLock, etc. were already reachable via AgentBus.on(listener) at runtime but couldn't be statically typed by consumers. Now in public-types.ts. Pre-existing duplicate LockId declaration in types/bus/ was deduplicated to a re-export from types/ids/ in passing.
  • —Replay-aware probe context. ProbeContext.isReplay: boolean flag wired through buildProbeContext({ runId?, isReplay? }) so probes that bill or call external services can opt out on replayed runs (ctx.isReplay === true). Replay-execution wiring lands in a future session; the accessor is ready.

  Integration:

  • —AgentBus.emit dispatches through ProbeRegistry first (typed-priority probes → legacy bus.on listeners → onAny catch-all). Existing bus.on(listener) consumers see every event in unchanged relative order.
  • —EventTranslator.emitEvent dispatches every RunEvent through the same registry before the existing pendingEvents push + persist flow.
  • —ToolExecutor.executeSingle calls probes.queryVeto({type: 'tool_executing', ...}) immediately after the existing tool_executing emit, before tools.execute(...).

  Not yet wired (follow-up commits):

  • —Per-run probes via createRun({ probes: [...] }) — the registry has the foundation; createRun plumbing lands in a follow-up.
  • —wrapProviderWithProbes / wrapVaultWithProbes are opt-in helpers; the SDK's own ProviderRegistry does not auto-wrap registered providers yet.
  • —sandbox_decision ships as a type only; emit site lands when a real sandbox provider exists (current LocalSandboxProvider is a stub).

  Public surface delta: 380 → 392 runtime keys (verified against the regenerated baseline). Net new symbols added by this changeset:

  • —probe, ProbeRegistry, createProbeRegistry, buildProbeContext, ProbeNameCollisionError, ProbeVetoError
  • —wrapProviderWithProbes, wrapVaultWithProbes

  Non-runtime (types-only) additions: ProbeEventKind, ProbeEventOf<K>, ProbeContext, ProbeHandler<K>, ProbeOptions<K>, Unsubscribe, VetoableEventKind, VetoDecision, VetoHandler<K>, VetoOutcome, DoctorStatus, DoctorCategory, DoctorCheck, DoctorCheckContext, DoctorCheckResult, DoctorCheckRecord, DoctorReport, ProviderCallId, ProviderCallUsage, SandboxDecisionAction, plus first-time exposure of all AgentBusEvent shape types.

  Doctor types ship in this release; the runtime registry + CLI command land in a subsequent ses_007 patch.

Patch Changes

• —

  ddd0aad: Test-side hardening from ses_006 pre-freeze fix.

  • —New test: runtime/query/iteration/phases/advisory.test.ts — pins the advisory-phase mutation boundary where fired advisories inject user messages via runMgr.pushMessage(createUserMessage(...)). 13 assertions covering early-return paths, happy-path exactly-once calls, envelope format, warnings + decisions rendering, and trigger-selection semantics. Before this test a regression removing the pushMessage call at advisory.ts:154 would pass typecheck, lint, the coverage gate, and every existing src/advisory/* test. It now fails deterministically.
  • —LogLevel gains 'silent' — purely additive; the value short-circuits every log() call. Used by the SDK's vitest setup to suppress unmocked getRootLogger() stderr writes so GitHub Actions stops annotating [ERROR]-level log lines as workflow errors. Consumer impact: zero unless you pass 'silent' to configureLogger() yourself.
  • —No runtime behavior change. No public surface additions beyond the one LogLevel union member.

Patch Changes

• —

  14ff062: Public-surface barrel split (ses_011-sdk-public-surface).

  Note on bump level. Originally classified as minor when ses_011 froze on 2026-04-21. Downgraded to patch post-freeze (2026-04-21) as part of a repo-wide release-cadence policy decision: the pre-1.0 SDK reserves minor/major for feature-delta releases, and internal refactors that keep the public-surface baseline intact ride patch. This changeset explicitly preserved all 380 pre-existing public names (verified by .github/scripts/verify-public-surface.mjs), so patch is semver-accurate at the name-set level. See .changeset/sdk-replay-primitive.md for the same-day rationale block.

  packages/sdk/src/index.ts splits from 357 lines of mixed re-exports into three focused bucket files, consumed through a thin 10-line root barrel:

  • —public-types.ts — every type a consumer type-checks against (branded IDs, wire shapes, domain entities, store contracts, event unions, config types).
  • —public-runtime.ts — every runtime value (classes, functions, constants, zod schemas, error classes, ID generators).
  • —public-tools.ts — agent-tool surface (defineTool primitive, built-in tools, domain builders, connector tool bridge, createRAGTool).

  No consumer-visible change. All 380 previously-exported names continue to be exported; none removed, none added. Verified by a baseline snapshot (.github/scripts/public-surface-baseline.json — captured at the tip of ses_010) plus a CI smoke test (.github/scripts/verify-public-surface.mjs) that loads @namzu/sdk at runtime and compares Object.keys() against the baseline.

  Additional cleanup:

  • —The ProjectId / RunId / MessageId / SessionId double-channel (reachable through both contracts/ and types/ids/) is closed. IDs come from types/ids/ uniformly; contracts/ids.ts is deleted; contracts/api.ts imports IDs from ../types/ids/ directly.
  • —The RunStatus carve-out is folded. Since ses_010 renamed the wire-side alias to WireRunStatus, the domain RunStatus can flow through types/run/index.ts with a plain export * — no explicit carve-out needed.
• —

  2eccadd: Replay primitive v1 — fork an existing run from any stored checkpoint with optional mutation at the fork point (ses_005-deterministic-replay).

  Note on bump level. This release adds new public exports (prepareReplayState, listCheckpoints, projectEmergencyToCheckpoint, MutationNotApplicableError, the Mutation / CheckpointListEntry / ReplayAttribution types, Run.replayOf?). In strict semver these would be a minor bump. Classified as patch here because the SDK is pre-1.0 and the project reserves minor/major for larger feature deltas — 0.5.0 should land with a more complete replay surface (5b end-to-end wrapper, reproduce mode, or similar) rather than just this state-preparation half. Decision logged 2026-04-21 post-freeze of ses_005.

  New public runtime values:

  • —prepareReplayState({ baseDir, runId, fromCheckpoint, mutate?, emergencyDir? }) — pure-read helper that resolves fromCheckpoint (CheckpointId | 'latest' | 'emergency'), applies mutations, and returns { messages, sourceCheckpoint, attribution } ready to thread into a query(...) call.
  • —listCheckpoints({ baseDir, runId }) — lists a run's checkpoints as lightweight CheckpointListEntry projections.
  • —projectEmergencyToCheckpoint(dump) — project an EmergencySaveData snapshot to an IterationCheckpoint shape with deterministic cp_emergency_* id.
  • —MutationNotApplicableError — thrown by prepareReplayState when a mutation targets a tool call that is not pending at the fork point; carries availableToolCallIds for recovery.

  New public types:

  • —Mutation — discriminated union; single injectToolResponse variant in v1.
  • —CheckpointListEntry — listing projection distinct from the pre-existing HITL CheckpointSummary.
  • —ReplayAttribution — { sourceRunId, fromCheckpointId, mutations, replayedAt } record.
  • —Run.replayOf?: ReplayAttribution — optional attribution field; undefined on original runs.

  Scope and non-scope — v1 ships forked execution from a captured checkpoint, not byte-for-byte reproduction. Past the fork point, provider calls and tool calls execute live. Deterministic reproduce mode is deferred to a follow-up session.

  A single-call replay({ runId, opts }) wrapper is intentionally not shipped in v1. Composing listCheckpoints → prepareReplayState → caller-owned query() is the v1 flow; the wrapper requires a ReplayEnvironment design (provider, tools, resume handler, session scope) that lands in a follow-up session.

  See docs/sdk/runtime/replay.md for the full primitive docs, determinism envelope, and non-scope.

• —

  9efae03: Type layering rationalised (ses_010-sdk-type-layering).

  Note on bump level. Originally classified as minor when ses_010 froze on 2026-04-21. Downgraded to patch post-freeze (2026-04-21) as part of a repo-wide release-cadence policy decision: the pre-1.0 SDK reserves minor/major for feature-delta releases, and internal refactors that keep the public-surface baseline intact ride patch. This changeset introduced no consumer-visible new names and renamed AgentRun → Run with a @deprecated alias, which the policy treats as a patch-level churn for 0.x. See .changeset/sdk-replay-primitive.md for the same-day rationale block.

  All pure shapes — entities, store contracts, wire types, events — now live under packages/sdk/src/types/. Feature folders (session/, manager/, store/, agent/, provider/) contain runtime code only.

  Public surface changes:

  • —AgentRun renamed to Run. AgentRun and AgentSession are kept as @deprecated type aliases for the 0.4.x compatibility window — existing code importing either continues to compile. New code should use Run.
  • —Wire-side Run interface renamed to WireRun, mirroring the existing WireRunStatus precedent. The root @namzu/sdk barrel now exports domain Run and wire WireRun with no collision.
  • —Internal folder packages/sdk/src/session/hierarchy/ removed. Only the @namzu/sdk root barrel (.) is a supported import surface; deep-imports were never supported and the old path no longer exists.

  No runtime behaviour change. Every entity previously exported (Project, Thread, Session, SubSession, ActorRef, Lineage, Tenant) continues to be exported from @namzu/sdk.

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Minor Changes

• —

  40eb841: Unblock BYO-provider use of AgentManager.spawn and capture the full 0.2.x → 0.3.0 window.

  Bug Fixes

  • —AgentManager.sendMessage no longer requires both configBuilder AND factoryOptions together. The configBuilder now runs whenever it is registered; factoryOptions defaults to {} when absent. This closes the silent crash path that consumers following README's "getting started" install hit with Bedrock (ERESOLVE → bare-config → ReactiveAgent null access).
  • —AgentFactoryOptions.apiKey is now optional. BYO-provider flows (Bedrock IAM, custom ProviderRegistry.create(...)) no longer need to fabricate a meaningless empty apiKey just to satisfy the type.

  Breaking Changes carried over from the 0.2.x → 0.3.0 window

  • —feat(sdk)!: propagate threadId through runtime + wire archive gate — childConfig now receives sessionId/threadId/projectId/tenantId automatically from the parent context (stamped by AgentManager after configBuilder returns). configBuilder implementations that previously emitted these fields manually are unaffected; implementations relying on the old 0.2.0 three-ID triple (sessionId/projectId/tenantId without threadId) will now see threadId populated on the child config.

  Other

  • —knip integrated as the dead-code detector (dev-only, no runtime surface change).
  • —ThreadManager.archive/delete primitives added to SessionStore; wire-side thread_id renamed during the Thread→Project wire refactor (internal rename).

  See commits since sdk-v0.2.0 for the full list; this changeset captures the visible-to-consumer summary.

All notable changes to Namzu are documented here.

Features

• —sdk: close Task 10 known deltas + expose session hierarchy (Phase 9) [BREAKING]
• —sdk: add retention + archival primitives with deleteSession close-out (Phase 8)
• —sdk: add migration utilities for 0.2.0 upgrade path (Phase 7)
• —sdk: refactor AgentManager to spawn SubSession triple with kernel summarization (Phase 6) [BREAKING]
• —sdk: add SessionSummaryMaterializer kernel terminalization primitive (Phase 5)
• —sdk: add handoff state machine with atomic broadcast rollback (Phase 4)
• —sdk: add SessionStore + PathBuilder + git-worktree workspace driver (Phase 3) [BREAKING]
• —sdk: add RunEvent schemaVersion + sub-session lifecycle events (Phase 2) [BREAKING]
• —sdk: introduce session hierarchy type foundation (Phase 1) [BREAKING]

Testing

• —sdk: add Task 10 integration test coverage matrix (Phase 10)

Documentation

• —changelog: update for sdk-v0.1.7
• —readme: rewrite root + fix sdk stale ProviderFactory refs

Documentation

• —changelog: add 0.1.6 (sdk) and 0.1.0 (computer-use) entries; fix cliff tag prefix + workflow race
• —changelog: update for sdk-v0.1.6-rc.1

Features

• —bedrock: extract BedrockProvider to @namzu/bedrock package (Phase I.3 pilot)
• —openrouter: extract OpenRouterProvider to @namzu/openrouter package (Phase I.4)

Refactor

• —sdk: address Codex review — scope providers/ subfolder, hide registry reset
• —sdk: replace ProviderFactory with ProviderRegistry for per-vendor extraction [BREAKING]

Stable release of @namzu/sdk 0.1.6 (promoted from 0.1.6-rc.1).

[sdk-v0.1.6-rc.1] — 2026-04-15

Documentation

• —changelog: update for v0.1.5

Features

• —sdk: add ComputerUseHost interface and computer_use tool

Miscellaneous

• —initialize namzu monorepo from sdk; add @namzu/computer-use capability package

[0.1.5] — 2026-04-15

Bug Fixes

• —emergency: uuid tmp suffix, outer try/catch, and explicit exit
• —store: resolve withLock race, delete deadlock, and atomic edge updates

Documentation

• —changelog: update for v0.1.5-rc.2

Refactor

• —barrels: route root barrel through sub-barrels (Path B)
• —connector: brand ConnectorId/TenantId on public interfaces [BREAKING]

Testing

• —store: add concurrency regression tests for DiskTaskStore

[0.1.5-rc.2] — 2026-04-14

Bug Fixes

• —plugin: wire MCP servers and fail fast on unsupported contributions
• —plugin: consume hook results and wire tool hooks in runtime
• —release: normalize pre-release counter to strip non-digit suffix

Documentation

• —changelog: update for v0.1.5-rc.1-fix
• —contracts: formalize wire/domain duality + refresh README
• —readme: rewrite code examples to match current SDK API

Refactor

• —plugin: remove duplicate PluginConfigSchema in types/
• —registry: migrate Agent/Connector/Tool registries to ManagedRegistry
• —run: remove legacy Session* aliases for run-centric classes

[0.1.5-rc.1] — 2026-04-12

Documentation

• —changelog: update for v0.1.4

Refactor

• —architectural cleanup and infrastructure improvements

[0.1.4] — 2026-04-11

Documentation

• —changelog: update for v0.1.4-rc.3

Features

• —sandbox isolation, new tools (edit/grep/ls), session-to-run migration

[0.1.4-rc.3] — 2026-04-10

Miscellaneous

• —release: derive version from git tag, no manual bump needed

[0.1.4-rc.2] — 2026-04-10

Bug Fixes

• —ci: remove duplicate --strip flag in git-cliff command
• —plugin: rename session hooks to run_start/run_end
• —release: use tag name as release title instead of prefixed name

Features

• —P3 + plugin architecture — emergency save, memory index, plugin system
• —P2 — AgentBus, prompt cache split, verification gate
• —integrate compaction loop and advisory phase into iteration pipeline

Miscellaneous

• —changelog: automate CHANGELOG.md via git-cliff in release workflow

[0.1.4-rc.1] — 2026-04-10

Bug Fixes

• —add description field to package.json, reorder README badges

Features

• —advisory: provider-agnostic advisory system with three-layer architecture
• —structured compaction, tool tiering, task router
• —output discipline, shell compression, pre-release workflow

Miscellaneous

• —remove BEFORE-RELEASE.md from repo

[0.1.3] — 2026-04-10

Bug Fixes

• —point entry fields to dist/ for bundler compatibility

Documentation

• —add npm, ci, license, typescript, node badges to README

[0.1.2] — 2026-04-10

Other

• —Namzu v0.1.1 — Wisdom, shared

Open-source AI agent framework by cogitave.

Let's build the agent layer together.

Refactor

• —constants centralization, strict lint, release automation

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/anthropic are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/anthropic v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/bedrock are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/bedrock v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Minor Changes

• —

  40eb841: Move @namzu/sdk from dependencies to peerDependencies.

  Previously, @namzu/computer-use@0.1.0 declared @namzu/sdk as a direct runtime dependency (workspace:^), which meant a consumer installing both packages would end up with two concurrent copies of @namzu/sdk in node_modules — the one they installed themselves and the one computer-use resolved. This produces symbol-identity bugs (two separate AgentManager classes, two separate RunEvent schemas, etc.) that surface as hard-to-diagnose "instanceof fails" at runtime.

  The correct shape, matching the 7 provider packages, is peer + dev:

  • —peerDependencies: @namzu/sdk: ">=0.1.6 <1.0.0" — consumer provides, resolved once.
  • —devDependencies: @namzu/sdk: workspace:^ — for local dev and type-checking.

  Consumer migration: if you previously relied on @namzu/computer-use pulling @namzu/sdk in transitively, install it explicitly:

  npm install @namzu/sdk @namzu/computer-use
  

  This is technically a breaking change (the transitive resolution no longer works), but pre-1.0 SDK context and the runtime-corruption risk of the old shape justify correcting it as a minor bump.

All notable changes to @namzu/computer-use are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/computer-use v0.1.0

Release of @namzu/computer-use v0.0.2-rc.1

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/http are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/http v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/lmstudio are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/lmstudio v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/ollama are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/ollama v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/openai are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/openai v0.1.0

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2

Patch Changes

• —

  40eb841: Widen @namzu/sdk peer range to >=0.1.6 <1.0.0.

  The previous peer range ^1 || ^0.1.6 resolved to >=0.1.6 <0.2.0 || >=1.0.0, which excluded the published @namzu/sdk@0.2.0 and caused npm install @namzu/sdk @namzu/<provider> to fail with ERESOLVE on a clean machine. The new range covers every pre-1.0 SDK minor from 0.1.6 onward; the 1.0 pledge will be the next explicit widening.

  This is the first release under the new Changesets-driven workflow and the wide-pre-1.0-peer convention. Consumers who followed the README's "getting started" install were previously blocked; after this release npm install @namzu/sdk@latest @namzu/<provider>@latest resolves cleanly.

All notable changes to @namzu/openrouter are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Release of @namzu/openrouter v0.1.0

Patch Changes

• —Updated dependencies [1df23b1]
  • —@namzu/sdk@0.6.0

Bug Fixes

• —emergency: uuid tmp suffix, outer try/catch, and explicit exit
• —store: resolve withLock race, delete deadlock, and atomic edge updates

Documentation

• —changelog: update for v0.1.5-rc.2

Refactor

• —barrels: route root barrel through sub-barrels (Path B)
• —connector: brand ConnectorId/TenantId on public interfaces [BREAKING]

Testing

• —store: add concurrency regression tests for DiskTaskStore

Bug Fixes

• —plugin: wire MCP servers and fail fast on unsupported contributions
• —plugin: consume hook results and wire tool hooks in runtime
• —release: normalize pre-release counter to strip non-digit suffix

Documentation

• —changelog: update for v0.1.5-rc.1-fix
• —contracts: formalize wire/domain duality + refresh README
• —readme: rewrite code examples to match current SDK API

Refactor

• —plugin: remove duplicate PluginConfigSchema in types/
• —registry: migrate Agent/Connector/Tool registries to ManagedRegistry
• —run: remove legacy Session* aliases for run-centric classes

Documentation

• —changelog: update for v0.1.4-rc.3

Features

• —sandbox isolation, new tools (edit/grep/ls), session-to-run migration

Miscellaneous

• —release: derive version from git tag, no manual bump needed

9d4c180 chore(release): 0.1.4-rc.1 3658715 feat(advisory): provider-agnostic advisory system with three-layer architecture 53404c6 feat: structured compaction, tool tiering, task router efd2936 fix: add description field to package.json, reorder README badges b8abff8 feat: output discipline, shell compression, pre-release workflow c081c46 chore: remove BEFORE-RELEASE.md from repo

f832ce0 fix: point entry fields to dist/ for bundler compatibility e06b3b4 docs: add npm, ci, license, typescript, node badges to README

Patch Changes

• —

  c9b180d: Coordinated patch bump across all publishable packages after the @namzu/telemetry@0.1.0 extraction landed. No functional changes — this is a compatibility and release-pipeline validation cut to (a) exercise the Trusted Publisher binding for @namzu/telemetry that was configured after the 0.1.0 bootstrap publish, and (b) give consumers a single aligned set of patch versions that all know about the new telemetry package.

  Resulting versions:

  • —@namzu/sdk → 0.4.1
  • —@namzu/telemetry → 0.1.1
  • —@namzu/computer-use → 0.2.1
  • —@namzu/anthropic, @namzu/bedrock, @namzu/http, @namzu/lmstudio, @namzu/ollama, @namzu/openai, @namzu/openrouter → 0.1.2