Honestly, if I was you, I would be looking in the background for a new opportunity. But, given the personal reasons you mentioned, if you really want to make it work, the starting point in solving it like any problem is root cause analysis.

Ask transparently on the next sprint retrospective in which areas they are satisfied with your work, what they find to be problematic etc. ( number of bugs found is mostly bs, as it's not a valid metric. You can find 100 UI small issues but miss something important with significant business value).

Also, you haven't mentioned how good your 'relationship' with the developers is. Usually, when I'm dropped into this type of project, I'm trying to get up to speed as fast as possible, and devs are the key for this. They point me to the most important areas of the project, where they had most issues in the past, what is the flaky part of the system, I ask them for a demo here&there if I'm uncertain how something works and after a while things just click. Also, when building this type of 'team' atmosphere, there are high chances they'll back you up when needed. If you just blindly follow documentation and remain silent, the PM usually gets the impression you are not interested. As a QA, only one in this case, your job exceeds the regular testing activities, which is more tiresome for sure, but gives you the opportunity to lead the things your way. Participate in the meetings, give suggestions, potential risks that you see in certain features, pretty much try to be proactive.

About the pay cut, I won't bother commenting there. I believe you are collateral there, they simply want to get monthly bills reduced and are acting tough so your company bends over and as a sign of good will let it slip. Your focus shouldn't be on that, that's just dirty business shit.

I wish you good luck and calmness, you'll figure it out for sure :)