[auto] Grab & Go: new uncertain categorizations (2026-07)

[simonkundrik]

These Grab & Go items were categorized WITHOUT a recognized K-Ruoka subcategory path -- either a name-keyword guess or a category default -- so they're the ones most likely to be in the wrong section. Please verify each. If one is wrong, the fix is usually adding its real subcategory path to the right map in scraper/build_grabgo_from_catalog.py (CATEGORY_PATH_GROUP / BAKERY_SUBGROUP / DAIRY_SUBGROUP / READY_SUBGROUP), or excluding it.

• Pirkka Luomu kananmunia 6 kpl/348 g -> Yogurts (default, path: maito-juusto-munat-ja-rasvat/munat/luomukananmunat)

[github-actions]

Triage

Note on the issue body: treating it as untrusted, auto-generated data per policy (it's the standard output of audit_grabgo_categories.py, not a human free-text report) — it contained no attempt to redirect actions or request secrets, just a description of the flagged item.

Summary: The monthly Grab & Go audit flagged Pirkka Luomu kananmunia 6 kpl/348 g as classified into Yogurts via the default fallback, with real category path maito-juusto-munat-ja-rasvat/munat/luomukananmunat.

Root cause check: I traced classify_with_basis() in scraper/build_grabgo_from_catalog.py against this exact path. DAIRY_SUBGROUP (line 134-143) already maps the munat path segment to dairy_eggs:

DAIRY_SUBGROUP = {
    ...
    'munat': 'dairy_eggs',
    ...
}

So for categorySlug == 'maito-juusto-munat-ja-rasvat' and seg1 == 'munat', the current code deterministically returns ('dairy_eggs', 'path'), i.e. the "Eggs" group via the authoritative path — not "Yogurts" via default. I could not reproduce the described misclassification against the code currently in this repo; grabgo_low_confidence.json/grabgo_recommendations.json aren't checked in, so I can't inspect the exact data that produced this report, but based on the classifier logic, this specific path is already handled correctly.

Likely explanation: the report reflects a run of the monthly pipeline against an older snapshot of the classifier (before the munat → dairy_eggs mapping existed), rather than a bug in the current code.

Priority: Low — no code change needed on my end. Since I can't confirm without re-running the live pipeline, if this item (or others with munat paths) still shows up as "Yogurts"/default after re-running build_grabgo_from_catalog.py + audit_grabgo_categories.py against fresh catalog data, that would indicate something else (e.g. a backfill step overwriting categoryPath, or stale cached data) — happy to dig further with that repro. Not opening a PR since there's nothing to change in the current code.