🩹 Three quiet correctness fixes for the free Gemini web provider
- Saves what it said.
stream_gemini_web streamed the reply but persisted the [gemini-web: no response after retries] placeholder as the assistant turn, poisoning multi-turn history. The parsed text now lands in the saved turn.
/gemini_chats new is actually new. Clearing pop()-ed the conversation ids, but save_config() deliberately re-merges the on-disk file (anti config-wipe guard), so popped ids resurrected and the "new" chat kept the old thread. Clearing now writes "", which persists and reads as "no thread".- Fresh chat answers on attempt 1, not 3. The harvester seeded the throwaway "DULUS" priming thread's ids, so the first two real requests came back empty and every new chat ate a 2-retry cascade. The harvest now clears the thread; the provider re-captures the real ids from the first good response, keeping continuity from message one.
PyPI: https://pypi.org/project/dulus/3.10.33/
