Long-running /loop can schedule its own wake-ups now that the server switch check is gone.
What's wrong with this entry?
The tool that lets a long-running /loop schedule its own next wake-up used to refuse and log a gate_off event when a server-side switch was off. That check is gone, so the tool works for anyone who can call it, and it now only declines once the loop has hit its maximum duration.
- The refusal text no longer mentions the switch; the remaining refusal cites max duration only and tells the model not to re-issue.
- No setting replaces the removed check.
Wakeup not scheduled. The loop reached its maximum duration — the loop has ended; do not re-issue.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Loop file can come from stored state instead of disk
Both mention loop
-
v2.1.246
The interactive session was split into controllers and stores
Both mention loop
-
v2.1.246
Resume, rewind, restore and summarize moved onto the session controller
Both mention loop