RAGE #129: implement ZARA/1 protocol and ZeroMQ client #142
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/zara!142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/129-zara1-protocol"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consumes #129 under TASK #139 / epic #127.
RAGE evidence
b0bc03590215424db01277cbc4758067a7b854abrage/daemon-129-research.orgrage/daemon-129-design.orgrage/daemon-129-gate.orgImplemented #129 slices
ZARA/1multipart framing and bounded validation;ZmqZaraClientbehind the existingZaraClientseam;ipc://endpoint;scripts/test-zara1-protocol.shincluded in the full repository gate.Authentication and hard multi-user isolation remain explicitly deferred to #130/#131.
zararemains the client-facing executable andzara-serverremains the daemon/service.TDD evidence
The work was developed as committed red/green slices. Notable later red findings:
67b0e8dd2ec1c076a1865e583d876e9171bb276f.61ef9d8e4bcce125ad978d1bc573cc711330e158: the focused gate exposed thatturn.completedwas emitted by the server codec but dropped by the client event adapter. Both distro audio lanes remained green.52b447cc9eb7bcf050bba279f03af1b123b9bc3b:turn.completedmaps toAgentCompleted, preserving turn/conversation IDs and success.Final exact-head authority
Candidate:
3ab7d04c6af2e62f00570fb9ebdc731c4eb075c0CI #284 / run
32572470202: GREENscripts/test-all.sh: PASSnix flake check: PASSnix build: PASSThis exact SHA is the merge authority.