docs(readme): swap the connectors frame to its TASK-162 re-render (TASK-165)

[lilyshen0722]

TASK-165's last input. Both byte-twins move to the connectors frame redrawn over #1978.

What changed

path	before	after
docs/assets/readme/connectors-2x.png	a1fbf5d2 / 199832 B	dbf5bb2c / 211471 B
frontend/src/assets/landing/connectors.png	a1fbf5d2 / 199832 B	dbf5bb2c / 211471 B

Both paths carry the same blob — git ls-files -s prints
100644 dbf5bb2c46166052843fe6c937a4c636692c19ba for each — so the landing page
and the README cannot drift apart.

Provenance of the bytes

• Redrawn by ux-lead (their connectors-1440-2x.png), 2880×1800, DPR 2, viewport
  1440×900, at rest: 0 interactive :hover, activeElement is body, and a
  pointer parked on blank page gives the same bytes.
• Render base is main 6b079b11 (the fix(v2): the connectors row's hover, name gutter, and line 3 (TASK-162) #1978 squash, TASK-162), whose frontend
  tree is 9d3de92f — the tree gated at 112c9af0.
• Two runs were byte-identical. Fixture is frame 4's, unchanged.
• The bytes were taken from the rendered file rather than transcribed: the copy
  hashes to dbf5bb2c in the index, which is the same object the author named.

Verification

• frontend/src/v2/landing/__tests__/landingFrames.test.ts — the paired
  byte-twin guard that lists ['connectors.png', 'connectors-2x.png'] — passes.
• All five landing suites: 37/37, under node v22 (CI=true npx jest src/v2/landing/__tests__ --watchAll=false --forceExit).
• No test, alt or caption edits, per ux-lead: the README <img> at :66 and the
  landing row's alt text were already correct for this frame.

Gate

ux-lead: the render, and the two placements (README frame at 880, landing row).
Nothing else in TASK-165 is left after this — frames 1, 2, 4 and 5 are already on
main.

[lilyshen0722]

UX-GATE: PASS @ c4e3281

This is an asset swap. I checked it against the frame I rendered and delivered for TASK-165 at 19:38Z.

• Both docs/assets/readme/connectors-2x.png and frontend/src/assets/landing/connectors.png are git blob dbf5bb2c (211471 B, 2880×1800 RGB). That is byte-identical to the frame rendered over main 6b079b1. Main has a1fbf5d2 at both paths.

• The diff is exactly those two files. README.md and both locales are untouched, so the README alt, the caption and landing.features.connectors.alt (en + zh) don't change. They still describe the new frame clause by clause: Telegram → Launch, Slack → Support, Telegram open with Launch and Support reaching it and Website and Growth off, GitHub granted to Launch for Wren, Kai and Vera.

• The merge-base is main 6b079b1 and the PR is 0 behind, so the frame was drawn on the tree this lands on. The old frame is also 2880×1800, so the README column (838) and the landing rows (573.4 at 1200, 342 at 390) lay out unchanged.

• The picture changes only in the channel rows and the GitHub row:

  • a 12 px name gutter;
  • "escalations reach the channel" beside a 14 px bell on Telegram and Slack;
  • Discord and WhatsApp stacked clear of "Not yet.";
  • a channel card 258 tall instead of 260.

  The header, rail, Tools controls and aside are byte-identical to the old frame.

• The single commit is Lily-authored and carries no co-author trailer.

Not measured here: CI. E2E, Test & Coverage and CodeQL (javascript-typescript) were still running when I stamped this.