[SaladDay]

MiniMax Code can now join Agent Core through the existing harness contract for environment:none text execution. The native ACP adapter supplies active-input receipts, ordered output, cancellation settlement and exact-history continuation; a qualified profile and version-bound operator opt-in connect it without Core handler, storage or scheduler branches. Product installation and execution qualification use native 0.4.12; permissions are configured before launch through native configuration.

Add a practical harness-onboarding guide, linked from the contributor rules, plus MiniMax Code deployment and acceptance instructions. A matching child document is published under the Feishu architecture document.

Validation:

• Fixed OpenAI Python SDK and raw HTTP against our public API, real daemon/gateway/Worker/PostgreSQL and native MiniMax Code 0.4.12: Kimi K3 and MiniMax M2.7 passed execution, same-Turn input receipt, cold daemon restart/continuation, slash text, tenant rejection and cancel/continue.
• Native missing/foreign history rejection; credential scan; product 0.4.12 new/resume, model/instruction refresh, Skill and MCP regression.
• Focused and race checks, make openapi (no generated diff), make check.
• Fresh independent GPT-6 Astra high blind review: no substantiated in-scope findings.

Scope: text only. Hosted workspace, Files/Artifacts, public functions/MCP and Subagents remain unqualified. Core runs in-process in the acceptance fixture, so this is not standalone deployment certification or complete public protocol compatibility. No database queries changed; sqlc regeneration is not applicable. The observed native permission-mode mutation issue is avoided through supported startup configuration. Hosted isolation gaps are recorded in Feishu for separate work.

Docker/E2B product image version pins were updated; full image builds are not part of this text-profile qualification. Native package execution and required repository build checks are covered.