PR Review Summary

(0) Total Issues | Risk: Low

This PR is a mechanical snapshot update capturing schema changes already merged to main. The OpenAPI snapshot reflects the following changes:

Changes Observed

1. Field removals from request schemas: agentName and projectName removed from WorkAppSlackAgentConfigRequestSchema (these are response-only fields that were incorrectly included in request schemas previously)

2. Added validation constraints: maxLength: 256 added to agentId and projectId string fields (derives from DB schema constraints)

3. New 400 error responses: Added "Agent not found" error response to:

   • PUT /{teamId}/settings (update workspace settings)
   • PUT /{teamId}/channels/{channelId}/settings (set channel default agent)

4. Simplified error schemas: Removed redundant { success: boolean } schema from 500 error responses — the body shouldn't be relied upon for error responses anyway

Verification

• Changes are consistent with the source schemas in packages/agents-core/src/validation/schemas.ts (lines 3070-3084)
• Route implementations in packages/agents-work-apps/src/slack/routes/workspaces.ts confirm the 400 responses are returned when agent lookup fails (lines 348-355, 869-876)
• The changeset correctly targets @inkeep/agents-api with a patch bump

Note

The PR description states "update snapshot" but doesn't specify what source changes prompted the snapshot regeneration. For traceability, consider adding a brief note about the originating PR or changes.

Summary: Clean snapshot update reflecting prior schema refinements. No issues found — the changes correctly capture validation constraints and error response improvements that were already merged to the source code.

Snapshot is consistent with the current source code — all 12 snapshot tests pass. The OpenAPI diff correctly reflects the upstream schema changes: maxLength: 256 on agentId/projectId, removal of agentName/projectName from request schemas, new 400 responses, and simplified 500 response bodies.

  ^{｜ View workflow run ｜ pullfrog.com ｜ 𝕏}

PR Review Summary

(0) Total Issues | Risk: Low

This is a delta re-review scoped to changes since the last automated review. The delta consists of a merge commit bringing PR #2487's changes into this snapshot update branch.

Delta Changes Reviewed

The merge introduced the "pass cron timezone to agent in scheduled trigger execution" feature:

Analysis

1. Implementation is clean: The buildScheduledTriggerHeaders() helper correctly handles null/undefined timezone by falling back to 'UTC'.

2. Consistent usage: All 3 call sites in the delta use the same pattern (buildScheduledTriggerHeaders(trigger.cronTimezone) or buildScheduledTriggerHeaders(cronTimezone)).

3. Headers flow correctly: The forwardedHeaders are spread into MCP server headers (line 300 of executionHandler.ts) and stored in message metadata (line 310), enabling downstream consumers to access the scheduled trigger's timezone context.

4. No breaking changes: This is additive — existing triggers without cronTimezone will default to 'UTC'.

Note

This delta code was already reviewed and merged to main via PR #2487. The current PR's synchronize event reflects that merge into the snapshot update branch.

Summary: Clean delta — the cron timezone feature is correctly plumbed through the scheduled trigger execution chain. No issues found. Ship it! 🚀