chore: pick up @metaharness/darwin@0.12.1's contrastive deadline fix (#4359)

metaharness#424 (merged 9c5e8e61, published as @metaharness/darwin@0.12.1
in ruvnet/metaharness#425) fixed the contrastive development loop's
timeoutMs restarting per callback instead of enforcing one deadline
across a round. @claude-flow/cli's existing "~0.12.0" pin already
covers 0.12.1, so only the lockfile's resolved version needs updating
to actually pick it up — no package.json change needed.

Hand-edited the two affected pnpm-lock.yaml entries rather than
regenerating: a full `pnpm update` cascaded into unrelated major
transitive bumps (vite 7->8, zod 3->4) across the workspace. Verified
with `pnpm install --frozen-lockfile` and confirmed the resolved
package contains the fix.

Co-authored-by: r <r@x>

v3/pnpm-lock.yaml

@@ -213,7 +213,7 @@ importers:
         version: link:../memory
       '@metaharness/darwin':
         specifier: ~0.12.0
-        version: 0.12.0
+        version: 0.12.1
       '@metaharness/flywheel':
         specifier: ~0.1.10
         version: 0.1.10
@@ -1732,8 +1732,8 @@ packages:
     resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==}
     dev: false
 
-  /@metaharness/darwin@0.12.0:
-    resolution: {integrity: sha512-opUL/Ho/48I0HWs+eSePVkrl1O9F+MreFakw2nYJGT5tG92DtOSmeFcpzLAEWt5Rnr5xNFZ0Ieg0RMKRhUyqiw==}
+  /@metaharness/darwin@0.12.1:
+    resolution: {integrity: sha512-LJfSbi2kOwEoyao5NrwgB4JeIbQPBmFPdF5njhS4gK3Z0GU3eqkvrGcw66OLuwP4hUIk/U7prhz0zZTq0uFkDw==}
     engines: {node: '>=20.0.0'}
     hasBin: true
     requiresBuild: true