admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: close send message production gate behavior

Browse Source
This commit is contained in:
zhaoyilun
2026-07-10 21:01:04 +08:00
parent 41b4b5b7d2
commit 6781c75f84
4 changed files with 74 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/go-mcp-runbook.md
View File

@@ -294,6 +294,8 @@ R6h centralizes the production-send gate. Default `execution_mode="production"`
`ISPHERE_SEND_PRODUCTION_ENABLED=1` is recognized by the gate policy, but it is not sufficient by itself: the evidence gate and connector gate must also pass before production can be allowed. In the default MCP server path, `production_send_enabled` remains `false`.
R6l closes the current send-message production path after R6k: because `strict_v2_pass=false`, production send remains blocked even if `ISPHERE_SEND_PRODUCTION_ENABLED=1` is set. In that state, the MCP response uses `gate_reason_code="send_evidence_missing"` and still reports all real side-effect flags as false.
## 10. Current tool surface and next-stage route
The current runbook verifies nine tools: