What exact supervisor-owned bridge protocol preserves a Pi active turn across Paseo daemon restart? Define durable bridge identity, attach and adoption fencing, command-writer leases, frame sequencing, bounded buffering or spooling, acknowledgments and cursor replay, RPC request-ID generations, pending extension UI requests, process-exit replay, disconnect grace, explicit close, orphan handling, and the terminal outcome when Pi or the supervisor is lost.
Part of #1
Blocked by: #5, #6
## Question
What exact supervisor-owned bridge protocol preserves a Pi active turn across Paseo daemon restart? Define durable bridge identity, attach and adoption fencing, command-writer leases, frame sequencing, bounded buffering or spooling, acknowledgments and cursor replay, RPC request-ID generations, pending extension UI requests, process-exit replay, disconnect grace, explicit close, orphan handling, and the terminal outcome when Pi or the supervisor is lost.
Dependency handoff from the resolved execution-contract ticket: bridge replay must fit behind the lifecycle-oriented process seam. The generic ProcessHandle exposes attachment-scoped byte streams and backend-lifetime identity but no cursor, acknowledgment, generation, or writer-epoch fields. Define those guarantees in the reconnectable Pi transport and supervisor bridge. If durable acknowledgement requires a higher-level checkpoint callback, keep it on that Pi transport rather than widening ProcessHandle for local and future non-JSONL providers.
Dependency handoff from the resolved execution-contract ticket: bridge replay must fit behind the lifecycle-oriented process seam. The generic ProcessHandle exposes attachment-scoped byte streams and backend-lifetime identity but no cursor, acknowledgment, generation, or writer-epoch fields. Define those guarantees in the reconnectable Pi transport and supervisor bridge. If durable acknowledgement requires a higher-level checkpoint callback, keep it on that Pi transport rather than widening ProcessHandle for local and future non-JSONL providers.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1
Blocked by: #5, #6
Question
What exact supervisor-owned bridge protocol preserves a Pi active turn across Paseo daemon restart? Define durable bridge identity, attach and adoption fencing, command-writer leases, frame sequencing, bounded buffering or spooling, acknowledgments and cursor replay, RPC request-ID generations, pending extension UI requests, process-exit replay, disconnect grace, explicit close, orphan handling, and the terminal outcome when Pi or the supervisor is lost.
Dependency handoff from the resolved execution-contract ticket: bridge replay must fit behind the lifecycle-oriented process seam. The generic ProcessHandle exposes attachment-scoped byte streams and backend-lifetime identity but no cursor, acknowledgment, generation, or writer-epoch fields. Define those guarantees in the reconnectable Pi transport and supervisor bridge. If durable acknowledgement requires a higher-level checkpoint callback, keep it on that Pi transport rather than widening ProcessHandle for local and future non-JSONL providers.