[waleedlatif1]

Summary

Validated Mailchimp against the official Marketing API spec.

• Archive Member did nothing: it sent DELETE .../actions/delete-permanent, which only accepts POST. It now archives with DELETE /lists/{id}/members/{hash}, the documented archive
• New Permanently Delete Member operation: POST .../actions/delete-permanent, the documented erasure, kept out of the first dropdown slot
• Member addressing: emails are sent as the documented subscriber_hash (MD5 of the lowercase email), which addresses the same member. Every path id goes through safeUrlPathSegment
• Unarchive: now sends the required status_if_new
• Member tags: tags get the required status, and comma-separated names are accepted. Input with no tag names now errors instead of sending a silent no-op
• Batch: operation bodies are sent as the JSON strings the spec requires. Unparseable operations now error instead of sending an empty batch
• Docs: the member removal note is updated

Type of Change

• Bug fix

Testing

• New mailchimp.test.ts (regression cases fail on the pre-fix tools)
• blocks tests, check-block-registry, check:tool-metadata, check:docs, check:docs-manifest, biome
• Independent audit against the spec and saved-workflow compatibility

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 14, 2026 2:17am UTC

[greptile-apps]

Confidence Score: 5/5

[Critical impact] The PR appears safe to merge; no blocking issues were found.

Summary

The PR fixes Mailchimp member archiving, adds a separate permanent-delete action, and updates member paths, tags, batch requests, and docs.

• Mailchimp offers separate archive and permanent-delete actions.
• Mailchimp member requests use the correct hash and safe path IDs.
• Mailchimp tag, batch, and restore requests use the expected fields.

_{Reviews (3) · Last reviewed commit: "fix(mailchimp): reject tag statuses othe..." · Reviewed by Greptile}

[cubic-dev-ai]

All reported issues were addressed across 74 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 74 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 74 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}