Resham Joshi 46e43a0ec3 Label optimize suggestions by destination (#281) ... Closes #277. Every paste-style fix now declares an explicit `destination` so users can tell at a glance whether a suggestion belongs in CLAUDE.md as a permanent rule, in a one-time session opener, in the current chat as an ask, or in a shell config file. Previously the prompts had no labeled home and users were dropping one-time session openers into CLAUDE.md as permanent rules. Type changes: - New `PasteDestination` union: `claude-md` / `session-opener` / `prompt` / `shell-config` - `WasteAction.paste` gains `destination?: PasteDestination` Renderer changes: - CLI `optimize` command (renderOptimize → renderFinding) prints a section header above each fix block: -- Suggested CLAUDE.md addition (permanent rule) ─── -- One-time session opener (do NOT add to CLAUDE.md) ─── -- Ask Claude in the current session ─── -- Add to your shell config ─── -- Run this command ─── - Interactive dashboard (FindingAction in dashboard.tsx) gets the same treatment so the in-popover findings list reads identically. Existing fixes retagged appropriately. Two existing prompts that lacked destination context altogether ("Set a delivery checkpoint at the start of the next expensive thread", "Start the next expensive thread with a fresh-context constraint") now read as one-time session openers with a clear "do not add to CLAUDE.md" hint — the exact failure mode the reporter described. Tests: - Existing `detectJunkReads` test extended to assert the destination tag. - New regression block walks every detector that emits a paste-style fix and asserts each one declares a destination — future detectors that ship without one get caught here.		2026-05-08 23:30:53 -07:00
..
litellm-snapshot.json	Label optimize suggestions by destination (#281)	2026-05-08 23:30:53 -07:00