chore(deps): update @relaycast/sdk to 4.0 in @agent-relay/sdk + cli

[willwashburn]

What

Bumps @relaycast/sdk ^3.1.1 → ^4.0.0 in @agent-relay/sdk and @agent-relay/cli (relay's two consumers).

The real root cause (no override needed)

The naive bump broke one test because of a version skew: packages/evals pinned @agent-relay/harness-driver: "8.6.0" — an exact published version, while the workspace is 8.7.2. The repo convention is to pin siblings at the exact workspace version so npm symlinks the local package; 8.6.0 ≠ 8.7.2 made npm fetch the published 8.6.0 from the registry, dragging in @agent-relay/sdk@8.6.0 → @relaycast/sdk@3.1.1 and preventing a single @relaycast/sdk from hoisting. That left relay's own SDK on a nested 4.0.0 the MCP-startup test's mock couldn't intercept.

Fix: repin evals to 8.7.2 (matching every other workspace cross-dep) so it uses the local harness-driver — which pulls no @relaycast/sdk. @relaycast/sdk@4.0.0 then hoists cleanly. No override.

Safety

relay's SDK only uses RelayCast/RelayError/options from @relaycast/sdk — none touched by 4.0's breaking changes. build:core clean, full suite 924 passing.

🤖 Generated with Claude Code

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 362d3cd5-798a-4180-9a70-e00d287653fd

📥 Commits

Reviewing files that changed from the base of the PR and between 03967f3 and a010f73.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• CHANGELOG.md
• packages/cli/package.json
• packages/evals/package.json
• packages/sdk/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/evals/package.json

🚧 Files skipped from review as they are similar to previous changes (2)

• packages/sdk/package.json
• packages/cli/package.json

---

📝 Walkthrough

Walkthrough

Three package.json files receive dependency version bumps: @relaycast/sdk moves from ^3.1.1 to ^4.0.0 in both packages/sdk and packages/cli, and @agent-relay/harness-driver moves from 8.6.0 to 8.7.2 in packages/evals. CHANGELOG.md gains two lines documenting the @relaycast/sdk 4.0 dependency and its updated durable-delivery status model.

Changes

@relaycast/sdk 4.0 upgrade

Layer / File(s)	Summary
@relaycast/sdk 4.0 dependency updates and changelog packages/sdk/package.json, packages/cli/package.json, CHANGELOG.md	@relaycast/sdk bumped from ^3.1.1 to ^4.0.0 in both packages/sdk and packages/cli; changelog entry documents the upgrade and the new durable-delivery status values (queued|delivered|acked|failed|dead_lettered).

@agent-relay/harness-driver update

Layer / File(s)	Summary
Harness driver dependency update packages/evals/package.json	@agent-relay/harness-driver bumped from 8.6.0 to 8.7.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• khaliqgant

Poem

🐇 Hop, hop, bump those versions up!
From three-point-one to four we leap,
queued, acked, delivered — oh what a sweep,
The harness driver got a patch so neat,
A changelog line to make it complete! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides comprehensive context but deviates from the template structure significantly, lacking the required 'Summary', 'Test Plan', and 'Screenshots' sections.	Restructure the description to follow the repository template: add a concise 'Summary' section, include a 'Test Plan' section with testing checkboxes, and note any applicable screenshots.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating @relaycast/sdk to version 4.0 in the two packages that depend on it.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/relaycast-sdk-4.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

CHANGELOG.md (1)

23-23: ⚡ Quick win

Make the Unreleased changelog bullet concise and user-impact-first.

Line 23 currently mixes user-facing change with internal implementation detail (status-model and override mechanics). Keep this as one short impact statement.

Suggested edit

-- `@agent-relay/sdk` and `@agent-relay/cli` now build against `@relaycast/sdk` 4.0 (durable-delivery status model `queued|delivered|acked|failed|dead_lettered`); a workspace override pins the dependency to a single 4.0 line across the tree.
+- `@agent-relay/sdk` and `@agent-relay/cli` now use `@relaycast/sdk` 4.0.

As per coding guidelines, CHANGELOG.md should keep [Unreleased] entries concise, impact-first, and omit implementation details.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 23, Simplify the changelog entry on line 23 to be
concise and user-impact-first. Remove the internal implementation details about
the durable-delivery status model (queued|delivered|acked|failed|dead_lettered)
and workspace override mechanics, as these are not relevant to end users. Keep
only the core user-facing impact: that `@agent-relay/sdk` and `@agent-relay/cli` now
build against `@relaycast/sdk` 4.0.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Line 23: Simplify the changelog entry on line 23 to be concise and
user-impact-first. Remove the internal implementation details about the
durable-delivery status model (queued|delivered|acked|failed|dead_lettered) and
workspace override mechanics, as these are not relevant to end users. Keep only
the core user-facing impact: that `@agent-relay/sdk` and `@agent-relay/cli` now
build against `@relaycast/sdk` 4.0.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8bde296f-3329-416d-b7c2-9d084be4b7a2

📥 Commits

Reviewing files that changed from the base of the PR and between c369c44 and 03967f3.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• CHANGELOG.md
• package.json
• packages/cli/package.json
• packages/sdk/package.json

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 03967f3630

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Map Relaycast 4 delivery statuses before bumping

With @relaycast/sdk 4 the durable-delivery API now reports the queued|delivered|acked|failed|dead_lettered status model, but the SDK adapter still only recognizes the old accepted|delivered|deferred|failed values in packages/sdk/src/messaging/normalize.ts and defaults unknown statuses to queued. When an agent acks a delivery or reads a dead-lettered row, inbox.*/deliveries.* will therefore surface a terminal item as queued, which can make durable-delivery consumers retry or misreport already-final deliveries; please update the status normalization alongside this dependency bump.

Useful? React with 👍 / 👎.