release: v0.13.0 — AI disclosure is gateway-enforced (EU AI Act Article 50)#9
Merged
Conversation
…le 50) Removed the ai_disclosure parameter from create_mailbox, update_mailbox, and configure_mailbox. AI transparency marking — the signed ai_generated claim, the X-AI-Generated header, and the visible disclosure footer — is injected at the send gateway on every agent-originated email and can no longer be disabled. API calls setting ai_disclosure:false are rejected with 400.
|
Thanks for the interest. This repository does not accept pull requests. Please open an issue with the proposed change or problem report instead. |
Contributor
Author
|
Codex-gate round 2 flagged a missing |
…cked the release flow (main requires PRs)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Synced from the private repo (GHST-450, private PR #188 — deployed and live-verified in production).
ai_disclosureparameter fromcreate_mailbox,update_mailbox,configure_mailbox— AI transparency marking (signedai_generatedclaim,X-AI-Generatedheader, visible disclosure footer) is enforced at the send gateway on every agent-originated email and cannot be disabled. API disable attempts return 400.server.json+package.json→ 0.13.0 (@multimail/mcp-server@0.13.0already published to the registry).Pseudonymity gates: content scan PASS (14 files), commit-identity PASS. Merge method: rebase only (GHST-508 invariant).
Consumer/API trace for removed tool inputs (codex gate, Sharp 1)
This sync carries TWO schema removals, both propagating already-reviewed, already-deployed private changes — the remote MCP worker (mcp.multimail.dev) has served these schemas in production since their respective deploys:
ai_disclosure(create_mailbox / update_mailbox / configure_mailbox) — GHST-450, private PR #188 (merged24d2ad77, deployed + live-verified 2026-06-11). The API now rejectsai_disclosure: falsewith 400 on all three write paths (create/PATCH/configure) and clamps writes at the data layer; marking is enforced at the send gateway. A client passing the removed param against the live API gets an explicit 400 (false) or a no-op (true) — never silent divergence.bcc(edit_scheduled_email) — GHST-578, private PR #187 (merged51e476b, deployed + live-verified 2026-06-10). Recipient edits on approved scheduled emails are blocked server-side (delivery uses D1-current recipients); the tool schema was aligned to the live API contract. The 2026-06-10 v0.12.0 public sync was cut from a pre-#187 tree, so this propagates now.SDK repos that wrap these tools are tracked separately (GHST-504).