test(adb): drop prose checks for the push guidance fix

The testing guide asks for structured facts rather than frozen
sentences or banned phrases. The existing mutatesDevice declarations and
push receipt assertions already cover the behavior; the doc-comment
correction stays.

Co-Authored-By: gensokyo-dev <gensokyo-dev@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/adb/AdbProvider.test.ts

@@ -1378,10 +1378,6 @@ exit 1`,
         line.includes("not device-side verified"),
       ),
     ).toBe(!verified);
-    // The device-mutation fact is reported whatever the digest verdict.
-    expect(result.value.limitations).toContain(
-      "Push writes a private snapshot of the caller's file to the device",
-    );
     // Unrecognized checksum output stays inspectable instead of being dropped.
     expect(result.value.rawResult).toEqual(
       !verified && exit === 0

src/contracts/toolEffects.test.ts

@@ -28,14 +28,6 @@ describe("tool effects", () => {
     );
   });
 
-  it("never advertises one tool as the only device-mutating operation", () => {
-    // Several tools declare mutatesDevice, so an exclusive claim misleads callers.
-    const exclusive = TOOL_CONTRACTS.filter(({ description }) =>
-      /\bonly\b[^.!?]*\bmutat/iu.test(description),
-    ).map(({ name }) => name);
-    expect(exclusive).toEqual([]);
-  });
-
   it("marks foreign execution and device mutation as destructive", () => {
     const destructive = TOOL_CONTRACTS.filter(
       ({ effects }) => effects.executesForeignCode || effects.mutatesDevice,