embed-coremind-python

name	embed-coremind-python
description	Drive the same Node runtime and explicit Loop over stdio JSON-RPC from Python, and register Python callables as agent tools. Use for Python SDK, protocol parity, tool bridge, or recovery work.

Python SDK and Tool Bridge

1. Read the module contract and the language-matched guide only when implementation details are needed.
2. Identify the business owner, accepted inputs and outputs, failure conditions, permission mode, and quality profile.
3. Follow the SOP in order. Do not invent unresolved business rules or broaden the requested architecture.
4. Add or update a failing test before implementation, then make the smallest change that passes it.
5. Require a truthful effect declaration for every Python callable and verify protocol parity for all six terminal states and approval events.
6. Inject initialization or registration failure and verify the partially started worker is closed before the exception escapes.
7. Inspect RunOutcome, Trace, budgets, approvals, and checkpoints. Treat a fluent answer without evidence as unverified.
8. Compare explicit Loop state order and pause-resume with TypeScript; never replay completed steps or committed effects.
9. Verify every nested snapshot contract against TypeScript, including operation, outcome, metrics, trace, checkpoints, artifacts, and extension receipts; reject any drift with invalid_run_snapshot.
10. Confirm packaged Python uses the bundled Node Worker and never introduces a separate Python Runtime or Loop.
11. Run the tests listed in module.yaml and npm run check:modules.
12. Stop on a security failure or non-reversible action that lacks explicit user authorization. Never push, tag, or publish implicitly.

中文执行原则：先确认业务规则，再按 SOP 实现；失败不得伪装成成功；full 只改变审批强度，不得关闭显式 deny、审计、checkpoint、Effect Receipt 和恢复。路径感知文件工具与 shell 的平台边界必须分别验证。