fix(runner): preserve Pi 1.0 serialized RPC events

Co-Authored-By: Paperclip <noreply@paperclip.ing>

tests/runner-e2e/FIXTURES.md

@@ -384,7 +384,7 @@ The explicit-only `pi-controls` suite adds `pending-permission-stop` and
 `same-turn-steering` on local and Daytona, each with one provider run, a
 120-second active-turn timeout and a 300-second attempt budget. These four
 control cases retain their behavior; the current matrix totals 26 Pi cells.
-Pi 1/profile 11 and coverage revisions intentionally change the affected suite
+Pi 1/profile 12 and coverage revisions intentionally change the affected suite
 fingerprints, so older qualification receipts cannot be reused. Catalog presence and
 deterministic calibration do not constitute paid qualification.
 

tests/runner-e2e/README.md

@@ -39,8 +39,9 @@ native-write evidence, caller-owned control acknowledgments, independent
 no-effect/retirement proof and the actual production task UI. Daytona also
 requires the existing immutable image and executable digests. These cells do
 not establish native follow-up queue persistence or provider-death recovery.
-The current Pi matrix has 25 explicit cells (13 local and 12 Daytona), including
-these four controls and the pending-native-question restart cases. Pi's profile
+The current Pi matrix has 26 explicit cells (13 local and 13 Daytona), including
+these four controls, the pending-native-question restart cases, and one Daytona
+provider-death case. Pi's profile
 remains pending; catalog presence is not live qualification.
 
 ## Provider-free browser bootstrap regression

tests/runner-e2e/pi-controls-evidence.test.ts

@@ -129,15 +129,15 @@ describe("Pi controls catalog admission", () => {
     expect(() => assertRemoteNativeEvidencePrerequisites(cells, {})).toThrow();
   });
   it("pins the Pi 1 profile and versioned coverage while retaining active Stop identity", () => {
-    // Pi 1/profile 11 changes profile-bearing definitions. Coverage v4/v2 adds
+    // Pi 1/profile 12 changes profile-bearing definitions. Coverage v4/v2 adds
     // provider death, pending restart and the strict file oracle; no runtime admission is promoted.
     const pi = runnerMatrix.find(c => c.profile.qualificationCandidate === "pi")!.profile;
     expect(pi.modelQualification?.qualificationId).toBe("pi:0.0.33:1.0.0:openrouter");
-    expect(runnerSuites.find(s => s.id === "pi-native")!.definitionMetadata).toMatchObject({ version: 4, profileVersion: 11 });
+    expect(runnerSuites.find(s => s.id === "pi-native")!.definitionMetadata).toMatchObject({ version: 4, profileVersion: 12 });
     expect(runnerSuites.find(s => s.id === "extended-harnesses")!.definitionMetadata).toMatchObject({ version: 2 });
     const hashes = Object.fromEntries(runnerSuites.filter(s => ["pi-native", "native-active-stop", "extended-harnesses", "rich-acp-warm-continuity"].includes(s.id)).map(s => [s.id, suiteDefinitionHash(s)]));
     expect(hashes).toEqual({
-      "pi-native": "8c4d4f1cba234223ee54b5a19d5fe3f815424e7335cf15f43bd3f77d342aec74",
+      "pi-native": "eec3b2c140d81561e69c13c1b193b66f7790af0cfc90bbed76c57af2d1e3cdde",
       "native-active-stop": "99682b2b106d816a011834fae5a944ed7729958893709d5b83a19b6f595e7e4d",
       "rich-acp-warm-continuity": "25e69f031696aeb459e6722a056ae0802379f9137799648fdd1945881f32f41a",
       "extended-harnesses": "e50f79cf604bffb2cdee3ad4e8bc1d106045a4f44ef07e877032ff5b8960c8ab",