bridge

mirror of https://github.com/luxfi/bridge.git synced 2026-09-24 00:26:46 +00:00

Files

T

zeekay 3eac448d43 docs(LLM): ZAP serialization — canonical at ~/work/zap, @zap-proto npm, no capnp-es

User directive (2026-05-24): 'no capnp-es must be zap-es ... keep all
zap brand neutral in ~/work/zap, zap-proto github etc ... should be
npm @zap-proto matching'.

Audit confirmed:
  - The bridge has ZERO capnp-es references (every wire call is JSON
    over HTTP via fetch). Bridge is clean.
  - Canonical ZAP repo is ~/work/zap (not ~/work/lux/zap or
    ~/work/hanzo/zap — those are forks slated for consolidation upstream).
  - TS implementation lives at ~/work/zap/zap-js (package name
    @zap-proto/zap). It already exists as pure TS — no source file
    imports capnp-es, despite the dep being listed in package.json
    (stale entry, removal queued for next ZAP TS publish).
  - WASM binding: @zap-proto/wasm at ~/work/zap/zap-wasm.
  - npm @zap-proto/* scope is the canonical brand-neutral home.

This commit just adds a doc section so the next dev (or me, next
session) doesn't accidentally  ERR_PNPM_ADDING_TO_ROOT  Running this command will add the dependency to the workspace root, which might not be what you want - if you really meant it, make it explicit by running this command again with the -w flag (or --workspace-root). If you don't want to see this warning anymore, you may set the ignore-workspace-root-check setting to true. when a future bridge
surface needs binary RPC. The rule is:
  use @zap-proto/zap (pure TS, no third-party Cap'n Proto dep)
  do NOT publish @luxfi/zap-* or @hanzoai/zap-* (forks the wire format)
  source-of-truth for wire format: ~/work/zap/README.md +
                                   ~/work/zap/zap-js/src/protocol.ts

2026-05-24 01:22:25 -07:00