From b75f406ba0d6d6f3c55ca2f169ec1321ef18d9eb Mon Sep 17 00:00:00 2001 From: Will Washburn Date: Mon, 18 May 2026 14:12:37 -0400 Subject: [PATCH] docs: update changelog for recent merges --- AGENTS.md | 8 +++++++ CHANGELOG.md | 65 ++++++++++++++++++++++++++++++++++------------------ 2 files changed, 51 insertions(+), 22 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index c0d9debbf..7b1ff02d2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -26,6 +26,14 @@ git push origin main # NO! This ensures the user maintains control over what goes into the main branch. +## Changelog Style + +Changelog entries should be concise and impact-first. Prefer one short bullet +per user-visible change: name the command, API, or schema touched and the +practical effect. Drop issue/PR links, internal review notes, implementation +backstory, and "foundation for..." phrasing unless that text clearly explains +the shipped impact. + ## .trajectories Must Be Tracked **CRITICAL: Never add `.trajectories/` to `.gitignore`.** diff --git a/CHANGELOG.md b/CHANGELOG.md index 9c452c97b..073551ad3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,40 +9,61 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Breaking Changes -- **Task injection failures now return errors**: When spawning an agent with a task, if delivery fails after 3 retry attempts, spawn returns `success: false` and kills the agent. Previously, spawn would return `success: true` even if task injection silently failed, leaving zombie agents. -- **Messaging sender default changed**: `agent-relay send` now defaults to the orchestrator identity (`$AGENT_RELAY_ORCHESTRATOR_NAME` or `orchestrator`) so `agent-relay replies ` can correlate direct-message conversations. +- `relay.spawn({ task })` now returns `success: false` and terminates the agent when task delivery fails after retries. +- `agent-relay send` now uses the orchestrator identity by default so `agent-relay replies ` can correlate worker DMs. ### Migration Guidance -- Callers of `relay.spawn()` with a `task` parameter should handle `success: false` results (though automatic retries make failures rare). -- Spawning without a task is unaffected and always succeeds. -- See the updated [Worker Orchestration guide](/docs/guides/worker-orchestration) for retry patterns. +- Pass `--from` to `agent-relay send` when a script requires a specific sender identity. +- Handle `success: false` from `relay.spawn()` calls that pass `task`; spawns without a task are unchanged. +- Set `POSTHOG_PROJECT_KEY` in GitHub Actions repository variables before publishing telemetry-enabled artifacts. ### Added -- **`@agent-relay/cloud` provider connect SDK** (6.1.0): Exposes `connectProvider()`, `runInteractiveSession()`, and SSH runtime helpers (`loadSSH2`, `createAskpassScript`, `buildSystemSshArgs`) so other CLIs can drive the same Daytona-brokered provider auth flow that powers `agent-relay cloud connect`. `ssh2` is now an `optionalDependency` of the cloud package. -- **`@agent-relay/sdk/workflows` script runner** (6.1.0): Exposes `runScriptWorkflow()`, `parseTsxStderr`, `formatWorkflowParseError`, `findLocalSdkWorkspace`, `ensureLocalSdkWorkflowRuntime`, plus `RunScriptWorkflowOptions` / `ParsedWorkflowError` types. The body of `agent-relay run