Commit Graph
17 Commits
Author SHA1 Message Date
zeekay d89d3a16e5 docs(zap): call out X-Wing — IETF-standardized X25519+ML-KEM hybrid
X25519 + ML-KEM-768 is the IETF X-Wing construction
(draft-connolly-cfrg-xwing-kem). Document where Lux uses X-Wing
(zap-protocol Rust core, AI-agent ZAP) vs the RNS hybrid (Lux node
sessions with identity-bound handshake). Comparison table added so
new code picks the right one.
2026-05-06 10:23:33 -07:00
zeekay 8ad962dc42 docs(zap): comprehensive LLM.md — wire format, PQ scope, two-implementation reality 2026-05-06 10:21:13 -07:00
zeekay 99631b3b4e fix(zap): correctness — distinct MsgErrorFlag, response flag on success, drop debug stderr
Three real bugs in luxfi/api/zap:

1. Debug fmt.Fprintf(os.Stderr, ...) prints on every wire read/write/
   handler invocation. Visible in production logs as [ZAP-WIRE-READ],
   [ZAP-CLIENT-READ], [ZAP-SERVER-WRITE], [ZAP-HANDLER]. Stripped.

2. Server's success path sent the handler's returned msgType directly
   without OR'ing MsgResponseFlag. Echo-style handlers (return same
   msgType) produced responses that looked like fresh inbound requests
   to the client demultiplexer, which dropped them. Tests caught this
   as 'Expected response type 137, got 9'.

3. Client treated every response as an error because the protocol used
   a single MsgResponseFlag for both success and error paths. Added
   MsgErrorFlag (0x40) — error responses now carry MsgResponseFlag
   AND MsgErrorFlag; success responses carry only MsgResponseFlag.
   All msg types must stay < 0x40 (the existing range 1-52 is fine).
2026-05-06 10:19:43 -07:00
zeekay 06b7887c87 feat: GetNodeVersionReply.Consensus + ConsensusInfo (info api); drop dead agentic_network.go
agentic_capnp sub-package was never generated; build-tag dead code referencing it
broke 'go mod tidy' (could not resolve unused phantom import). No-fake policy.

deps: tls v1.0.3 (hkdf.New); go mod tidy
2026-05-05 16:57:04 -07:00
zeekay 55e851bacb deps: update go.mod/go.sum 2026-04-19 17:04:02 -07:00
zeekay f4791bbf26 chore: symlink AGENTS.md and CLAUDE.md to LLM.md
Canonical project context lives in LLM.md. Symlinks ensure
agentic coding tools (agent, Cursor, etc.) find context
automatically regardless of which filename they look for.
2026-04-01 14:08:02 -07:00
zeekay b009e78f4d chore: bump Go 1.26.0 → 1.26.1
Fixes 5 stdlib CVEs (html/template, os, net/url, crypto/x509 x2).
2026-03-12 01:07:37 -07:00
zeekay d24119bc75 feat: add typed State enum to ZAP VM protocol v1.0.4 2026-03-11 12:09:33 -07:00
zeekay c03b59c868 docs: add LLM.md project guide 2026-03-11 10:34:33 -07:00
zeekay f4325cd5d3 chore: update Go module dependencies 2026-03-03 14:41:48 -08:00
zeekay d5f3eb1b77 chore: add BSD-3-Clause LICENSE 2026-02-14 05:26:18 -08:00
zeekay f51e8ffb83 debug(zap): add wire-level debug output for Initialize diagnosis
Add temporary stderr debug prints to ReadMessage, readLoop, handleConn,
and ServerConn.Write to capture exact msgType bytes on the wire. This
will reveal why the client sees MsgResponseFlag set on Initialize
responses that the server sends as MsgInitialize (0x01).
v1.0.3
2026-02-10 22:07:02 -08:00
zeekay d38045dba5 feat(zap): add error response protocol and concurrent request handling
Add MsgResponseFlag for error responses over the wire, enable concurrent
request dispatch with per-goroutine panic recovery, and simplify State
type to use canonical vm.State. Update consensus dependency to v1.22.67.
v1.0.2
2026-02-10 18:54:45 -08:00
zeekay cc9ec49d75 feat: add ZAP-format agentic network schema
Convert agentic.capnp to proper whitespace-based ZAP syntax:
- Remove file IDs, ordinals (@N), braces, semicolons
- Use indentation-based structure
- Add AgenticNetwork service interface
- Supports ZMQ, Cap'n Proto, gRPC wire protocols
- Includes post-quantum cryptography primitives
2026-02-04 17:56:47 -08:00
zeekay 57d45de11a chore: sync dependencies and format code 2026-02-04 15:46:05 -08:00
zeekay dd2f2c716e Add ZAP wire protocol transport for VM communication
- Add zap/ package with zero-copy binary wire protocol
- Support for VM client/server communication over ZAP
- Wire format: [4-byte length][1-byte message type][payload]
- Includes sender, transport, and VM implementations
v1.0.1
2026-01-24 11:39:40 -08:00
zeekay b1db41a415 api: initial v1.0.0 v1.0.0 2026-01-16 11:52:14 -08:00