test(web): fix the workflow script test that times out on busy CI runners - #1801

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

`UsageService.test.ts` fails on every run since 2026-11-01: its fixture aged past the 92-day saved-usage retention.

- **Red:** required `CI`, Test Server 2, on `hyprws` and every PR
- **Also red:** the sync candidate for `v0.1.6-nightly.20261031.3956`, so the fork sync cannot land the fix itself

## Change

**Exact backport** of upstream `1280ccd0d2a` (`https://github.com/pingdotgg/t3code/pull/28603`): the test pins `TestClock` near the fixture write.

- **Same patch-id:** `2389d44654df`
- **No upstream tag carries it yet;** the sync drops this commit once one does

## Scope and approval

Maintainer-authorized fork CI fix, precedent #1801: an exact upstream backport that unblocks #1990 and the fork sync.

Fixes #1992

### Close conditions

- [ ] `UsageService.test.ts` passes on any date
- [ ] `hyprws` CI is green

## Verification

- **`vp test run src/usage/UsageService.test.ts`:** 42 passed
- **`pnpm run typecheck` (server):** exit 0
- **Without the fix:** fails in CI run 41297867987, Test Server 2

## Fork trailers

Fork-Domain: upstream-fixes
Fork-Tier: bugfix
Fork-Upstreamable: yes
Co-authored-by: donjor <[email protected]>

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no

## Problem

The sync to `v0.1.1-nightly.20261020.3386` fails after a clean rebase:

```text
the rebased tip dropped 1 pull request link(s):
#1801: cited by fe075c9 ..., by no new commit
```

#1801 backported upstream `2532e64099` exactly; both share patch-id `4221c8a56228`.
The rebase drops it correctly, as its body said it would.
The link guard from #1620 has no exemption for that drop, so no sync can pass.

## Change

`refuseDroppedLinks` skips old commits that `git cherry <target> <old>` marks `-`, meaning the target already carries the patch.
Every other dropped link still refuses.

## Scope and approval

Maintainer-authorized: unblocks the requested fork sync.

## Verification

| Check | Result |
| --- | --- |
| New test, without fix | fails |
| New test, with fix | passes |
| `scripts/fork-sync.test.ts` | 69 passed |
| Guard on the real sync shas | passes |
| `vp run fork:ci` | exit 0 |

Written by Claude Opus 5.5 in Claude Code, hosted by T3 Code.

## Fork trailers

Squashes:

- 68228e2 fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 3c48e3a fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- 4f2343c fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)
- eb10567 fixup! fix(fork-sync): an exact upstream backport may drop its PR link (#1805) (#1805)

Fork-Domain: fork-meta
Fork-Tier: bugfix
Fork-Upstreamable: no