test(server): follow #7151's tool status onto non-Prime rows (#64)

`pylon` has been red since #62. Adopting #7151 carries the adapter's status
onto every tool lifecycle row, not just Prime's, and this suite asserted the
opposite for `tool.started` and `tool.completed`.

The assertions described the behavior before that commit rather than guarding a
Pylon invariant — the test's subject is that Prime-specific handling does not
leak into non-Prime paths, which still holds — so they follow upstream. The
alternative was re-gating status to Prime only, which contradicts #7151's own
test expecting `status: "inProgress"` on a non-Prime `item.started`; the two
cannot both hold, and staying in step wins where Pylon has no stated reason.

Worth remembering: this was caught by CI, not by me. A targeted run covered
ProviderRuntimeIngestion.test.ts and missed the .activity.test.ts sibling, and
I merged #62 without checking that pylon went green afterwards.

Author: rynfar

apps/server/src/orchestration/Layers/ProviderRuntimeIngestion.activity.test.ts

@@ -555,8 +555,13 @@ describe("runtimeEventToActivities Prime tool lifecycle", () => {
       "codex-tool-update",
       "codex-tool-complete",
     ]);
-    expect(started?.payload).toMatchObject({ detail: "echo existing behavior" });
-    expect(started?.payload).not.toHaveProperty("status");
+    // `#7151` carries the adapter's status onto every tool lifecycle row, not
+    // just Prime's. These assertions previously described the behavior before
+    // that commit rather than guarding a Pylon invariant, so they follow it.
+    expect(started?.payload).toMatchObject({
+      detail: "echo existing behavior",
+      status: "inProgress",
+    });
     expect(updated?.payload).toMatchObject({
       status: "inProgress",
       detail: "existing progress",
@@ -568,8 +573,8 @@ describe("runtimeEventToActivities Prime tool lifecycle", () => {
     expect(completed?.payload).toMatchObject({
       detail: "existing result",
       data: { exitCode: 0 },
+      status: "completed",
     });
-    expect(completed?.payload).not.toHaveProperty("status");
 
     const fallbackSummaries = [
       runtimeEventToActivities({