…ckout

Regression test for #16455.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…its repository

A pull request read may borrow any project on its host, so Check out and a
linked PR's Fix could fetch another repository's pull request into an
unrelated checkout, adding fork remotes and worktrees there. Before any Git
mutation, preparePullRequestThread now requires a configured remote of the
base repository named by the host's canonical PR URL, or of the head fork.

Checkout fixtures declare their GitHub identity through the existing
insteadOf rewrite helper, and a fork-only clone keeps working.

Fixes #16455

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…card

A filter path segment ending in [] resolves to the list of every element's
value, so a task can run only when, say, an issue carries a given label:
{path: 'body.issue.labels[].name', op: 'equals', value: 'needs more info'}.
equals, in and startsWith match when any element does, notEquals only when
none equals the value, exists when the list is not empty. Placeholders
accept the same syntax and render the list.

Before this, filters could only compare scalars and arrays satisfied
exists alone, so a GitHub issue_comment hook had to wake the bound thread
on every comment in the repository and let the agent discard the rest.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

The checkout guard only compared raw remote URLs, so a remote such as
`gh:acme/app` was refused even though `insteadOf` expands it to
github.com/acme/app. Compare both raw config and `git remote -v` URLs.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…e-16455

Co-Authored-By: Claude Opus 5.5 <[email protected]>

An HTTP remote on another port of the PR's host is a different server
(Forgejo keeps one login per host:port), so it no longer passes the guard.
Remotes that only their provider maps to the web host, such as a Forgejo SSH
host, are compared through the provider's refined repository identity.
Register the fixture seeder with Knip and keep the fixture to its one root.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

A Forgejo PR served under `/git` also accepted a fork checkout at the
same owner/name on the host's root, which can be a different server.
The head repository is now only looked for under the base's serving
root; SSH remotes that omit the mount still match through provider
refinement.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…in fixture seeder

Annotate the mounted Forgejo PR test scenarios as FakeGhScenario so their
state literal no longer widens to string (TS2322/TS2345 in CI typecheck).
The PR handoff fixture seeder now compares the resolved root against the
resolved /tmp, so macOS's /private/tmp passes, and rejects /tmp itself.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Port the checkout guard onto the source control definition registry and
provider web host resolution, and drop the reproduction fixture.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…-clone checkouts

Pass the checkout provider's kind to identity refinement so Cursor Origin
maps its git host to its browser host, skip the guard for bare-number
references that only resolve in the checkout's own repository, and accept
a same-named repository under the PR's serving root as a fork clone.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Before refusing, look the PR number up in the checkout's own repository
and accept when the host answers with the same pull request, so a remote
that still names a renamed repository is recognised.

Co-Authored-By: Claude Opus 5.5 <[email protected]>