docs(contracts): promote antigen MCP contract to v1.3 - #3
Conversation
Align OpenHarness with hardened SCP vendor text: no MCP tls_verify, DEV_AUTO CLI-only, dual-gate consent; add missing 1.3 changelog bullet. Co-authored-by: Cursor <cursoragent@cursor.com>
Pin eol=lf so CONTRACT_HASH stays stable under Windows autocrlf. Co-authored-by: Cursor <cursoragent@cursor.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4242ce05fd
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| scp_registry_summary / scp_inspect (scp_mcp v1.0 + v1.1) → uses updated projection per load order | ||
| ``` | ||
|
|
||
| Core inspect load order documented in [scp_mcp_v1.1.md](scp_mcp_v1.1.md). |
There was a problem hiding this comment.
When this contract is rendered from OpenHarness, this relative link resolves to docs/contracts/scp_mcp_v1.1.md, but that file is not present in the repository (only docs/contracts/scp_mcp_v1.md exists). Consumers trying to verify the stated core inspect load order from the public contract will hit a broken link, so either add the v1.1 contract file here or point this note at an existing document.
Useful? React with 👍 / 👎.
1 participant
Summary
scp_antigen_mcp_v1.mdat hardened v1.3 (no MCPtls_verify, DEV_AUTO CLI-only, dual-gate consent).eol=lffor stable CONTRACT_HASH.docs/plans/.Companion: ManintheCrowds/SCP#26
Test plan
6c7bdcec8f82f12054abc87b71e85a331ce728aed875164da3692b486cc3d8fa(LF)Post-Deploy Monitoring & Validation
No additional operational monitoring required — documentation/contract text only; no runtime deploy.