Integrate master into the v0.9.6 candidate

Brings in the two test-only repairs landed 2026-08-06:
- PR #87 (6664f8e) order run-binding cleanup after fixture readiness
- PR #88 (9fbf6e4) derive the expected renderer policy from the platform

Delta is +24/-2 across test/eval/agent-workflow-run-binding.test.js and
test/render-pdf-page.test.js. No product, manifest, or dependency change.

Merged so the shipped head carries both fixes and the release aggregate binds
the tree that actually ships, rather than an ancestor.

Author: silverstein

test/eval/agent-workflow-run-binding.test.js

@@ -1087,6 +1087,7 @@ setInterval(() => {}, 1000);
     let caught = null;
     let parentPid = null;
     let grandchildPid = null;
+    let settledAt = null;
     const startedAt = Date.now();
     try {
       await Promise.race([
@@ -1110,6 +1111,7 @@ setInterval(() => {}, 1000);
     } catch (error) {
       caught = error;
     } finally {
+      settledAt = Date.now();
       if (watchdog !== null) clearTimeout(watchdog);
       const readFixturePid = async filename => {
         try {
@@ -1124,7 +1126,19 @@ setInterval(() => {}, 1000);
       parentPid = Number.isSafeInteger(reportedPid) && reportedPid > 0
         ? reportedPid
         : await readFixturePid(parentPidPath);
+      // The injected killProcess denies every real signal, so the fixture is
+      // still running once the runner gives up, and it records its grandchild
+      // pid on its own schedule rather than inside the runner's rejection
+      // budget. Wait for that observable readiness before the process group is
+      // killed below, otherwise a slow host lets the kill beat the write and
+      // the pid these assertions need is never recorded. The wait is bounded so
+      // a genuinely missing pid still fails instead of hanging.
       grandchildPid = await readFixturePid(grandchildPidPath);
+      const readinessDeadlineAt = Date.now() + 2_000;
+      while (grandchildPid === null && Date.now() < readinessDeadlineAt) {
+        await new Promise(resolve => setTimeout(resolve, 5));
+        grandchildPid = await readFixturePid(grandchildPidPath);
+      }
       if (parentPid !== null) {
         try {
           process.kill(-parentPid, "SIGKILL");
@@ -1152,7 +1166,10 @@ setInterval(() => {}, 1000);
         await new Promise(resolve => setTimeout(resolve, 10));
       }
     }
-    expect(Date.now() - startedAt).toBeLessThan(5_000);
+    // Bound the runner's own rejection, measured when the race settled, not the
+    // fixture teardown that follows it.
+    expect(settledAt).not.toBeNull();
+    expect(settledAt - startedAt).toBeLessThan(5_000);
     expect(caught).toMatchObject({
       code: "CODEX_PROCESS_TERMINATION_UNVERIFIABLE",
       process_result: {
@@ -1180,6 +1197,7 @@ setInterval(() => {}, 1000);
     });
     expect(parentPid).not.toBeNull();
     expect(grandchildPid).not.toBeNull();
+    expect(await fs.readFile(grandchildReadyPath, "utf8")).toBe("ready");
     for (const pid of [-parentPid, parentPid, grandchildPid]) {
       expect(() => process.kill(pid, 0)).toThrow(
         expect.objectContaining({ code: "ESRCH" }),

test/render-pdf-page.test.js

@@ -163,7 +163,11 @@ describe("render_pdf_page MCP tool", () => {
         size_bytes: sourceBytes.length,
       },
       raw_pixel_status: "available",
-      renderer_policy: "native_with_system_fallback",
+      // The system-renderer fallback is a macOS capability, so pdfjsRendererPolicy
+      // reports plain "native" everywhere else. The hardcoded darwin value failed
+      // on every non-darwin host; it stayed hidden because the aggregate gate runs
+      // on macOS.
+      renderer_policy: process.platform === "darwin" ? "native_with_system_fallback" : "native",
     });
     expect(result.structuredContent.png_sha256)
       .toBe(createHash("sha256").update(Buffer.from(image.data, "base64")).digest("hex"));