Add capability-proved nonpersistent daemon workers

[rynfar]

Outcome

Add a capability-gated fresh daemon-worker mode that does not create or append the worker recovery journal, and returns an exact create receipt proving that mode. This unblocks the host-private correlated Comet text turn without persisting its random lifecycle correlation token.

Coordination

• Prime fork umbrella: Track Pylon fork parity and upstream overlap #1
• merged correlated lifecycle/proof contract: Expose attach-negotiated daemon session capability proof #17 and PR feat(sdk): prove negotiated daemon session capabilities #18 (pylon@91e13b6798343995291ccca6f523fba81ff96cd6)
• Comet consumer blocker: feat(harness): run one bounded correlated Prime text turn rynfar/comet#7
• Comet umbrella: Prime Agent integration: coordinate Comet, Pylon, and fork contracts rynfar/comet#1
• Pylon consumer umbrella: Prime provider parity: tasks, automation, and upstream watch pylon#114

An independent Comet #7 review found that the approved correlated lifecycle is copied into the worker recovery journal. The snapshot and correlated queued actions contain correlationId. Comet #7 explicitly forbids logging, serializing, persisting, hashing, or exporting its host-random correlation token. Comet cannot solve that below Prime's public API.

Public contract

Proposed names, to freeze during review:

• frozen root SDK feature: nonpersistent_daemon_worker_v1;
• daemon server capability: nonpersistent_daemon_worker_v1;
• optional fresh-create field: workerRecovery: "disabled";
• successful create summary receipt: workerRecovery: "disabled".

The mode is available only when all of these agree. Method presence, versions, schemas, an ignored create option, or the server offer alone are not proof.

The request is valid only for a fresh lifecycle:"client_owned" create with no sessionPath/resume selector. Ordinary creates omit the field and preserve current recovery behavior byte-for-byte. Older/stock artifacts ignore no new requirement and remain usable by consumers that do not request this mode.

Required behavior

1. Validate the request at the supervisor before launch.
2. Mark the worker descriptor as nonrecoverable without storing any prompt correlation or prompt payload there.
3. Do not pass DAEMON_WORKER_RECOVERY_JOURNAL_ENV to that worker. No worker recovery journal may be created or appended during create, prompt ownership, queueing, delivery, terminal settlement, or cleanup.
4. Never recover or reuse a nonpersistent worker after process loss. Preserve client-owned cleanup authority and retire its descriptor/process ownership safely.
5. Return workerRecovery:"disabled" only for the exact worker generation launched in this mode. Contradictory, stale, resumed, or ordinary workers must not receive the receipt.
6. Keep correlated lifecycle behavior, bounded ingress, attach proof, cancellation, and ordinary worker recovery unchanged.
7. Classify the protocol change as backward-compatible and capability-gated. Increment the schema revision and update SDK/daemon docs plus Pylon ownership records.

Acceptance tests

• SDK feature registry and server offer are exact and frozen/current.
• A valid fresh client-owned create receives the exact disabled-recovery receipt.
• Missing feature/offer, omitted option, malformed option, wrong lifecycle, saved-session selector, and ignored-option simulations cannot produce the receipt.
• No recovery journal file exists before, during, or after a correlated prompt lifecycle whose correlation is a privacy canary; descriptor/session artifacts contain no canary.
• A killed nonpersistent worker is not relaunched or recovered; authoritative client-owned cleanup still settles and removes ownership.
• Ordinary resident/client-owned workers still write and recover from their journal under the existing tests.
• Daemon restart/descriptor discovery treats a dead nonpersistent worker as nonrecoverable and never synthesizes a recovery lifecycle.
• Exact-artifact no-model smoke binds the installed package to its package hash and proves the new create receipt plus current-generation correlated capability.

Merge order

1. Implement and independently review this issue on a branch from current pylon.
2. Produce and verify an exact package artifact.
3. Update Comet chore(pylon): harden fork synchronization #7 to require the SDK feature, server offer, request option, exact create receipt, and existing post-attach correlated proof.
4. Re-review Pylon's existing correlated consumer for compatibility; no provider behavior should change because it omits the new create field.
5. Merge Comet chore(pylon): harden fork synchronization #7 only after both consumers approve the exact Prime artifact.

[rynfar]

Claiming implementation.

• repository: pylon-code/prime-agent
• branch: feat/nonpersistent-daemon-worker
• worktree: /Users/rynfar/.prime/worktrees/prime-nonpersistent-worker
• base: pylon@91e13b6798343995291ccca6f523fba81ff96cd6
• owned area: SDK feature registry/docs, daemon protocol/session-summary/worker-descriptor contracts, supervisor launch/recovery/receipt logic, focused daemon and issue-20 regressions, .pylon/features.yaml, and .pylon/upstream-review.md
• shared contract: nonpersistent_daemon_worker_v1 plus fresh create/receipt workerRecovery:"disabled"; names remain subject to exact-head cross-consumer review
• compatibility: ordinary creates and stock artifacts preserve current recovery; the new mode is optional, fresh, client-owned, non-resumable, and must never write a worker recovery journal
• dependencies: Prime Expose attach-negotiated daemon session capability proof #17/PR feat(sdk): prove negotiated daemon session capabilities #18 are merged; Comet chore(pylon): harden fork synchronization #7 will remain blocked until an exact artifact from this issue is approved
• validation: focused tests from the package root, npm run check, exact artifact/reproduction, journal privacy canaries, killed-worker cleanup/nonrecovery, and independent Prime/Pylon/Comet review
• merge order: Prime Add capability-proved nonpersistent daemon workers #20 -> exact artifact -> Comet chore(pylon): harden fork synchronization #7 consumer repair -> compatibility re-review -> Comet PR

I will not push or open a PR until a frozen exact head has no P0/P1 review findings.