[BUG] L100 Akechi PLD: : Requiescat planner timing/range behavior

[prompt-to-code]

1. In the Req track, some options use a 180s cooldown display even though its 60s

From what I can tell:
Together is listed as 60s
RaidBuffsOnly, Force, and ForceWeave are 180s

2. Imperator should be usable outside melee range

Imperator can be used at range, but currently the logic requires the target to be within 3y. This can cause Imperator not to be used and drift. I think the issue may be that Requiescat and Imperator share the same planner track, but the module’s usage condition treats both as if they require melee range.
A possible fix would be to keep the same Req. track, but base the range check on BestRequiescat: use 3y when BestRequiescat is AID.Requiescat, and 25y when it is AID.Imperator.

3. Blades and Holy Spirit

The blade combo can be dropped if Requiescat is no longer active, even when there are steps available.
Happens if req falls due to small downtime, but blades are still available)

Expected:
Req / Imperator required to start Confiteor.
Once the Blade combo has started, the module should continue Blade of Faith / Truth / Valor based on BladeComboStep

Holy Spirit
Currently, Divine Might Holy Spirit is spent immediately after the Atonement chain. Ideally yo want to spend Holy Spirit right before the next Royal Authority would overwrite Divine Might.

Desired behavior:
Royal Authority → Atonement → Supplication → Sepulchre → Fast Blade → Riot Blade → Holy Spirit → Royal Authority

It should still be used early if:
the player is outside melee range,
Divine Might is about to expire,
Divine Might would be overwritten by the next Royal Authority,
or the user explicitly forces Holy Spirit.

But normally DMHS should probably be held until the next combo GCD would be Royal Authority.

Ik its lowk alot- I can try to fork and submit a PR with these changes if that would be helpful.

[prompt-to-code]

@Akechi-kun I noticed a behavior with the new Holy / Divine Might logic that I think needs to be adjusted.

When using Holy = VeryLate, DMHS is correctly held until after Riot Blade. However, if out of melee range while DM is active, the module still holds HS for that Riot Blade timing. Because of that, the ranged logic can end up using Shield Lob instead, even though DMHS is available, instant, and would be the better ranged GCD.

Current behavior:

Divine Might is active.
Holy Spirit is available.
Player is outside melee range.
Holy = VeryLate continues holding Holy Spirit until LastComboAction is RiotBlade or Divine Might is about to expire.
Ranged = Automatic may use Shield Lob while away.
Result: the module uses Shield Lob even though DMHS could have been used for ranged uptime.

Expected behavior:

In melee range, VeryLate should keep its current behavior and hold DMHS until after Riot Blade / before Royal Authority.
Out of melee range, VeryLate should allow DMHS to be spent immediately instead of using Shield Lob.
If Divine Might is about to expire, it should still be spent as normal.

Everything else was wonderful, ty!