Repository navigation
Prime Agent integration: coordinate Comet, Pylon, and fork contracts #1
Description
Activity
Milestone: the reviewed native daemon foundation shipped in #4 (merge
de66c08c3687208effe2e2fdb514d6d690f1cc0a), closing #3.Delivered: public-root SDK/package validation, stock protocol-v7 baseline capability offers, stable host-private daemon identity and crash recovery, bounded/cancellable process ownership, provider-compatible environment isolation, deterministic adversarial fixtures, and a real installed Prime Agent 0.8.1 load/connect/shutdown smoke. Architecture and security rereviews found no remaining blockers.
No user-visible Prime session exists yet. I am defining the next separate asynchronous SDK session-host issue now. It will not treat server offers as attach negotiation and will remain blocked on bounded public SDK JSONL ingress at pylon-code/prime-agent#13. Recovery and detached-worker settlement must also align with pylon-code/prime-agent#8 and pylon-code/prime-agent#11 before production session recovery is claimed.
Prime dependency milestone
Prime Agent PR pylon-code/prime-agent#12 merged as
f728316dabbaa85aa561e6d6b08550ed337574be. A fresh review caught and repaired a real event-persistence false-completion path before merge; real ordinary and post-compaction regressions now fail the correlated lifecycle closed.This does not yet create user-visible Prime chat in Comet. Comet #5 remains blocked on one reviewed Prime artifact that also contains accepted zeronsh#11, regenerated #8, and zeronsh#13 outcomes. Work now advances to protected zeronsh#11 coordination; its active dirty worktree will not be modified until its owner checkpoints and declares ownership.
Prime dependency milestone: Prime PR #14 merged at
fd5cadc600f867a0a5a989064cce22934e9dad94, closing Prime zeronsh#11. It provides the reviewed capability-gated snapshot/recovery and authoritative owned-session cleanup contracts required by Comet's native daemon host.The remaining safe-host order is unchanged:
- regenerate and merge Prime docs: simplify agent instructions and skill routing #8 from exact post-Add workspace file mentions to the composer zeronsh/zeron#11
pylon; - implement/review bounded public ingress in Prime Interest in adding Grok Build support? zeronsh/zeron#13;
- claim and implement Comet feat(harness): establish bounded native Prime SDK session host #5.
The fresh #8 regeneration is now active from Prime
a903d4b6768f484bd6d459b7b0aa7dee38e461e2. Comet #5 remains deliberately unclaimed; no native session IDs, paths, credentials, or process details are exposed.- regenerate and merge Prime docs: simplify agent instructions and skill routing #8 from exact post-Add workspace file mentions to the composer zeronsh/zeron#11
Prime upstream governance gate #8 is complete. PR #15 merged as
e7871eb699d0f65047a21d179216ebfec7755d0cafter exact-head reviews, zero conversations, and all trusted hosted jobs passed.Bounded public ingress Prime #13 is now claimed from exact merged
pylonate7871eb699d0f65047a21d179216ebfec7755d0cin an isolated worktree. The declared client-local feature proof/raw-byte limit/error/reconnect contract is under the final joint Prime/Comet design review before source edits.Dependency order is now: zeronsh#15/#8 (done) → zeronsh#13 (active) → Comet #5.
Prime bounded-ingress candidate is now ready as PR #16 at exact head
9013a63a76fa339b5e2898947e9cff040505d72c/ tree814cfa93bfdbab0d43acaa92c208205fd7dd5749on basee7871eb699d0f65047a21d179216ebfec7755d0c.Three commit-bound reviews approved with no P0/P1: transport security, API/resource/governance, and Comet consumer compatibility. Local validation includes 53 focused tests, 13 real-process passes with 8 fixture skips, both stock/current 0.8.1 adoption directions, the 36 MiB indivisible message, deterministic 100/500 MiB bounded-client reconstruction, and exact 64/128 MiB resource probes.
Trusted exact-head hosted CI is running. Comet #5 remains blocked until PR zeronsh#16 passes CI, has no unresolved conversations, receives exact head/base maintainer approval, and merges into
pylon.Prime bounded public daemon ingress PR #16 passed trusted hosted CI and merged as
7238ac8cff25962ada9ffe4530b7d4d1cddc1b47(parentse7871eb699d0f65047a21d179216ebfec7755d0c+9013a63a76fa339b5e2898947e9cff040505d72c, tree814cfa93bfdbab0d43acaa92c208205fd7dd5749). Prime zeronsh#13 is closed.Comet #5 has now been claimed from
origin/main@de66c08c3687208effe2e2fdb514d6d690f1cc0aonfeat/prime-session-host-7238in an isolated worktree. It will require the exact public-rootbounded_daemon_ingress_v1token and constructDaemonClientwith a 64 MiB inbound frame limit under an isolated 512 MiB V8 heap. No production session path will accept stock 0.8.1 or infer support from versions, schemas, methods, constructor arity, or daemon offers.Comet native-session milestone merged: PR #6 (#6) is now
main@9ef2295877d33fe241479471e908105fccbeb434with reviewed treebb5b90da8c098ac595a4b79afbda5ee4513d3d15and parentsde66c08c3687208effe2e2fdb514d6d690f1cc0a+3ba88e519d2b062dc705a4e17629ac135d286020.Delivered: capability-gated public SDK session host, fresh-draft create/attach/snapshot, bounded 64 MiB SDK ingress / 512 MiB V8 / 16 KiB private frames / 8 requests / 32 events, exact stock/fork gates, prestarted cancellation reaper, authoritative owner/nonowner cleanup, poison-horizon preservation, fixed UTF-8 preflight, and host-private native identities.
Exact-head security, API/privacy, and adversarial-test reviews reported no P0/P1. Hosted x86 Linux, ARM Linux, and macOS package builds passed at the reviewed head: https://github.com/rynfar/comet/actions/runs/33298602520.
This remains host-only: no Prime
Harness, registry, prompt stream, model/settings, RPC/document, or UI surface exists yet. The next focused issue will specify the bounded correlated prompt/event host before any user-visible adapter/registration slice.Next focused chain opened after the merged session owner:
- Prime attach-negotiated proof: Expose attach-negotiated daemon session capability proof pylon-code/prime-agent#17
- Pylon consumer correction: Prime correlated prompts must require post-attach capability proof pylon-code/pylon#190
- Comet bounded host-private correlated turn: feat(harness): run one bounded correlated Prime text turn #7
Merge order is Prime proof/artifact -> Pylon compatibility gate -> Comet turn host. Public Harness/opaque resume/registry/UI remain later slices.
Purpose
Coordinate the native Prime Agent integration for this Comet fork with the existing Pylon provider and the Pylon Prime Agent fork. This issue is the Comet-side umbrella. It does not replace the existing cross-repository authorities:
Coordination rules
pylon-code/prime-agent, provider-neutral product semantics topylon-code/pylon, and Comet adapter/UI work here.0.8.1package version.Workstreams
Harnessadapter.Merge bar
A Comet change must name the Prime capability it uses, preserve a safe unsupported path, keep native identities private, include deterministic fake-protocol tests, and link the matching Prime/Pylon issue or state explicitly that no shared contract changes.