mirror of
https://github.com/zap-proto/dev.git
synced 2026-10-30 15:05:18 +00:00
zeekay
f15816a8b2
Replace the fictional MCP-style tool-calling API (Zap.connect / call_tool / Gateway / ToolCall) and wrong package names with the verified zero-copy wire + capability RPC surface, every name checked against source. - go.mdx: github.com/zap-proto/[email protected]. Builder→Parse round-trip, zapgen codegen (NewPing/WrapPing/PingInput), the rpc call envelope (BuildRequest/ParseResponse + 3-value pipelining client), and the cap layer (Issue/Attenuate/Verifier.Verify). Compiled+ran a generated Calculator client/server end to end (prints 15). - python.mdx: PyPI zap-proto, import zap (not zap_protocol). Wire round-trip, zap.rpc (Server/Client/Method — ran end to end), zap.cap (issue/attenuate/ Verifier — ran issue+verify), and the [app] decorator app (ZAP + Client). - rust.mdx: zap-schema crate (zapc bin) + the zap-proto/rust workspace crates (zap/zapc/zap-rpc/zap-futures). Real zap-rpc Server trait + RpcSystem client + zap::cap (issue/Verifier). Drops nonexistent zap-proto/zap-codegen crates, spec-rs, zap_protocol module. - cpp.mdx: separates the cpp-core schema front-end + zero-copy zap:: runtime (MallocMessageBuilder / messageToFlatArray / TwoPartyClient) from the cpp high-level binding; drops the fictional zap::connect/callTool client. - quick-start.mdx: real install/codegen (zapgen, cargo install zap-schema, @zap-proto/zapc — not zap-codegen / @zap-proto/codegen / spec/cmd/zap) and real generated-RPC server/client per language.