Arnaud
d230098b1e
5 parallel domain re-sweeps against current code (last full audit was 2026-07-21/22, three days of heavy shipping since -- billing, developer/BYOK permission split, moderator scoping). Corrections and additions: - Fixed stale admin nav count (13 -> 15 sections, was missing Billing entirely). - Closed the /r/[id] followers-visibility gap that was flagged open -- it's fixed in code, found a new inconsistency in its place: a followers-only recipe never shows on the author's own profile grid. - Corrected "auto-deduct pantry on cook" -- the API logic is real and correct but both UI callers hardcode it off, so it never fires in practice. Was overstated as "Exists, one nuance." - Fixed "bulk-set-week" mislabel (it's bulk-clear only, no bulk-create). - Added several undocumented features: recipe notes, manual nutrition entry, AI conversation thread management + chat-history search, two more draft-recipe AI endpoints, the authenticated meal-plan collaboration UI (distinct from the public link), move-to-pantry button, pantry bulk-merge, public shopping-list page + print/QR, add-to-shopping-list AI tool, leftover-cron scope limitation. - Noted shopping-list collaboration now supplements polling with real push notifications on add/check events. New "Consumer-friendliness assessment" section directly answers whether Epicure has too many technical/developer-oriented features for a home-cook audience: mostly no -- API keys, webhooks, BYOK, OpenAPI docs, and self-serve developer access are all real surface but properly gated and hidden from nav by default. One genuine exception found and flagged: Settings -> AI's Model Prefs picker lets every user pick raw model IDs with zero gating -- the one place a developer-tool control was left unfenced on a consumer screen. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>