Administration Building not updating max allowed strategies with Strategia

[newzilla7]

KSP Version: 1.12.3.3173
Log: https://drive.google.com/file/d/1uTE2XWWUXVBL6Sv-TUN5B3n20NkX_XDB/view?usp=sharing

Issue: Strategia is supposed to use CustomBarnKit to update the limit on active strategies from the stock (1, 2, 3) to (2, 3, 4). However, the administration building is not being updated with this change, and is still limiting the active strategies to the stock limits.

Reproduction Steps: I reproduced the issue on a new save to verify it wasn't just a mod conflict. I removed everything from GameData, then restored only the bare minimum for Strategia to function:

• ContractConfigurator (v2.1.3)
• CustomBarnKit (v1.1.22)
• Squad
• SquadExpansion
• Strategia (v1.8.0)
• Module Manager (v4.2.2)

I then started the game and created a new save with all default settings. The level 1 Administration Building only allowed a maximum of 1 active strategy (should be 2 at level 1). To verify it wasn't simply a display error, I used the debug menu to add funds and reputation necessary to activate multiple strategies. Though I met the requirements for 3 different strategies, I was only able to activate 1. The remaining strategies remained unavailable, with the listed reason being a max active strategies limit of 1.

Screenshots here: https://imgur.com/a/duaBHLc

Notes: As far as I can tell, I have the most up-to-date versions of all of these mods, as well as KSP. I searched both these forums and reddit for mentions of similar issues and couldn't find any, which is why I'm posting here.

[newzilla7]

I decided to hook up dnSpy and see if I could figure out what's going on behind the scenes. It seems this behavior results from Strategia getting the max active strategies from CustomBarnKit, then subtracting 1. Why  it does this kinda mystifies me... I guess maybe the mod author decided to revert to stock limits, but did it through code instead of their CustomBarnKit config? I feel like I might be missing something cause this seems like such a weird behavior, but at least I know why it's doing this from a technical perspective...