3-verify-pr-fix

# Verify a candidate PR Review the packet, the candidate diff, and relevant tests. Live comparison against a captured baseline is optional. No edits, no merges, no pushes. ## 1. Resolve the PR and its linked issue ```bash PR=$(echo "$ARGUMENTS" | sed -E 's|.*/||; s|#||g' | grep -oE '^[0-9]+' | head -1) [ -z "$PR" ] && { echo "Invalid input: '$ARGUMENTS'. Pass a PR number or URL." >&2; exit 1; } REPO=stickerdaniel/linkedin-mcp-server gh pr view $PR --repo $REPO --json title,body,baseRefName,headRefName,headRepositoryOwner,mergeable,mergeStateStatus,additions,deletions,changedFiles,maintainerCanModify,statusCheckRollup ``` Extract the linked issue number from the PR body (`Closes #`, `Fixes #`, `Resolves #`, or plain `#N`). Call it `ISSUE`. If multiple, ask which one is the verification target. Read that issue's packet and comments. ## 2. Packet, diff, and tests This path does not need `/tmp/repro-issue-$ISSUE-main.json`. Absence of a local baseline limits the live branch, not the whole PR verdict. Do not create fake success or failure files. ```bash gh pr diff $PR --repo $REPO gh pr view $PR --repo $REPO --json files --jq '.files[].path' ``` Hard flags (any one downgrades a clean live pass to concerns): - Locale-dependent detection: `== "Connect"`, `in ["Pending", "Follow"]`, `contains("1st")`, `aria-label="..."` with translated text. Attribute presence is the locale-independent signal. - LinkedIn class-name selectors: `.entity-result__item`, `.artdeco-button__text`...