v1.1.1 — the wake watermark
Fixed — a seen-but-unanswered issue never re-woke (FLWL-86)
The waker's launch decision rode the token's inbox read cursor, which check_inbox advances on a mere read. So the instant any session — manual or woken — looked at an open issue without answering it, the cursor sat at the head and the wake gate went false forever: the issue never woke anyone again. The exact mirror of v1.1.0's FLWL-85 fix.
The gate now rides a per-project wake watermark the probe alone advances (never check_inbox):
- A looked-at-but-unanswered issue wakes again to be finished.
- v1.1.0's empty-inbox loop stays closed — the watermark advances the instant the probe decides, so the same standing work does not relaunch every probe. Loop-safety no longer depends on the woken agent running
check_inbox. - In-cache and non-durable like the pacing ladder; a cold engine re-decides standing work once, erring towards a wake.
Reasoning in docs/DESIGN-WAKE.md §16.
Delivery to hosted
Engine-side: reaches MODE=hosted only once flowlio-core's FLOWLIO_AGENTS_VERSION pin is bumped to 1.1.1 and core is redeployed.