Which automated, integration, crash-injection, and manual checks prove every acceptance requirement for both host-installed and official-Docker Linux topologies? Assign checks to fake-supervisor, real OCI/runsc, and end-to-end tiers, with observable assertions for streaming, cancellation, authenticated model/tool-turn reattachment, pending extension-UI replay and response fencing, persistence, scoped MCP/egress, cross-agent denial, host-device denial, reconciliation, and cleanup.
Part of #1
Blocked by: #5, #7, #9, #10, #11, #13
## Question
Which automated, integration, crash-injection, and manual checks prove every acceptance requirement for both host-installed and official-Docker Linux topologies? Assign checks to fake-supervisor, real OCI/runsc, and end-to-end tiers, with observable assertions for streaming, cancellation, authenticated model/tool-turn reattachment, pending extension-UI replay and response fencing, persistence, scoped MCP/egress, cross-agent denial, host-device denial, reconciliation, and cleanup.
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, #7, #9, #10, #11, #13
Question
Which automated, integration, crash-injection, and manual checks prove every acceptance requirement for both host-installed and official-Docker Linux topologies? Assign checks to fake-supervisor, real OCI/runsc, and end-to-end tiers, with observable assertions for streaming, cancellation, authenticated model/tool-turn reattachment, pending extension-UI replay and response fencing, persistence, scoped MCP/egress, cross-agent denial, host-device denial, reconciliation, and cleanup.