From b9001b7aac37d988468c05915a908debe99c4d5f Mon Sep 17 00:00:00 2001 From: GHStaK Date: Wed, 18 Mar 2026 13:03:02 +0900 Subject: [PATCH] Document gemini rollback baseline --- TODO.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/TODO.md b/TODO.md index cfa26e8..a87074c 100644 --- a/TODO.md +++ b/TODO.md @@ -655,6 +655,28 @@ - If behavior in the browser does not match the latest backend/frontend code, the first assumption should be stale frontend assets until proven otherwise ## Recent Change Log +- Date: `2026-03-18` +- What changed: + - Reverted the recent Gemini output-format experimentation commits so the repo returns to the last simpler known-good search/Gemini state anchored by `91ee375`. + - Reverted commits: + - `f5d76fc` `Replace gemini batch JSON protocol` + - `b6a217c` `Harden single-candidate gemini recovery` + - `3be7971` `Reduce gemini partial batch noise` + - `513199f` `Harden gemini vision JSON recovery` + - The effective runtime baseline after the rollback is now the `91ee375` state plus the newer Windows 11 PowerShell workflow work. +- Why it changed: + - Repeated Gemini output-format changes were still producing real user-facing failures across multiple logs, including: + - `gemini vision failed for all batches` + - `gemini vision partially failed on 4 of 6 batches` + - extremely short truncated payloads such as `"{\"recommend"` and `"{\"recommendations\":[{\"index"` + - The user explicitly requested a rollback to a commit state that worked normally instead of continuing to stack more Gemini parsing experiments. +- How it was verified: + - `pwsh -NoProfile -File scripts/selftest.ps1` + - local git history inspection confirmed the rollback point as the pre-experiment Gemini baseline `91ee375` +- What is still risky or incomplete: + - This rollback intentionally gives up the later Gemini parsing experiments, so the codebase no longer contains those attempted mitigations. + - If the original upstream Gemini truncation issue already existed before those follow-up commits, it can still reappear and would need a cleaner redesign from the reverted baseline rather than more incremental patching on top of the discarded branch. + - Date: `2026-03-17` - What changed: - Fixed a search-budget regression where source collection could consume the full `SearchService` deadline and leave no time for Envato / Artgrid enrichment, causing Gemini to see only missing or low-value visuals.