[Add] Check out a pull request from the Apply panel (#458) - #461

…kets (#463)

## Why

Leaving a ticket with a PR applied and returning to it reopened the
ticket branch instead of the saved PR. A real older WordPress PR also
exposed 1,784 generated Gutenberg files as the contributor's changes,
and reviewing a large added file failed with `Maximum call stack size
exceeded` while the screen claimed there was nothing to send.

## What changes

Tickets remember their applied local PR across unlink, switching tickets
and app restart. **Revert this PR** clears that association and restores
the ticket work; edits on the PR stay with its local copy. Restoring a
PR pauses the watcher, installs dependencies only when the lockfile
changes, and rebuilds the site.

The single highlighted banner stays inside the ticket card, using **PR
#N is applied** and **Revert this PR**. Existing Apply wording and the
`.patch`/`.diff` mechanism remain. Other source actions are hidden while
a PR is applied. Ticket actions remain disabled, with a visible reason,
until applying or reverting and its rebuild finish.

Generated `/gutenberg/` files remain ignored when an older PR's
`.gitignore` is checked out. The review excludes generated additions
already parked by older app versions, while retaining changes to files
present in the original base. Updating `diff` from 5.2 to 8.0.4 fixes
large-file patch generation. Failed reviews show an error rather than an
empty-state claim, and PR reviews name the PR as their comparison base.

## How to test this

**Platforms:** macOS and Windows, on this PR's **current head**. The top
PR's code includes #459, #460 and #461. No signed Buildkite artifact has
been verified for this head yet.

From the repository root:

```sh
npm test
npm run test:electron
npm run test:e2e
```

`tests/e2e/journeys/pr-checkout.spec.js` covers apply → edit → unlink →
restart → relink → switch tickets → revert. It verifies that saved PR
edits and the original ticket edits return separately, that a restored
PR actually rebuilds its assets, and that an explicit revert stops
automatic PR restoration. Its regression cases were run red before the
fixes. The failed-review journey verifies that a read error cannot
become “nothing to send.” The IPC regressions cover untracked and
previously parked generated files, a 150,000-line text addition, and
conditional installation on PR restoration.

The existing patch journeys verify apply/revert and persistence for
`.patch` files. **What must not happen:** PR edits must not overwrite
ticket work; restoration must not replace the saved copy with a new
GitHub head; unchanged lockfiles must not trigger an install; generated
Gutenberg downloads must not appear as the contributor's work.

**Local macOS package:** built unsigned from `c71fbb7`, with all 15
packaged smoke tests passing. The packaged main process, renderer bundle
and ticket-action module match the current build byte-for-byte.

**Real-repository check performed on macOS:** an isolated local clone of
the reported `wordpress-develop` PR #8906, including the old WIP commit
with all 1,784 generated files, opens Review with zero contributor
changes and no exception. The original site was not modified.

**Remaining manual coverage:** a signed Windows build, live GitHub
fetching, long real dependency installs, OS file dialogs and real
build-watch processes. The automated journeys use a local Git remote and
small npm scripts; their passing result does not claim those external
checks.

## Risks and limitations

Generated files already stored in old WIP commits are not deleted or
rewritten; the review excludes additions under `/gutenberg/` absent from
the original base. The app retains local PR branches after reverting. PR
edits still cannot be submitted as a new contribution through this flow.
An already-unlinked ticket from an older app version has no saved
active-PR association; apply that PR again once.

The independent review found four issues in PR restoration and its
integration; all were fixed and re-reviewed. Review record below.

## Related

Stacked on #461 → #460 → #459. Part of #458. This PR preserves the
existing stack commits.

<details>
<summary>Review outcome</summary>

- **Review:** completed — independent Codex agent `review_final_stack`;
reviewed base/HEAD `a55df1e85595b8de6309371fbd83c987def0f081` plus the
complete pending diff. Four runtime findings fixed across re-review:
restored-PR build/install, missing new-ticket destination, cancellation
handler, and terminal ownership. One terminal test fixture correction
applied. Final outcome: **0 remaining [fix here] · 0 [follow-up]**.
- **Since review:** committed as `9b49879`; the commit contains the
reviewed pending work, including the final fixture correction and
screenshot, then `9b49879 → 6709d44` reviewed independently: only two
test fixtures changed to use explicit Git identity after Windows CI
exposed reliance on host configuration. No runtime changes in that
delta. The subsequent `6709d44 → c71fbb7` delta was reviewed
independently with zero findings: publish ticket-switch callbacks in a
layout effect and keep ticket actions blocked through the entire
PR/patch operation. The latter fixes a real Windows journey failure
where Unlink was clickable before Revert had finished; its new unit
regression was red before the fix and green afterward.

- **CodeRabbit:** completed a review of `9b49879` and raised one
actionable finding (callbacks assigned to a ref during render). Fixed in
`c71fbb7` with a layout effect and independently re-reviewed. Subsequent
green CodeRabbit statuses say **Review skipped**, so the independent
review is the review of record for the final head.

Validation on `c71fbb7`: Node 1,417 passed, 2 expected skips; Electron
1,419 passed; all 29 journeys passed in one run; 15 local packaged smoke
tests passed; lint clean. Final-head CI is green on macOS and Windows:
unit suites, all journeys and packaged smoke tests; lint and docs build
pass. [E2E
run](https://github.com/WordPress/contributor-toolkit/actions/runs/34770983332),
[unit
run](https://github.com/WordPress/contributor-toolkit/actions/runs/34770983301).
Pages deployment is intentionally skipped for a PR.

</details>

<details>
<summary>Screenshots</summary>

The banner and source controls are captured from the real Electron UI:

![Applied PR in its
ticket](https://raw.githubusercontent.com/WordPress/contributor-toolkit/juanmaguitar/pr-checkout-ticket-continuity/docs/public/screenshots/pr-applied.png)

![Apply
controls](https://raw.githubusercontent.com/WordPress/contributor-toolkit/juanmaguitar/pr-checkout-ticket-continuity/docs/public/screenshots/apply-patch-panel.png)

</details>


<details>
<summary>Stack review update (2026-09-14)</summary>

Rebased onto the reviewed lower stack as `c9e828f`. The CodeRabbit
finding on `ticketSwitchLifecycleRef` remains fixed in the commit phase,
and the same layout effect now publishes the corrected PR retry callback
inherited from #461. Validation on the final stack: focused
unit/integration suites 33/33; full Node suite 1,420 passed with 2
expected skips; targeted dirty-trunk journey 1/1; lint and `git diff
--check` clean. **0 remaining [fix here] · 0 [follow-up].**

</details>

The pull-request checkout stack (#459, #460, #461, #463) landed while this was
open. One conflict, in README.md: trunk rewrote the "try the work that already
exists" bullet, because a pull request is a checkout now rather than a patch
applied into the tree, and this branch had added a sentence to the bullet above
it. Trunk's wording kept, this branch's sentence kept.

Everything else merged without a conflict, and the seams that could have merged
cleanly and still broken were checked: the packaged smoke test's list of
contextBridge keys now carries both sides' additions, and the IPC coverage
guard classifies both sides' channels.

Verified on the merge: lint clean, 29 journeys, 15 packaged, and a wpct:// link
delivered against a build packaged from it. One unit test fails,
"the patch panel can render a large added text file without overflowing the
stack" — it fails on origin/trunk alone on this machine too, so it is a
baseline failure and not this branch's.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SNfwbKozBsY9ub5goLJyBm

## Why

`v1.1.0-beta.1` shipped on 12 September. Trunk carries five commits
since, and this is the **second beta for 1.1.0**, published so
contributors can keep testing before the stable tag. The headline is
checking out a pull request as a real branch, with the author's commits
intact, in place of the unattributed diff the Apply panel produced
(#459, #460, #461, #463, closing #290 and #458); it also gives the app
an address a browser can hand a ticket to, `wpct://ticket/<id>` (#465,
closing #464).

The version reaches two places a contributor sees, and both must carry
the real build: electron-builder embeds it in the artifact names
(`wordpress-contributor-toolkit-1.1.0-beta.2-*`), and `src/logging.js`
writes `app <version>` as the log's first line, so a problem report
names the build it came from. That is why the bump merges before the
tag.

## What changes

Only the version. All three package-version fields in `package.json` and
`package-lock.json` move together from `1.1.0-beta.1` to `1.1.0-beta.2`.
No dependency versions change, and there is no application behaviour
change in this PR.

## How to test this

Platforms: any for the suite; macOS or Windows for the artifact check
that follows the merge.

In the repository root:

1. `npm run lint` is clean and `npm test` passes.
2. `node -e "console.log(require('./package.json').version)"` prints
`1.1.0-beta.2`.
3. `python3 -c "import
json;d=json.load(open('package-lock.json'));print(d['version'],
d['packages']['']['version'])"` prints `1.1.0-beta.2 1.1.0-beta.2`.

**What must not have happened:** no dependency version may change. `git
diff trunk` shows exactly three changed lines, all of them the root
package version.

After merge, the release build must produce artifacts named
`wordpress-contributor-toolkit-1.1.0-beta.2-*`, and the first line of a
fresh app log must read `app 1.1.0-beta.2`.

## Risks and limitations

No UI change. The risk is a mis-scoped edit in `package-lock.json`,
where dependencies also carry `1.1.0-beta.1`; the replacement was
confined to the first 2000 bytes of the file, which holds the two root
entries, and both files were re-parsed as JSON afterwards.

## Related

Same shape as #397 (v1.0.1) and #457 (v1.1.0-beta.1).

---

<details>
<summary>Review outcome (required — see AGENTS.md)</summary>

Version-only change, three lines. Verified locally on this branch: `npm
run lint` clean, `npm test` 1451 pass, 0 fail, 2 expected skips; `git
diff --stat` shows two files, three insertions, three deletions; both
JSON files parse. Nothing to fix, nothing deferred.

</details>

<details>
<summary>Screenshots or recording</summary>

Nothing on screen changes.

</details>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_0121dia1RzfskutrzA8iSK1K

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>