[Proxicon]

Problem

The beta.10 owner campaign reproduced inconsistent MCP request-size behavior, could not delete an owned inbound email rule through the supported API/MCP lifecycle, and lacked a current-release executable evidence gate. Its historical NOT_READY receipt remains unchanged.

Changes

• Enforce the same bounded decoded JSON-body limit in the HTTP MCP host and public Web/YARP gateway. Preserve finite framing/concurrency limits, duplicate validation, and deliberate structured 413 responses.
• Add administrator-selected inbound-rule deletion and confirmed helpdesk_email_settings.delete_rule, preserving processing history and existing authority.
• Export v25: 37 tools / 390 operations, with all 389 prior contracts unchanged and one explicit addition. Retain exact historical catalog/delta bytes.
• Add a beta.11 receipt gate and laptop guide, fresh fixture selectors, complete transport probe, prerequisite checks, exact mail/approval effect accounting, and unchanged 103-domain/86-historical/cleanup/soak requirements.
• Set the sole product version to 0.1.2-beta.11 and document the companion NetRatel terminal-history repair in Preserve terminal run history when deleting ordinary job definitions netratel#410.

Validation

Release solution build succeeded with zero errors. Focused local coverage passed 105 unique cases: 100 initial passes plus five proxied-socket cases rerun successfully after correcting their synthetic ApiBaseUrl fixture. All nine new real-socket transport cases passed. The owner inbound-rule SQLite case passed; PostgreSQL execution belongs to the normal hosted provider gate because this executor has no Docker.

Campaign tooling passed 41 Python regressions and 19 unchanged historical gate tests. Native export confirmed all 389 existing contracts retained. Documentation, public disclosure, Slopwatch and whitespace checks passed. The final PR and exact-main CI, hosted publication, public distribution verification and laptop deployed acceptance remain separate gates.

Fixes #266.
Fixes #267.
Delivery: #268. Full deployed acceptance remains #219.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-10-26T11:27:36.542134Z	188008f	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.