Hivelord instant cancellation bug

## Testmerges
#12480: 'Sneaky Hijack Edgecase + Transmute Fixes' by Drulikar at commit be2730f9cf
#12542: 'Xeno defensive grab' by Drulikar at commit 71a0cb6906
#12573: 'Opensearch query builder' by fira at commit 4364144f53
#12626: 'Refurbished Combat Information Centre (2) - USS Almayer' by Steelpoint at commit c167971a27
#12182: 'Multiz projectile balance' by cuberound at commit 864049540e
#12706: 'MapGrids: QuadTrees Replacement' by fira at commit a93271db4b
#12434: 'Attempts to fix runaway explosion recursion' by Drulikar at commit cd4a1137c5
#12627: 'Tyrargo Rift (2) - Various Alterations' by Steelpoint at commit 39578b0c44
#12751: 'Remove rotation updates each-tick on projectiles' by fira at commit 64cba7cda2
#11804: 'Some more gun.dm nonsense' by Nihisohel at commit 9ccd9a661b
#12640: 'Fuel pumps have health during hijack + bullet ping fix + trapper shotgun flag fix' by Drulikar at commit f5a7f3b9f8
#12464: 'LV1021: Operation Falcon's Fury - Ground Map' by Steelpoint at commit e9ca7f7177

## Round ID
35571

## Description of the bug
Randomly right after the hijack I tried building and it instantly cancelled, tried opening any door, it also instantly cancelled, repeat any building or item, tried the three fixes, reconnection and closing/reopening the client. Nothing worked, a helped about the bug, somehow randomly it started working again, no clue how or why.

## What's the difference with what should have happened?
I expected normal building, then suddenly it all cut short on the first frame it seems

## How do we reproduce this bug?
Not sure

## Attached logs
```
N/A
```

## Additional details
- Author: Maciejewicz
- Admin: Thespy24574
- Note: None

Start by reviewing the report for round 35571 and compare the described post-hijack building and door interactions with normal behavior. No source files, tests, reproduction steps, or logs are identified, so first establish a reliable reproduction and locate the affected interaction code. Done means the instant cancellation is explained and no longer occurs in the reported scenario.

Written by the indexing model from the issue text.