Files
pipelines/app/notes/paste-hero-release-verification.md

2.0 KiB

Paste and mobile identity transition release verification

Candidate base: 9408ec15 (retained Chats workspace), isolated release worktree. Paste: dc152cb2. Hero: 08043c34 + 5d6d4434; scalable header identity: 887ba054. Additional asynchronous file ownership guard: 7246567d.

Checks:

  • 42 focused VM tests passed before the ownership follow-up (/tmp/memwatch/out.yJ6Z34).
  • 15 composer paste tests, including two new ownership regressions, passed after the follow-up (/tmp/memwatch/out.sfE8JR). This is 44 distinct VM cases.
  • Seven production browser clipboard bridge tests passed in Chrome (/tmp/memwatch/out.KdKGFb).
  • Analysis clean after the follow-up (flutter-analyze.IWaHC2).
  • Full-app fixture web build passed at build/probe-paste-hero.

Browser evidence (all listed PNGs inspected):

  • /tmp/review/paste-hero-paste/: full-app 880x1000 dark Material. Synthetic clipboard text dispatched to the document body reaches the real unfocused composer; focused composer keeps native insertion; external textarea keeps paste; synthetic file paste produces the capture.txt attachment chip.
  • /tmp/review/paste-hero-mobile-v2/: full-app 560x1000 Material. The real list row opens its pushed chat page; filmed frames at 332/382 ms show the shared avatar between the row and header positions; completed header keeps one-row controls. Back returns to the list.
  • /tmp/review/paste-hero-cupertino/: same open/return flow with native Cupertino chrome. Film and final states inspected.

Capture scripts: /tmp/paste-hero-paste-capture.json, /tmp/paste-hero-hero-capture.json, /tmp/paste-hero-cupertino-capture.json. The first mobile attempt used a space-normalized label; semantics require the exact newline label, corrected in v2. No product failure was inferred from that.

These are software Chrome captures over fake data, not native device/FPS measurements. No shared server restart, live chat mutation, host clipboard write, APK publication or device installation was performed. Capture drivers exited and cleaned up their owned browsers and loopback servers.