feat(harness): establish native Prime daemon foundation - #4
Merged
Conversation
This was referenced Aug 30, 2026
This was referenced Aug 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Establish the host-private native Prime Agent daemon foundation for #1.
prime-agentexecutable to its canonical package and public root ESM export;VERSION,DAEMON_PROTOCOL_NAME, protocol v7+,DaemonClient, andDaemonAgentConnection.attachbefore daemon spawn;Closes #3.
Boundary
This PR is lifecycle bootstrap only. It creates no Prime session and adds no registry, RPC, synchronized document, model, or UI state. Session events must use a later asynchronous SDK host with response/event demultiplexing. Fork-only behavior remains disabled until both server and attach-side client capabilities negotiate it.
The later session slice is explicitly blocked on bounded public SDK ingress in pylon-code/prime-agent#13. Detached Prime session workers also need authoritative shutdown plus worker/descriptor reconciliation; the process groups here do not claim ownership of detached workers.
Compatibility and privacy
correlated_prompt_lifecycle_v1.>= 7rule.serverCapabilitiesare offers, not active negotiation.exports["."]; canonical Node and canonical CLI targets bypass wrappers after discovery.Validation
cargo test --offline -p zeron-harness prime:: --lib— 15 passedcargo test --offline -p zeron-harness --test prime_daemon— 23 passed, 1 opt-in smoke ignoredcargo test --offline -p zeron-harness --lib -- --skip shell_env::unix::tests::falls_back_when_interactive_attempt_hangs— 105 passedcargo clippy --offline -p zeron-harness --all-targets -- -D warningswith only six explicit pre-existing lint exceptions — passedrustfmt --check— passednode --check crates/harness/src/prime/shim.mjs— passedgit diff --check— passedThe skipped
shell_env::unix::tests::falls_back_when_interactive_attempt_hangsfailure reproduces unchanged onorigin/mainatb520992(Option::unwrap()atshell_env.rs:330). Existing unrelated ACP unused-assignment warnings are unchanged.Two independent final rereviews found no remaining merge blockers: one architecture/contract review and one adversarial process/privacy/path review.
Coordination