How do agent-session lifecycle, Pi native persistence, sandbox resource state, active-turn attachment state, and cleanup intent compose atomically across create, cancel, close, archive, delete, Pi crash, daemon crash, and restart? Define persisted state, ownership, reconciliation outcomes, idempotency, and the boundary between reattaching an active resource and resuming a conversation in a new resource.
Part of #1
Blocked by: #14
## Question
How do agent-session lifecycle, Pi native persistence, sandbox resource state, active-turn attachment state, and cleanup intent compose atomically across create, cancel, close, archive, delete, Pi crash, daemon crash, and restart? Define persisted state, ownership, reconciliation outcomes, idempotency, and the boundary between reattaching an active resource and resuming a conversation in a new resource.
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: #14
Question
How do agent-session lifecycle, Pi native persistence, sandbox resource state, active-turn attachment state, and cleanup intent compose atomically across create, cancel, close, archive, delete, Pi crash, daemon crash, and restart? Define persisted state, ownership, reconciliation outcomes, idempotency, and the boundary between reattaching an active resource and resuming a conversation in a new resource.