chore(showcase): ratchet validate-pins baseline for main (post-4095)

PR CopilotKit#4095 (agno SDK upgrade to 2.5.17) merged into main and shifted the
`[FAIL]` set produced by validate-pins.ts. The FAIL count is unchanged
(110 -> 110), but the hash of the sorted/deduplicated FAIL lines drifted
because a FAIL healed in one package while another regressed — net zero
on the counter, different tuples in the set.

Re-ratchets `showcase/scripts/fail-baseline.json` to reflect current main:
  validatePinsFailCount: 110 (unchanged)
  validatePinsFailHash:  c87ecdd6... -> 958bcf24...

Main CI is red until this lands; please merge ASAP.

Observed from run 24632821166:
  validate-pins FAIL: actual=110 baseline=110
  validate-pins HASH: actual=958bcf24... baseline=c87ecdd6...

Author: jpr5

showcase/scripts/fail-baseline.json

@@ -1,6 +1,6 @@
 {
   "_comment": "Drift ratchet baseline for showcase_validate.yml. `validatePinsFailCount` holds the last-known FAIL count; `validatePinsFailHash` is a SHA-256 of the sorted, deduplicated `[FAIL] ...` lines from validate-pins.ts. CI compares BOTH: if the count changes, it tells you to ratchet (up rejected, down instructed). If the count is equal but the hash differs, the FAIL *set* has drifted (one item fixed, another regressed) and CI fails with a diff. Never raise the count without an explicit review + sign-off. `baselineDemoCount` is the per-package e2e-spec-count floor (single source of truth consumed by both the workflow and validate-parity.ts). NOTE: validate-parity.ts `BASELINE_DEMO_COUNT` default must match `baselineDemoCount` here; keep them in sync. See .github/workflows/showcase_validate.yml 'Run validate-pins (ratchet)' step.",
   "validatePinsFailCount": 110,
-  "validatePinsFailHash": "c87ecdd6cc0829f8ef93c6e3cc4bb30aa3a577f99c5c8e9349b7c2dc78a45560",
+  "validatePinsFailHash": "958bcf24c27cef69d7856e12deafe92073af7ad716289b2f6e4418827264ae17",
   "baselineDemoCount": 9
 }