Prime Agent integration: coordinate Comet, Pylon, and fork contracts

[rynfar]

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:

• Fork contract and upstream-overlap tracker: Track Pylon fork parity and upstream overlap pylon-code/prime-agent#1
• Pylon provider-parity umbrella: Prime provider parity: tasks, automation, and upstream watch pylon-code/pylon#114

Coordination rules

• Start implementation only from a claimed, cross-linked issue.
• Route Prime daemon/API changes to pylon-code/prime-agent, provider-neutral product semantics to pylon-code/pylon, and Comet adapter/UI work here.
• Record contract dependencies, capability names, compatibility behavior, owning branches/worktrees, test receipts, and merge order in the issues.
• Use isolated worktrees. Never reset, stash, switch, stage, or commit another harness's active work.
• Keep optional behavior capability-gated. Do not infer fork support from the 0.8.1 package version.
• Do not merge one side of a shared contract until both consumers' compatibility tests have been reviewed together.
• Keep Prime's local daemon/socket/session paths inside the host engine. Do not expose raw local protocol or private paths through Comet sync.

Workstreams

• Merge correlated-lifecycle queue and post-compaction integrity fixes in the Prime fork.
• Merge immutable snapshot/recovery integrity work.
• Audit and merge the Prime upstream sync candidate.
• Produce a reproducible, uniquely hashed Prime artifact.
• Merge the capability-negotiated native daemon foundation and authoritative private session owner (feat(harness): establish native Prime daemon foundation #4 and feat(harness): own bounded native Prime sessions #6).
• Verify stock-Prime degradation and fork-capable session behavior independently.
• Add the bounded correlated prompt/event host as a focused host-only issue.
• Map safe Prime turns into a hidden normalized Comet Harness adapter.
• Register models/settings and expose the first text-only user-visible Prime chat preview.
• Add opaque resume, steering/interruption recovery, and subagents as separate reviewed contracts.
• Extend provider-neutral surfaces for Prime resources, queues, compaction, refinement, goals, and automation as separate issues.

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.

[rynfar]

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.

[rynfar]

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 zeronsh#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.

[rynfar]

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:

1. regenerate and merge Prime Use native word-editing shortcuts on every platform zeronsh/comet#8 from exact post-Add workspace file mentions to the composer zeronsh/comet#11 pylon;
2. implement/review bounded public ingress in Prime Interest in adding Grok Build support? zeronsh/comet#13;
3. claim and implement Comet feat(harness): establish bounded native Prime SDK session host #5.

The fresh zeronsh#8 regeneration is now active from Prime a903d4b6768f484bd6d459b7b0aa7dee38e461e2. Comet #5 remains deliberately unclaimed; no native session IDs, paths, credentials, or process details are exposed.

[rynfar]

Prime upstream governance gate #8 is complete. PR #15 merged as e7871eb699d0f65047a21d179216ebfec7755d0c after exact-head reviews, zero conversations, and all trusted hosted jobs passed.

Bounded public ingress Prime #13 is now claimed from exact merged pylon at e7871eb699d0f65047a21d179216ebfec7755d0c in 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/zeronsh#8 (done) → zeronsh#13 (active) → Comet #5.

[rynfar]

Prime bounded-ingress candidate is now ready as PR #16 at exact head 9013a63a76fa339b5e2898947e9cff040505d72c / tree 814cfa93bfdbab0d43acaa92c208205fd7dd5749 on base e7871eb699d0f65047a21d179216ebfec7755d0c.

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.

[rynfar]

Prime bounded public daemon ingress PR #16 passed trusted hosted CI and merged as 7238ac8cff25962ada9ffe4530b7d4d1cddc1b47 (parents e7871eb699d0f65047a21d179216ebfec7755d0c + 9013a63a76fa339b5e2898947e9cff040505d72c, tree 814cfa93bfdbab0d43acaa92c208205fd7dd5749). Prime zeronsh#13 is closed.

Comet #5 has now been claimed from origin/main@de66c08c3687208effe2e2fdb514d6d690f1cc0a on feat/prime-session-host-7238 in an isolated worktree. It will require the exact public-root bounded_daemon_ingress_v1 token and construct DaemonClient with 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.