nsaspy/zara
1
0
Fork 0
Code Issues 95 Pull requests 18 Projects Releases Packages Wiki Activity Actions

Make Zara CLI use daemon-owned timers by default #296

Closed
nsaspy wants to merge 1 commit from codex/default-daemon-cli into master
pull from: codex/default-daemon-cli
merge into: nsaspy:master
Conversation 2 Commits 1 Files changed 27 +1383 -73
nsaspy commented 2026-09-04 22:44:14 +00:00
Owner
Copy link

Summary

  • Switches the Zara CLI to daemon-owned timers by default
  • Extends protocol/runtime/backend/server plumbing (ZMQ transport, events)

Changes

  • zara/runtime/backend.py, zara/runtime/events.py, zara/protocol*.py, zara/server*.py, zara/zmq_transport.py
  • 27 files changed, +1383/-73

Merged from local worktree Zarathushtra-default-daemon-cli.

## Summary - Switches the Zara CLI to daemon-owned timers by default - Extends protocol/runtime/backend/server plumbing (ZMQ transport, events) ## Changes - `zara/runtime/backend.py`, `zara/runtime/events.py`, `zara/protocol*.py`, `zara/server*.py`, `zara/zmq_transport.py` - 27 files changed, +1383/-73 Merged from local worktree `Zarathushtra-default-daemon-cli`.
Make Zara CLI use daemon-owned timers by default
Some checks failed
CI / test (pull_request) Failing after 10s
Details
CI / shared mic / Arch Linux (pull_request) Failing after 10m51s
Details
CI / shared mic / Ubuntu 24.04 (pull_request) Failing after 14m13s
Details
6d704b0892
nsaspy commented 2026-09-04 22:52:37 +00:00
Author
Owner
Copy link

Review triage (2026-08-29): the timer-lifecycle work is serious and well-tested (typed TimerLifecycleRecord with strict shape validation, daemon-owned timer pump, 196-line backend test), and daemon-owned timers align with the client-migration direction of #133.

Blocking merge: (1) conflicts with the RAGE-reviewed daemon runtime contracts (zara/protocol.py, runtime/backend.py, zmq_transport.py) — the rebase must reconcile with ZARA/1 protocol versioning from #129/#130; adding SERVER_MESSAGE_TYPES is a contract-surface change that needs that review; (2) zara/prolog_engine.py +130 lines — AGENTS.md makes this the canonical Prolog access layer, so the timer-event drain design needs review against the module boundary rules; (3) AGENTS.md edits are doc-alignment and acceptable, flake.nix changes need separate verification. Keeping open as queued feature work behind P0 #134; it maps under daemon epic #127.

Review triage (2026-08-29): the timer-lifecycle work is serious and well-tested (typed TimerLifecycleRecord with strict shape validation, daemon-owned timer pump, 196-line backend test), and daemon-owned timers align with the client-migration direction of #133. Blocking merge: (1) conflicts with the RAGE-reviewed daemon runtime contracts (zara/protocol.py, runtime/backend.py, zmq_transport.py) — the rebase must reconcile with ZARA/1 protocol versioning from #129/#130; adding SERVER_MESSAGE_TYPES is a contract-surface change that needs that review; (2) zara/prolog_engine.py +130 lines — AGENTS.md makes this the canonical Prolog access layer, so the timer-event drain design needs review against the module boundary rules; (3) AGENTS.md edits are doc-alignment and acceptable, flake.nix changes need separate verification. Keeping open as queued feature work behind P0 #134; it maps under daemon epic #127.
nsaspy commented 2026-09-04 22:52:37 +00:00
Author
Owner
Copy link

Closing this stale implementation while preserving the timer requirement. The branch predates the current typed intent/capability plane, RuntimeHost ownership, principal isolation, long-horizon task runtime, and recent hook/backend work, so reviving its 27-file daemon/protocol patch would reintroduce obsolete wiring. set a timer ... remains required and should be implemented/recovered from current master through the canonical daemon-owned timer/service path under the current semantic/runtime contracts, not by merging this head.

Closing this stale implementation while preserving the timer requirement. The branch predates the current typed intent/capability plane, RuntimeHost ownership, principal isolation, long-horizon task runtime, and recent hook/backend work, so reviving its 27-file daemon/protocol patch would reintroduce obsolete wiring. `set a timer ...` remains required and should be implemented/recovered from current `master` through the canonical daemon-owned timer/service path under the current semantic/runtime contracts, not by merging this head.
nsaspy closed this pull request 2026-09-05 01:42:23 +00:00
Some checks failed
CI / test (pull_request) Failing after 10s
Details
CI / shared mic / Arch Linux (pull_request) Failing after 10m51s
Details
CI / shared mic / Ubuntu 24.04 (pull_request) Failing after 14m13s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara!296
No description provided.