Synced from monorepo

Synced from monorepo

Changes:
- Report invalid MCP server config instead of failing startup
- Keep completed terminal output when the gateway connection is lost
- Show a duration-only detail view for single-task task output
- Don't let a stale registry turn counter hide local sessions
- Raise the file-descriptor soft limit on Linux and log effective limits at startup
- Stop aborting when HTTP client construction fails
- Make session thread and runtime spawn failures recoverable
- Fix main-prompt paste parity in the question freeform input
- Fire SessionEnd hooks on /exit and headless quit
- Embed the deployment-config signing public key
- Repaint paste-chip background on inline panel inputs
- Security: prevent acceptEdits from auto-approving agent writes into the always-trusted global hook root
- Fix stacked "Worked for" markers so parks render as status and turns close with exactly one marker
- Parse hooks from config files
- Add a remote kill-switch for managed-config signature verification
- Security: fix workspace file-reference resolution bypassing workspace filesystem confinement

Source-Revision: d02693a856a54f1030695b36b91d276e96b30b23

crates/codegen/xai-grok-pager/tests/pty_e2e/common.rs

@@ -28,10 +28,11 @@ pub(crate) const WELCOME_TIMEOUT: Duration = Duration::from_secs(20);
 /// session spawn) on the agent's single-threaded runtime, and the client-side
 /// `acp_send` has no timeout — so under the fully-parallel pty_e2e suite the
 /// starved agent thread can push this well past the 20s `WELCOME_TIMEOUT`
-/// (leaving the "Loading session…" placeholder up). Sized generously for the
-/// same contention reason as `WRAP_TIMEOUT`, not because resume is slow when
-/// run alone.
-pub(crate) const RESUME_TIMEOUT: Duration = Duration::from_secs(60);
+/// (leaving the "Loading session…" placeholder up). A prior 60s budget still
+/// timed out under CI load with the same stuck-loading signature; match
+/// [`WRAP_TIMEOUT`] (120s) for the same contention reason, not because resume
+/// is slow when run alone.
+pub(crate) const RESUME_TIMEOUT: Duration = Duration::from_secs(120);
 
 /// Substring we wait for on the welcome screen. Matches the menu label `"Quit"`
 /// (`render_welcome_done` / gate menus); case-sensitive, so it does **not**
@@ -976,13 +977,16 @@ pub(crate) fn wait_minimal_ready(harness: &mut PtyHarness) {
 
 /// Quit minimal cleanly. The prompt is always focused (a bare `q` would type
 /// into it), so quit is Ctrl+Q pressed twice (it requires confirmation). Falls
-/// back to the harness kill path if the chord doesn't take.
+/// back to the harness kill path if the chord doesn't take. Give the confirm
+/// chord and process exit enough time under suite load so a SIGKILL does not
+/// cut off the agent mid-`updates.jsonl` flush (which breaks a subsequent
+/// `--continue` resume).
 pub(crate) fn quit_minimal(harness: &mut PtyHarness) {
     let _ = harness.inject_keys(b"\x11"); // Ctrl+Q — arms the confirm
-    harness.update(Duration::from_millis(80));
+    harness.update(Duration::from_millis(200));
     let _ = harness.inject_keys(b"\x11"); // Ctrl+Q — confirms
     match harness
-        .wait_exit_code(Duration::from_secs(5))
+        .wait_exit_code(Duration::from_secs(15))
         .expect("wait for minimal pager exit")
     {
         PtyExitPoll::Running => harness.quit().expect("kill minimal pager after timeout"),