CD 9b9c9c71fe fix(bridge): stall-based WAITING detection, remove GetCascadeTrajectorySteps ...

GetCascadeTrajectorySteps has 775-step hard limit and cannot see
WAITING steps beyond that. No RPC exists for direct WAITING detection.

New approach: if stepCount frozen for 2+ polls (~10s) while status is
RUNNING, treat as WAITING and write pending approval to Discord.
30s cooldown prevents duplicate pending messages.

Also removes the last GetCascadeTrajectorySteps call from Extension -
now only a single GetAllCascadeTrajectories RPC per 5s poll cycle.

2026-03-08 08:05:41 +09:00

27 KiB

Raw Blame History

View Raw